I think I can pick up where Ibrahim left off. I have the same question as he/she.
Ibrahim shot 14bit raw video from a Canon 5D Mark III.
Magic Lantern is a firmware for Canon DSLR cameras that enables RAW video. The firmware is ported mainly for the Canon 5D Mark III (3) and Canon 5D Mark II (2.) Among other entry level Canon DSLRs.
Magic Lantern creates a file ending in “.MLV.” To my understanding, an .MLV file is simply a container that holds .DNG frames. (Albeit with a little extra metadata in the header.) .MLV is not usable by most programs, so a standard part of the process is using an app to extract the .DNG’s from the .MLV. Resulting in cDNG sequences.
As it is now, there is no IDT for Magic Lantern enabled Canon cameras. But for those of us using Magic Lantern, we are used to workarounds, as the firmware is open source and user-developed; so development is slow.
I too, would like an ACEScct workflow (or one that is really close) in Davinci Resolve for Magic Lantern RAW video.
As I mentioned above we Magic Lantern users are used to work-arounds. For me, inside Davinci Resolve (Color Management set to ACEScct, and output set to REC709) choosing ANY IDT for cDNG sequences from Magic Lantern, reveals an identical image. It seems the IDT doesn’t change anything for cDNG sequences from Magic Lantern. Is there an explanation to this? Is it because it is RAW data?