It still doesn't mean that Resolve support would not be welcome. ffv1 uses fairly complex math and its decompression costs a lot of CPU. Have you tested CPU usage when playing back ffv1 4K files? Good lossless compression doesn't come for free. Alpha Exports Codec Passthrough (1) Decode Encode Apple ProRes imf 422, 422. Problem is that you may always need to convert ffv1 for further work. DaVinci Resolve 16.2 Supported Formats and Codecs 2.
Yohann wrote:Adding my vote as well for this suggestion. Please consider an implementation of a FFV1 decoder, it doesn't even have to be highly performance since we already heavily use the optimized medias when working on DPX sequences. If the FFV1 files were readable natively, that would be a huge progress for a lot of archivists. That's 60% storage space saved with zero data loss.!Įven film laboratories we are working with start to provide the digitized reels using this codec.īut unfortunately, we still need to convert them back to DPX sequences if we want to be able to read and work on them within Resolve. Thus, if you want the video to be in the MKV format, you have to render the video in another file format and convert the file to MKV with a third-party application. The figures are pretty much self explanatory: with a recent 4K scanned movie (colored 10bit), the total weight of the DPX sequences were 2.0TB and was reduced to 833GB after being transcoded to FFV1. DaVinci Resolve 18 cannot export files in the MKV file format. We convert our DPX sequences to FFV1 files before archiving them to LTO tapes since the space saved is huge.
I am working at the Cinémathèque française and have been able to setup a well-working networked workflow based on DaVinci Resolve for the q.c and restoration of our digitized film collection. Adding my vote as well for this suggestion.
0 kommentar(er)
