On 23-12-2020 03:35 pm, Nicolas George wrote:
Gyan Doshi (12020-12-23):
Which piece of info or object would indicate that? At the stage of this
check, I don't see any available.
Read Michael's mail:
Output #0, avi, to 'file.avi':= 0kB time=-577014:32:22.77 bitrate=
-0.0kbits/s speed=N/A
The problem is obviously the time. The large negative number looks like
it was converted from AV_NOPTS_VALUE, so test if the PTS being printed
is AV_NOPTS_VALUE or not.
That's not the issue. It's the mangled line - the output from
lavf/dump.c. mangled with stats line
AV_NOPTS_VALUE is an acceptable value and already checked for at line
1815. As is <=0 output size.
Indicating to the user that ffmpeg processing has stalled at the
beginning is a valid and acceptable outcome, even a necessary one.
The delay here is just to avoid the mangling. Some hardcoded value is
the best that I see we can do, but if you have an analytical solution,
I'm all ears.
Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
