[FFmpeg-trac] #11307(avcodec:open): [truehd_core] Application provided invalid, non monotonically increasing dts to muxer in stream 0

[FFmpeg]

#11307: [truehd_core] Application provided invalid, non monotonically increasing
dts to muxer in stream 0
------------------------------------+-----------------------------------
             Reporter:  microchip   |                    Owner:  (none)
                 Type:  defect      |                   Status:  open
             Priority:  minor       |                Component:  avcodec
              Version:  git-master  |               Resolution:
             Keywords:  thd         |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+-----------------------------------
Changes (by Balling):

 * keywords:  truehd truehd_core Atmos => thd
 * priority:  normal => minor
 * status:  new => open

Comment:

 ffmpeg  -i mzero_truehd_sample.mkv -c:a copy fawfafa.thd

 prints ()

 {{{

 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 97 >= 97
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 102 >= 102
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 107 >= 107
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 112 >= 112
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 117 >= 117
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 122 >= 122
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 127 >= 127
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 132 >= 132
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 137 >= 137
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 142 >= 142
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 147 >= 147
 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 152 >= 152



 and then ends

 [truehd @ 0000029225d65e80] Application provided invalid, non
 monotonically increasing dts to muxer in stream 0: 63227 >= 63227
 }}}


 so each of them has a difference of 5 just like in your example, the fix
 here is to use (see link on patchwork above)

 The default value of 1/1000 is good **for most use-cases**, but there
 might
 be scenarios where it is not (e.g. **TrueHD packets** have a duration <
 1ms,
 so different packets will **end up with the same timestamp** when using
 1/1000).  If the user has set a timestamp precision, then that should be
 honoured; **but if not, then we might use a different value than 1/1000**
 (in the future; I know that currently no code path that makes use of
 this exists).

 I doubt this will be implemented.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11307#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker