Cineform Codec Support - Lossless RGB 16bit Integer Format

Here is a link to a feature request:
FI-03033 - Flame Family (

I would like Cineform RGB 16bit lossless quicktime support. There currently isn’t a good transport option for log or display referred colourspaces from Flame in a single file. This seems like a good codec to fit the bill (JPEG2000 is too processor intensive). Please upvote it if you could use it in your workflow.


It doesn’t cost anything anymore, right? Why would I want to use it instead of just using ProRes?

1 Like

I think because it’s lossless?

1 Like

and 16bit.

There is also dpx-c which is based on cineform right? Its pretty dope alltogether

maybe we should try to convince ilm to add integer 12bit to EXR instead :rofl:

They changed the spec one time because of an internet slapfight with one of the Photoshop devs, so I’m hopeful!

Cineform is 16bit, RGB, lossless and open source. These specs are requirements from a lot of Studios and SVODs for post production workflows as well as for archival and transport media. The open source part also removes the license issues of a proprietary format such as ProRes (a.k.a. Why can’t I export a ProRes from my Linux or Windows Resolve PC). Oh yeah, Resolve already supports Cineform too so back and forth between Resolve and Flame working in a lossless workflow would be easier.

As a transport format, having an entire sequence as one file instead of multiple files also speeds up file transfer times as there aren’t multiple read/write requests happening for each and every frame. It makes it much easier to create manifests for archives as you could potentially list all your files in the single or double digits instead of having tens of thousands to up to over a million files.

The droplet compression is also highly efficient in terms of compression/decompression times and gets a smaller file size. This is better for both costs and the environment as you don’t need as much storage to deal with the media, which means less materials and energy is required to store it.

If it was contained within an OP1a mxf wrapper, there is a lot more metadata that can be stored with it as well.


Unfortunately, Cineform only resides within a Quicktime or AVI wrapper so that metadata comment is mute. Metadata in quicktime is very limited, but still probably has more information than a dpx file…

Yea i was about to say this, metadata would be important

I do agree there is a total gap in widely supported codecs for these formats:

  1. 12/16bit integer losless compressed mxf(or whatever holds metadata) container format

  2. 16/32bit float losless compressed container format (exrs in a container…)

  3. 12/16 integer Losless compressed single frame formar (exr integer… dpx-c) .

I was really rooting for cineform to take off after going opensource, especially becausw its wavelet based like jpeg2000, which is cool , I think adobe can handle it as well?

1 Like

Another lossless option could actually be H265.

They have some High Throughput 16bit 4:4:4 profiles.

I actually don’t have a strong preference as to which codec, I just want a lossless 16bit integer codec that could be widely supported tht doesn’t slow the system down to decode it (like J2k does).

1 Like