Saving a .ts file: "Too short" error, due to "PTS<DTS"

[mm0359]

Windows: XP.

I have a (very) few .ts files that current Avidemux still can't save.
Here is one case.

I am saving a 1.68 GB .ts file in Copy/Copy/Ts mode.
The source seems to have/trigger a "PTS<DTS" issue.

Code Select Expand


v2.6.8: 38%, Too short
...
[getPacket] PTS<DTS : PTS=2963559 ms , DTS=2965399ms
[adm_lavLogCallback] [lavc] pts (266720379) < dts (266885979) in stream 0
[FF]Error writing video packet

v2.6.9-2.6.10: 00%, Too short
...
[getCompressedPicture] Compensating for rounding error with PTS=39860022ms DTS=0ms
[getCompressedPicture] Final DTS <0, fixing
[saveLoop] No PTS information for frame 1036
[adm_lavLogCallback] [lavc] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 3729602 >= 0
[FF]Error writing video packet

v2.6.11-2.6.14 (161024_8b5bfb9baa1): (38-)39%, Too short
...
[getPacket] PTS<DTS : PTS=2963559 ms , DTS=0ms
[adm_lavLogCallback] [lavc] pts (266720379) < dts (266885979) in stream 0
[FF]Error writing video packet


Fwiw, other "frequent" warnings for this file:

Code Select Expand


[Ts Demuxer]*********Pes too long*******

[ADM_verifyDts] Low dts : Out of order dts at frame 73838 2965379777,0,2963479777

[guessH264] Our best guess is at 39840022
[guessH264] Too much unknown PTS (2), aborting

[adm_lavLogCallback] [lavc] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 388558 >= 388558
[saveLoop] [FF]Error writing audio packet


Fwiw, I also noticed the following "adm_lavLogCallback ... deprecated ...":

Code Select Expand


  Avidemux v2.6.14 (161024_8b5bfb9baa1) .

[adm_lavLogCallback] [lavc] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[adm_lavLogCallback] [lavc] Encoder did not produce proper pts, making some up.


Anyway Avidemux could (better) handle this case?
Or anything I could do to work around this?