On 24-01-2019 08:11 PM, Carl Eugen Hoyos wrote:
So you did test a command line that triggered the error message
for audio?
Not till now :)
Ok, mostly not a problem (in terms of raising attention via the log),
But exit code is shown as 0.
And your modified message *is* shown for crafted c
2019-01-24 15:17 GMT+01:00, Gyan :
[...]
>>> 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. F
On 24-01-2019 07:05 PM, Carl Eugen Hoyos wrote:
2019-01-24 14:13 GMT+01:00, Gyan :
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
2019-01-24 14:13 GMT+01:00, Gyan :
> 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.)
> 3) If the offending track is audio, the
On 24-01-2019 05:25 PM, Carl Eugen Hoyos wrote:
ffmpeg | branch: master | Carl Eugen Hoyos | Thu Jan 24
12:52:50 2019 +0100| [406f8d9c9a10267299d6eefd0672bd4f4c9342b4] | committer: Carl
Eugen Hoyos
lavf/movenc: Mention video_track_timescale as option to fix the timescale.
Smarter improveme
