[FFmpeg-trac] #6588(undetermined:closed): Failure to decode some frames causing freeze
FFmpeg
trac at avcodec.org
Thu Mar 31 19:53:53 EEST 2022
#6588: Failure to decode some frames causing freeze
-------------------------------------+-------------------------------------
Reporter: Mark Ogle | Owner: (none)
Type: defect | Status: closed
Priority: important | Component:
| undetermined
Version: git-master | Resolution: fixed
Keywords: mov h264 | Blocked By:
regression |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Changes (by Balling):
* status: new => closed
* resolution: => fixed
Comment:
Okay, so what happens here is that it is counted from 1 now:
[mov,mp4,m4a,3gp,3g2,mj2 @ 00000253cf3eb640] AVIndex stream 0, sample 1,
offset 20d4, dts 0, size 51637, distance 0, keyframe 1
'''and that now we have
'''
{{{
AVIndex stream 0, sample 14, offset 1c1e7, dts 5200000, size 57728,
distance 0, keyframe 1
}}}
instead of
{{{
AVIndex stream 0, sample 0, offset 1c1e7, dts 5200000, size 57728,
distance 0, keyframe 1
}}}
also the file is thought to be progressive, which it is.
Next:
63 packets read (431352 bytes); 51 frames decoded;
not printed. so is dup parameter:
frame= 63 fps= 56 q=-1.0 Lsize= 176kB time=00:00:02.40 bitrate=
600.1kbits/s dup=12 drop=0 speed=2.14x
'''no picture ooo
'''
also not printed.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6588#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list