[FFmpeg-trac] #11055(avcodec:reopened): OGOP (Open GOP) in certain conditions may cause missing frames of decoding
FFmpeg
trac at avcodec.org
Sat Jun 22 21:02:27 EEST 2024
#11055: OGOP (Open GOP) in certain conditions may cause missing frames of decoding
-------------------------------------+-------------------------------------
Reporter: markfilipak | Owner: (none)
Type: defect | Status: reopened
Priority: normal | Component: avcodec
Version: git-master | Resolution:
Keywords: everything | Blocked By:
OGOP |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by markfilipak):
Replying to [comment:141 MasterQuestionable]:
> ͏ Not specifically on your file: on OGOP (Open GOP) in general.
> ͏ (rationale explained well before; comment:17 notably)
>
> ͏ "non-monotonous DTS" messages are warning, I believe: mere
indicating the peculiarity of the input timestamps.
>
> ͏ comment:72 explained why and how. ("framecrc" "-vf" etc.)
> \\
> \\
> ͏ Meanwhile, I wonder:
> ͏ Could the origin inputs ("00305.m2ts", "00306.m2ts") be decoded
without similar problem?
> ͏ .
> ͏ Verifiable with alike:
> ͏ `ffmpeg -v debug -hide_banner -nostdin -nostats -i "00305.m2ts"
-map v:0 -c copy -f null -`
> ͏ (shall report the packet count for comparison)
Did you want me to run that command?
I ran this:
ffmpeg -v debug -hide_banner -nostdin -nostats -i c:\00305.m2ts -map v:0
-c copy -f null - 2>"c:\00305.m2ts nostats.txt"
'00305.m2ts nostats.zip' is attached.
A debug log file was not created (?).
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11055#comment:149>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list