On 23-12-2020 03:12 pm, Nicolas George wrote:
Gyan Doshi (12020-12-23):
Avoids breaking output file dump report.
---
fftools/ffmpeg.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
This looks broken. Why 100ms? Because on your setup, 80ms is not enough
but 100ms is? On a slower system, it would need to be 120 or 200.
Test if the info to be printed is already valid.
Which piece of info or object would indicate that? At the stage of this
check, I don't see any available.
Earlier, it was hardcoded to 500 ms. I chose something more apt for
2020, but 500 ms is fine as well.
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".
