September 14, 2016 at 3:57PM


CINEGY codec

Cinegy codec is a GPU accelerated codec able to process 1100FPS@8k 10bit 422...
Why no one talks about it? Why the cameras are not using it? What to expect of this codec? Do you think it should be implemented in cameras and recorders? Finally the standard codec able to do it all? Will the manufactors embrace it?

I think there is something sneaky in the "backstage" of the industry giants making efforts for this codec not to see daylight...


Probably because it is a boutique solution for 8K video and up.

Can we can download the encoder, encode a video and then render it on a viewer that can decode it without paying a gazillion dollars?

If so, I try it, let me know how to obtain it, if not you have the answer why no-one talks about it.

September 14, 2016 at 5:25PM

Cary Knoop

The encoder is called the Cinegy Daniel2 encoder and it is real.

The reason you can't just download and use it has a number of reasons.

a) we are still optimizing it and will only have a matching, code frozen encoder/decoder pair that is GPU accelerated in October (2016). This will also be first of all limited to Windows and Nvidia GPUs. Other OSes will come later as may other GPUs, although we are no in a hurry here as OpenCL comparatively sucks. We have a CPU based reference encoder and a GPU based decoder and player that proves the speed achievable.

b) if the Cinegy Daniel2 codec is not deeply, directly integrated into the GPU rendering or effects pipeline of the application that uses it then most of its benefits are lost. An implementation as Quicktime or AVI plugin is more or less pointless. Maybe we would see a 2-3x speedup but not the factor we can achieve.

c) we have been showing the Cinegy Daniel2 GPU codec at all tradeshows and conferences we attend, but people seemingly hear 8K and beyond and then immediately think this is way in the future, despite the fact this is equally applicable to 4K or HD.

d) we are talking to the usual suspects whose editing and effects tools you are using. The responses vary from: "we have a published API knock yourself out" to "integrate it via Quicktime" with some very few wanting to jump on it and wanting immediate deep integration.

e) we are concentrating with this on the Japanese market as there we will see the first 8K broadcasts and therefore 8K workflows that need much higher turnaround speeds.

At IBC 2016 which just ended, we did show 8K realtime video recording and playback of the same file while recording using the Cinegy Daniel2 GPU decoder and Daniel2 Player.

Summary: In any case whether the Daniel2 GPU codec will be adopted and therefore useful to more than a handful specialist applications depends on its adoption and integration in the commonly used video apps and tools.

September 15, 2016 at 4:17AM


Let me know if you need beta testers at the command line level (Avisynth, Vapoursynth) or with a frameserver.

September 15, 2016 at 3:08PM

Cary Knoop

Hi Jan,

You are absolutly right about everything. In my opinion there are some ways for the consumer to have your amazing product:
1st- the NLE programers adopt this codec because they care about their clients.
2nd- the client pressure and demand the integration.
3rd- build a new NLE with this codec in mind.
4th- integrate this codec in the aquisition of images,to be more specific, get this codec sraight out of the camera nativelly, and this would be awesome for everyone workflow wise.

Do you think it is possible for cameras to provide this codec based images? As I see it, it would be a win-win situation...

September 20, 2016 at 4:38PM


My advice: make this codec available for free on Windows and MacOS systems as a 3rd party codec that can be used in any NLE. At least up to 1080p output or even 4k.

You won't have any other chance to make this codec popular.
The mass need to test it with their own footage and workflow.

September 15, 2016 at 7:30AM

Steadicam Operator/Owner

Your Comment