[FFmpeg-user] "corrupt decoded frame"
Mark Filipak
markfilipak.imdb at gmail.com
Thu Aug 14 23:19:48 EEST 2025
On 14/08/2025 02.55, Paul B Mahol via ffmpeg-user wrote:
> see -xerror flag ?
I tried it. It's too blunt an instrument, Paul. It aborts on even
trivial errors. Let me explain...
I copy in two steps. Step 1 remuxes. Step 2 transcodes. I previously
posted the commands for Step 1 and Step 2.
I just now,
1, Ran Step 1 (without -xerror) and there were 9956 "Non-monotonic DTS"
warnings [1], and
2, Ran Step 2 (without -xerror) and quit when I got 6 "corrupt decoded
frame" errors in the first 4 minutes of video [2].
[1] There's nothing surprising about "Non-monotonic DTS" warnings. I
_always_ get thousands of "Non-monotonic DTS" warnings on _every_ BD.
That's why I broke the process into two steps. Step 1 is to eliminate
the Non-monotonic DTSes (which I don't believe are real).
[2] "Corrupt decoded frame" errors in Step 2 _are_ new. We, me and Mark
at Xreveal, believe it's a sign of a new AACS or BD+. Step 2 has been
perfect until 'A MAN CALLED OTTO', and it's been perfect since 'A MAN
CALLED OTTO'.
Oh, by the way, I've verified the correctness of the 'A MAN CALLED OTTO'
rip. The errors in Step 2 are not disc read errors.
More information about the ffmpeg-user
mailing list