x264 slightly broken?!

[meimeiriver]

Yes, I know it sounds unlikely, but recently I got several errors like these (Blu-Ray):

[h264 @ 00000280112c7740] concealing 698 DC, 698 AC, 698 MV errors in B frame

At first I thought it was really the source, but now I'm wondering whether this is a bug somehow inside x264?! I did several checks, like

eac3to saturn3.mkv -check

Or, more rigorously,

ffmpeg.exe -v error -i saturn3.mkv -f null - >error.log 2>&1

Neither reports any error in the source. And I've had more of these spurious errors of late (whereas I had none before). I run x264 core:148 r2665 a01e339 (64-bit).

[LigH.de]

This error message looks to me like it reports decoding errors from the video source which seems to be in H.264 format on the original Blu-ray. So the H.264 encoder used in their Blu-ray video studio may be not completely correct (and I doubt they used x264 in this case).

[meimeiriver]

This error message looks to me like it reports decoding errors from the video source which seems to be in H.264 format on the original Blu-ray. So the H.264 encoder used in their Blu-ray video studio may be not completely correct (and I doubt they used x264 in this case).

That is an excellent explanation!

At any rate, I watched the entire (re-encoded) Blu-Ray last night, and could not detect any visible distortions. Odd.

[El Heggunte]

[h264 @ 00000280112c7740] concealing 698 DC, 698 AC, 698 MV errors in B frame

Does that message come from MPlayer, or ffplay

If the answer is "yes", then that's 'normal'

[meimeiriver]

[h264 @ 00000280112c7740] concealing 698 DC, 698 AC, 698 MV errors in B frame

Does that message come from MPlayer, or ffplay

If the answer is "yes", then that's 'normal'

Now that I'm awake, and had my coffee again, I actually suspect it's coming from LWLibavVideoSource, which uses FFmpeg (libavcodec), and not from x264 really (always hard to tell, as the terminal output of x264 and ffmpeg kinda show up on the same page; which is to say, I think the ffmpeg component of LWLibavVideoSource just clobbered its error over the x264 progress). Because that really looks like an ffmpeg style error message.