Back Forum Reply New

x264 Rev. 368/368A crashes

x264 and Megui crashes when i'm encoding video.
It happens at the same frame when i try to encode again.
When  i try a different clip it crashes to but at a different frame.
MeGUI crashes to so i don't have a log file   
The problem started when i upgraded to rev 368 from 367D.
It would be nice if someone uploaded build 367D so i can start encoding again  

What options did you choose (copy and paste your cmd line)?
Have you tried ecoding via cli w/o megui?

quot;x264.exequot; --pass 2 --bitrate 4000 --stats quot;.statsquot; --ref 7 --mixed-refs --bframes 3 --b-pyramid --subme 6 --b-rdo --weightb --analyse all  --8x8dct --me umh --progress --no-psnr --output quot;U:\HDTV\Shrek 2\Shrek 2.mkvquot; quot;U:\HDTV\Shrek 2\Shrek 2.avsquot;

Same problem when encoding via CLI and no log file

Overclocked? Memory Problems? I did 2 successful tests with 368 and 1 with 368B with even more extreme settings.

This probably isn't it but have you tried lowering the bitrate to say 2mbps?

It's overclocked but i is 100% stable for 2 months.
The crashes started when i changed from 367D to 368 so the problem should be in x264

well maybe lower your OC and then see. at least that will take that out of the list of problems.

i have no issues with this version of x264 either.

i have tried lowering the resolution from 1280x720 to 720x400 and now the problem is gone

Post you avs file. Seems your source is HD, so it's good to know if (how much) you resize. Also try exactly the same encode, but without --b-rdo and report back if it crashes again (--b-rdo has been tweaked in revisions 368/368A). BTW I just encoded a short 2k frames clip with 368A without any problem.



I have tried changing settings in x264 and it makes no difference.
att resolutions under 1152x640 there is no problems but when the resolution is at or over it crashes att the same frame every time.

Avisynth script:
#  PLUGINS
LoadPlugin(quot;C:\PROGRA~2\GORDIA~1\DGMPGDec\DGDecode.dllquot;)

#  SOURCE
mpeg2source(quot;U:\HDTV\Shrek 2\Shrek 2.d2vquot;)
trim(0,1000)
FDecimate(threshold=1, rate=23.976)
crop(0,0,1280,1080)
Lanczos4Resize(1280,720)

I i encode i att the orginal fps (29,97) i have no problems until 2. pass and there i get this log:

Log for job job1-2

avis [info]: 1280x720 @ 29.97 fps (180 frames)
x264 [warning]: DPB size (22118400) gt; level limit (12582912)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!

---------------------------------------------------------------------------

If i change framerate to 23,976 in either Dgindexby forcing film  or by using decimate in avisynth the encoder quits with no error in 1. pass

Have you tried the same encode, but without --b-rdo? Also in the second pass try to output to quot;Shrek 2.mp4quot; instead of quot;Shrek 2.mkvquot; and see if it crashes again.


Originally Posted by hpnHave you tried the same encode, but without --b-rdo? Also in the second pass try to output to quot;Shrek 2.mp4quot; instead of quot;Shrek 2.mkvquot; and see if it crashes again.

Yes i have tried that.
None of the options in x264 changes anything.
The only thing that has any effect is resolution and Framerate.
I had none problems with rev 387 so if anyone could help me get it i could test if i get the same error with it

You may download rev 386 from
./cd/...revision368.7z

and see if it makes any difference (use directly x264.exe). I guess the celtic_druid's builds are clean svn without patches (right?).

Using celtic_druid's build of 386 there was no error

I tried the same setting with sharktooths build now and the encoding stoppet at frame 77/143 on 1. pass

Settings:
quot;x264.exequot; --pass 1 --bitrate 4000 --stats quot;.statsquot; --bframes 3 --b-pyramid --subme 1 --weightb --trellis 2 --analyse none --me dia --progress --no-psnr --output NUL quot;C:\Shrek 2.avsquot;

Ok, I just reproduced a similar crash with your command line. This time it is not --b-rdo related, so it's some new stuff for the developers to debug.

I'm using the same source
harry_potter_goblet-tlr2_h1080p.mov_track1.mp4 (176'555'616 bytes)

as explained in this post:
showthread.ph...192#post739192

but this time I'm using your command line options:
x264.exe --pass 1 -B 4000 -b 3 --b-pyramid -m 1 -w -t 2 -A none --me dia --progress -o NUL b.avs

also to get a bigger resolution I changed the avs to:Code:
DirectShowSource(quot;F:\harry_potter_goblet-tlr2_h1080p.mov_track1.mp4quot;, fps=23.976, pixel_type=quot;YV12quot;)
#original size 1920x816
trim(120,2302)
so it is now real HD encode, not 1/2 as I did before.

Crash at frame 164.

Changing the trim in avs to:Code:
DirectShowSource(quot;F:\harry_potter_goblet-tlr2_h1080p.mov_track1.mp4quot;, fps=23.976, pixel_type=quot;YV12quot;)
#original size 1920x816
trim(260,2302)
Crash at frame 9.

Both CD's 368 and ST's 368A crash exactly the same way, so it seems not quot;patch relatedquot;.

i have the same problem using the fast firstpass settings of megui when i try rev.368A i will do the the same encode with rev.368 and see (both from sharktooth).
the source is xvid in avi 576x432 frate:23.976HTML Code:
quot;x264.exequot; --pass 1 --bitrate 458 --stats quot;C:\Spirit Stallion Of The Cimarron\2pass.logquot; --keyint 450 --bframes 2 --b-pyramid --filter 1,1 --subme 1 --b-rdo --weightb --analyse none --qpstep 10 --me dia --progress --no-psnr --output NUL quot;C:\Spirit Stallion Of The Cimarron\New.avsquot;
carsh again with rev368

I confirm that ... crash with 1280*720*25 and not with 720*400*25 ...

I just tried again with revision 372. The crashes with the HD source seems fixed   I can't tell by the svn log (369-372) if akupenguin has done some specific work in this direction or because of some other changes to the source (unrelated to the problem) I simply can't reporduce the crashes with the same options, so the HD problem potentially still exists with other sets of options (I hope not).

We think the crashes were caused by the quot;always check mvpquot; patch. r370 used the fixed version.

Thank you!
¥
Back Forum Reply New