Robert Niessner wrote:If that would be simple enough then we already would have ProRes RAW support in Resolve.
As Resolve does support a vast range of other RAW Formats from competitors the only conclusion for me is that somehow Apple doesn't wants them to.
Unlike those other RAW codecs, Prores RAW is the only one that actually competes with BRAW as it's the only other one available in external recorders.
Robert Niessner wrote:Originally the BMCC only had uncompressed CDNG, later with firmware 1.8 or 1.9 (afair) it got lossless compression which reduces file sizes to 50%-60%. And I had several tools which could not read compressed DNGs.
That's correct but since my post was already long I decided to say "Before they switched to BRAW" in an attempt to refer to the time period right before they switched to BRAW. At that point, none of their previous cameras could shoot uncompressed RAW any more.
Robert Niessner wrote:I think he means that BRAW has an SDK making sure decoding is standardized, while CDNG isn't and every tool can use its own method for decoding.
That's a good point. That could be addressed to some degree by creating a shared, open-source library for decoding CDNGs that other programs could adopt and contribute to.
But also one of the reasons BRAW can be so consistent with decoding is because the actual sensor information is irrelevant at the decoding step. It doesn't know if the sensor used to record the data was bayer, RGBW, or Foveon. All of the information related to how the sensor captured the image was discarded in-camera.
Robert Niessner wrote:There is more metadata needed than slate, ISO and WB.
I just checked out what metadata gets stored in old 2018 DNG files from my BMCC:
Slate
...
BRAW adds:
...
Those could be added to CDNGs as well. Both DNG and MXF support custom metadata so you're not limited to a specific set of fields, you can add any information you feel is relevant. Less metadata was stored in BMD's BRAW file vs their CDNG files because they decided to store less, not because their was limitation on what CDNG could store.
Robert Niessner wrote:You are aware that a Bayer sensor does only have 1/4 of red and blue and 1/2 of green sensels?
That's the trick here.
Y, cb, and cr don't translate to G,B, and R channels though. All of the sensels on a bayer sensor contribute to both the luma and color channels. After debayering an image, you still get full-resolution RGB channels even though each channel as information filed in with interpolated data.
When converted to Ycbcr, the luma channel is created with an weighted sum of the data in all three channels. The Cb and Cr channels don't store the absolutely brightness values of blue and red, they store them as the delta between them and the Y channel. When transforming back to RGB, you could say the green channel is derived from the information in the luma channel that the cb and cr channels didn't claim. Because the green chroma info is reliant on all three channels, once you lower the cb and cr channel resolutions to 25%, you're also lower the green chroma resolution to 25%.
If you look at the RGBW color filter on 12K sensors, half the sensels are contributing chroma information, 16% are contributing specific color information, and all of the sensels are contributing different degrees of luma information...or at least that's true when you're shooting 12K. Once you shoot 8K, every final pixel is made up of far more actual sensel information. By the time you're shooting 4K, every single channel from every single pixel will have been made up from the combined values of multiple red, green, blue, and clear sensels with no interpolated values.
Mathematically, the 12K should be able to record 4K video that looks as good or better than a Foveon sensor but the general belief is that it's 4K doesn't look as good as shooting 12K or 8K and downsampling in post. That's because 12K BRAW only stores color information at 6K, at 8K it's only storing color information at 4K, and at 4K it's storing color information at 2K.
A real RAW format that tries to preserve sensor readout data might store the 12K's 4K readout as four 12-bit channels and when it's expanded to 16-bit linear RGB in post, each channel would actually have precision closer to three 13-bit channels because the W channel's values would be added to the RGB channel without first reducing the actual RGB values to keep the total within a 12-bit range.
With losslessly compressed CDNG that would average between 600-730MB/s at 24fps. That's high because it's not storing a single bayer channel and instead storing 4 full-resolution channels but that's still less data than shooting Q0 12K to get a similar, but still technically inferior result. Then of course if you're okay with lossy compression the camera could combine in the W channel into the RGB channels in camera. That would immediately reduce the bit-rate to 450-550MB/s and that's before any DCT compression is done.
Robert Niessner wrote:I think you should re-read the patent. If what you said was true, then we should get the same out of ProRes files when doing color manipulations - but that isn't the case. For example I have shots with lots of those saturated LEDs - I can get so much more out of BRAWs than from ProRes files.
You could if the Prores file is 12-bit and doesn't have the ISO and white balance adjustments baked it. You don't even really have to compare it to another codec to show that the WB and ISO dropdowns aren't doing anything that can't be done with the other grading tools. You can take the same BRAW shot, put two copies of it into a Resolve timeline, and set one to ISO 100 and the other to ISO 1000 then try to match one to the other in the grading tools. Again, it's just metadata,