Quote:
Originally Posted by kolak
Could we have ProRes presets updated so they better match official profiles (in this case ProRes_ks is better). It will be slower, but more Apple alike.
We need color tag as well, so parameters like this for ProRes HQ:
-metadata:s "encoder=Apple ProRes 422 (HQ)" -vendor apl0 -movflags write_colr -c:v prores_ks -flags "+bitexact"
Then also have interlaced box (+field order) to tick which adds:
-vf "setfield=1, fieldorder=tff" -top 1 -flags "+ildct+ilme+bitexact"
*tff or bff (and top 1 or 0)
This way we enforce proper interlaced encoding.
I'm not sure about this bit, but if you can set:
AVFormatContext.flags |= AVFMT_FLAG_BITEXACT.
|
> Could we have ProRes presets updated so they better match official profiles
Any hint how to do this? proresenc_kostya.c has prores_quant_matrices, do you mean to change that?
> -metadata:s "encoder=Apple ProRes 422 (HQ)" -vendor apl0 -movflags write_colr -c:v prores_ks -flags "+bitexact"
From this I understand:
-movflags write_colr: ok
-vendor apl0: ok
"encoder=Apple ProRes 422 (HQ)": can you help with all possible strings?
-c:v prores_ks: this is what I used anyway
-flags "+bitexact": can you provide any background on what it means?
> -vf "setfield=1, fieldorder=tff" -top 1 -flags "+ildct+ilme+bitexact"
setfield: ok
fieldorder: ok
ildct+ilme: ok
top: as I read it belongs to chroma location which can have 7 different values. This is disturbing option.
I think it is better if it is understood by the pipeline. Wondering how big is this problem? Can you have in practice only 422-top or anything else?