Changes between Version 1 and Version 2 of Ticket #6905, comment 3


Ignore:
Timestamp:
Dec 11, 2017, 12:59:40 AM (21 months ago)
Author:
Misaki
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6905, comment 3

    v1 v2  
    1 What do you mean by working file? Many programs play it back just fine. ffplay does it normally the first time; if you seek back to the start, frame 0 does display for an extra 2~3 seconds. totem plays it completely normally. vlc has a short delay, plays it normally, then starts dropping frames because of "more than 5 seconds of late video". Note that playback behavior is slightly different between ordered-frames.avi and ordered-frames-avicopy.mp4; common programs are using the frame (not packet) dts values for avicopy.mp4, which are a bit different from those in the .avi. Specifically, the second frame is displayed longer.
     1What do you mean by working file? Many programs play it back just fine. ffplay does it normally the first time; if you seek back to the start, frame 0 does display for an extra 2~3 seconds. totem plays it completely normally. vlc has a short delay, plays it normally, then starts dropping frames because of "more than 5 seconds of late video".
     2
     3(Edit: Note that playback behavior is slightly different between ordered-frames.avi and ordered-frames-avicopy.mp4; common programs are using the frame (not packet) dts values for avicopy.mp4, which are a bit different from those in the .avi. Specifically, the second frame is displayed longer; in totem, the 0 is played for a long time, then the 1 is shown for little or no time, then it plays 'normally'; if you seek back to the start, it does play normally. But in ffplay, both the 0 and 1 are displayed for extra time, with the 0 still getting more time if you seek back to start. vlc is just two seconds 'late', no dropped frames; not sure if vlc apparently requiring two frames as a buffer is related.)
    24
    35ffmpeg doesn't give any warnings or errors for that command.