Changes between Version 3 and Version 4 of Ticket #6905, comment 8


Ignore:
Timestamp:
Jan 1, 2018, 12:30:55 AM (17 months ago)
Author:
Misaki
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6905, comment 8

    v3 v4  
    1 [Edit] When used as an input option, it does generate pts and there's no warning messages, but the generated pts are just 1 second (at 1 fps) higher than those generated by mp4 with the warning message. It's still using the packet pts to generate timestamps, rather than the frame dts as reported by ffprobe. I don't know if the 'frame dts' for .avi format is used the same way as 'frame pts' is used for other formats like mp4, or if accessing the frame dts for an avi requires some decoding while it's available without decoding for an mp4; basically whether the problems that ffmpeg and Chrome are experiencing are historical and due to the concept of 'pts' possibly arising after 'dts' had been around for some time. 'pts' and 'dts' are both not in Wiktionary.
     1[Edit] When used as an input option, it does generate pts and there's no warning messages, but the generated pts are just 1 second (at 1 fps) higher than those generated by mp4 with the warning message. (dts is the same, so pts are all 1 second higher than dts with -show_packets.) It's still using the packet pts to generate timestamps, rather than the frame dts as reported by ffprobe. I don't know if the 'frame dts' for .avi format is used the same way as 'frame pts' is used for other formats like mp4, or if accessing the frame dts for an avi requires some decoding while it's available without decoding for an mp4; basically whether the problems that ffmpeg and Chrome are experiencing are historical and due to the concept of 'pts' possibly arising after 'dts' had been around for some time. 'pts' and 'dts' are both not in Wiktionary.
    22
    33