6 days ago · If the FFV1 files were readable natively, that would be a huge progress for a lot of archivists. Please consider an implementation of a FFV1 decoder, it doesn't even have to be …

5 days ago · FFV1 is still massive as at best you get 3:1 for typical video. Very pro work is done with DPX or EXR so uncompressed image sequences (10,12,16bit or float). In the same time …

4 days ago · That's a shame because MKV/FFV1 is gaining in popularity in A/V archives, so it's more and more likely people end up with such files to be loaded into Resolve sessions, for non …

3 days ago · I can read and write FFV1 just fine, but not in an AVI container. A rewrap into MOV should help. My disaster protection: export a .drp file to a physically separated storage regularly.

3 days ago · Since I don't see major performance issues once the file is loaded for good, there doesn't seem to be a ressource problem with FFV1 decoding. The same source file opens and …

Mar 18, 2023 · The correct future proof way is to encode to ffv1 and mkv. Because both are standardized and documented so future generations can recover the data(3). Davinci has no …

Mar 6, 2025 · Hi FFv1, 14 and 16 bit depths are reported as 8 bits. Sample mediainfo: General Complete name : G:\MOV\Lossless-sizeComp-Sparks\FFv13-422-14.mov

6 days ago · Just wanted to say thanks for MKV and FFV1 support. I and others have been lobbying for years and it's been there for quite some time. Makes our workflows so much …

Dec 5, 2022 · Thank you for adding it to Resolve. Could you also add a 9-bit in additional? The idea is to keep sources for 8-bit videos without a grain. 10-bit encoding requires a bit more …

Feb 20, 2025 · Resolve isn't able to decode grayscale FFV1. The files show up in the media panel and can be imported into the project bin but the playback is impossible: media viewer displays …