Ahhh,... okay, reencoding 'Test Patterns Resolve 422 HQ 10-bit.mov' with ProRes created a file with the 'Druation_LastFrame' info.
The whole time I understood it that the input had this info not the output,...
is the call used.
During the reencoding ffmpeg reports:
-> the input is problem and ffmpeg makes something funny with the time codes.
(when reencoding to a non ffmpeg based encoder, only the frames are used not the time codes)
There is probably an additional ffmpeg-option to fix this,..
Cu Selur
The whole time I understood it that the input had this info not the output,...
ffmpeg -y -noautorotate -nostdin -threads 8 -ignore_editlist true -i "C:\Users\Selur\Desktop\ProRes Examples 10 12 bit\Test Patterns Resolve 422 HQ 10-bit.mov" -map 0:0 -an -sn -pix_fmt yuv422p10le -strict -1 -vsync 0 -vcodec prores_ks -profile:v 3 -vtag apch -metadata encoding_tool="Hybrid 2021.03.30.1" -f mov "E:\Output\Test Patterns Resolve 422 HQ 10-bit_2021-03-30@16_23_34_1710_01.mov"
During the reencoding ffmpeg reports:
[mov @ 00000108f32800c0] Application provided duration: -9223372036854775808 / timestamp: -9223372036854775808 is out of range for mov/mp4 format
[mov @ 00000108f32800c0] pts has no value
(when reencoding to a non ffmpeg based encoder, only the frames are used not the time codes)
There is probably an additional ffmpeg-option to fix this,..
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.