Hello! I found it useful to have the ability to provide a hint to the muxer about the desired timebase.
This is useful, for example, when transmuxing to MP4 container. If the timebase of the input stream differs from the output, then when transferring the timestamp from one timebase to another due to inaccuracy of calculations there may be two different packets with the same dts/pts at the output. Which will result in an error message from FFmpeg:
[mp4 @ 0x7ff150113f40] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 1538093 >= 1538093
Hello! I found it useful to have the ability to provide a hint to the muxer about the desired timebase.
This is useful, for example, when transmuxing to MP4 container. If the timebase of the input stream differs from the output, then when transferring the timestamp from one timebase to another due to inaccuracy of calculations there may be two different packets with the same dts/pts at the output. Which will result in an error message from FFmpeg: