Log in

View Full Version : x264 warnings


Ranguvar
13th July 2008, 14:52
I'm doing the second pass of a 2pass encode of Black Hawk Down, ripped from a Blu-ray disc (MPEG-2). I have a quad-core Q6600 CPU, and 2GB of RAM.

I'm using bob0r's modified r912 build: http://forum.doom9.org/showthread.php?p=1158308#post1158308

I'm using AviSynth MT v0.7.

My AviSynth script:
LoadPlugin("C:\AVSplugins\MT.dll")
LoadPlugin("C:\AVSplugins\DGDecode.dll")
LoadPlugin("C:\AVSplugins\ColorMatrix.dll")

SetMTMode(2, 0)
MPEG2Source("C:\BLACK_HAWK_DOWN\Vid.d2v", info=3)
ColorMatrix(hints=true)
Crop(2, 140, -2, -140).BicubicResize(832, 352)

My x264 CLI:
x264.exe --keyint 240 --min-keyint 24 --bframes 5 --b-pyramid --deblock 0:-1 --bitrate 920 --pass 1 --stats "Vid.stats" --partitions none --direct auto --me dia --subme 2 --output "1pass.mp4" "Vid.avs" --level 3.1 --progress --threads auto --non-deterministic

x264.exe --keyint 240 --min-keyint 24 --bframes 5 --b-pyramid --ref 5 --mixed-refs --deblock 0:-1 --bitrate 920 --pass 2 --stats "Vid.stats" --partitions p8x8,b8x8,i8x8,i4x4 --direct auto --weightb --me umh --merange 32 --subme 7 --b-rdo --bime --8x8dct --trellis 2 --no-fast-pskip --output "Vid.mp4" "Vid.avs" --level 3.1 --progress --threads auto --non-deterministic

I don't know if any errors occurred during the first pass, but the video from the first pass seems OK.

The 2nd pass is nearly done, and x264 is reporting warnings, for example, here's a few:

x264 [warning]: recovering by using intra mode
x264 [warning]: internal error (MV out of thread range)20:59
mb type: 7
mv: l1r0 (225,272)
limit: 224
mb_xy: 22,8
completed: 184
x264 [warning]: recovering by using intra mode
x264 [warning]: internal error (MV out of thread range)
mb type: 7
mv: l1r0 (225,272)
limit: 224
mb_xy: 23,8
completed: 184
x264 [warning]: recovering by using intra mode
x264 [warning]: internal error (MV out of thread range)
mb type: 7
mv: l1r0 (-86,191)
limit: 160
mb_xy: 23,12
completed: 232
x264 [warning]: recovering by using intra mode
x264 [warning]: internal error (MV out of thread range)15:05
mb type: 7
mv: l1r0 (-81,214)
limit: 160
mb_xy: 21,17
completed: 312
x264 [warning]: recovering by using intra mode
x264 [warning]: internal error (MV out of thread range)14:12
mb type: 7
mv: l1r0 (-88,166)
limit: 224
mb_xy: 11,11
completed: 216
x264 [warning]: recovering by using intra mode
encoded frames: 141185/207624 (68.0%), 8.59fps, eta 2:08:52

check
13th July 2008, 15:03
It's an x264 error, caused by a motion vector being returned which is referencing a macroblock not actually encoded yet (iirc). x264 has code to detect this and falls back to encoding the block as intra (instead of crashing). They won't really affect the output stream much at all, it's only a few MBs out of the entire movie. Getting that many in a single stream is unusual though.. can you replicate the issue?

Ranguvar
13th July 2008, 15:15
It's an x264 error, caused by a motion vector being returned which is referencing a macroblock not actually encoded yet (iirc). x264 has code to detect this and falls back to encoding the block as intra (instead of crashing). They won't really affect the output stream much at all, it's only a few MBs out of the entire movie. Getting that many in a single stream is unusual though.. can you replicate the issue?
There's tons more, and new ones occur every minute or two.

Replicate as in encode again, and get the same error? Well, I'll see, after this is done encoding... Or do you mean using a different source?

Dark Shikari
13th July 2008, 17:05
This goes back to an old issue where in some very rare cases x264 would somehow end up past its "threading limit" and have motion vectors that are too long, resulting in a crash.

Instead, I added a failsafe to make it drop back to intra instead in such a case.

I'm going to guess that --non-deterministic might aggravate this.

Ranguvar
13th July 2008, 19:01
Alright, I need to re-encode anyways with a higher bitrate, so I'll take off --non-deterministic. Thanks.

CruNcher
13th July 2008, 23:15
Are you encoding this for the PSP ?

Ranguvar
14th July 2008, 00:36
With 5 refs, 5 b-frames, b-pyramid, i8x8, 8x8dct, and a resolution of 832x352? Nope :P