19.04.2022, 08:37
No, FFV1 isn't a bad archival format, it just doesn't differentiate between interlaced and progressive data.
The best way to fix this is for me to add a dummy selection to the FFV1 encoder which lets the user decide whether wants interlaced or progressive data to be saved.
Since this will influence how Hybrid does filtering.
If you don't do any filtering overwriting the input scan type to progressive should be fine too.
Cu Selur
The best way to fix this is for me to add a dummy selection to the FFV1 encoder which lets the user decide whether wants interlaced or progressive data to be saved.
Since this will influence how Hybrid does filtering.
If you don't do any filtering overwriting the input scan type to progressive should be fine too.
Cu Selur