On 24-01-2019 07:05 PM, Carl Eugen Hoyos wrote:
2019-01-24 14:13 GMT+01:00, Gyan <ffm...@gyani.pro>:
Or better, a viable timescale ceiling can be printed.
Yes, this is exactly the reason why nothing was committed for
several years.
(Although printing the current scale is a very good idea that
wasn't suggested so far.)
The ceiling should be (int) (INT32_MAX * track->timescale /
track->duration )
(Shouldn't the value limit be UINT32_MAX?)
3) If the offending track is audio, then nothing can be done, the
message should reflect that (and the muxer should quit).
Please provide an example.
I don't follow. The error msg only suggests to modify the timescale of
video tracks. For audio, the timescale is fixed to the sampling rate and
isn't selectable, so if there's an overflow there, there's no remedy.
Gyan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
