Log in

View Full Version : x264 crashed because of uTorrent ? (Was using MeGUI)


Ð.Sp!dér
17th February 2007, 21:48
So I pulled a free fansub (anime) off bt via uTorrent and figured I might as well try to encode it. I guess I was pretty bored and wanted to try something new with my spare time. Anyway, not many people were leeching this. No, actually there was nobody leeching at that time. So the encode went smoothly. 1st pass went by quick, then 2nd pass. Somewhere around the middle of the 2nd pass x264 crashed.

I'm using WinXP SP2 and it gave me a nasty Send/Don't send error saying that x264 crashed. I don't know if it's a MeGUI bug or if it has something to do with the x264 codec itself. I just thought I'd report it.

(AthlonXP 2200+ @ 1.800 Mhz)
Looking for job processor for job...
Processor found!
Starting job job1-1 at 7:06:44 PM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
--pass 1 --bitrate 433 --stats "D:\Encodes\01.stats" --bframes 3 --b-pyramid --direct auto --filter 1,1 --subme 1 --analyse none --me dia --thread-input --progress --no-psnr --no-ssim --output NUL "D:\Encodes\01.avs"
successfully started encoding
Processing ended at 7:32:01 PM
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [info]: 640x352 @ 23.98 fps (35446 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:277 Avg QP:16.23 size: 29643
x264 [info]: slice P:10671 Avg QP:19.02 size: 4887
x264 [info]: slice B:24498 Avg QP:20.11 size: 806
x264 [info]: mb I I16..4: 26.0% 0.0% 74.0%
x264 [info]: mb P I16..4: 11.5% 0.0% 0.0% P16..4: 48.8% 0.0% 0.0% 0.0% 0.0% skip:39.8%
x264 [info]: mb B I16..4: 0.3% 0.0% 0.0% B16..8: 9.1% 0.0% 0.0% direct:14.4% skip:76.2%
x264 [info]: final ratefactor: 22.88
x264 [info]: direct mvs spatial:99.9% temporal:0.1%
x264 [info]: kb/s:433.5

encoded 35446 frames, 23.58 fps, 433.53 kb/s

----------------------------------------------------------------------------------------------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Postprocessing finished!
Looking for job processor for job...
Processor found!
Starting job job1-2 at 7:32:01 PM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
--pass 2 --bitrate 433 --stats "D:\Encodes\01.stats" --ref 8 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --direct auto --filter 1,1 --subme 7 --trellis 2 --analyse all --8x8dct --me umh --thread-input --progress --no-psnr --no-ssim --output "D:\Encodes\01.mkv" "D:\Encodes\01.avs"
successfully started encoding
Processing ended at 9:37:37 PM
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [info]: 640x352 @ 23.98 fps (35446 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!

----------------------------------------------------------------------------------------------------------
The current job contains errors. Skipping chained jobs

Btw, I had the file clicked. In Explorer that is... (Not IE) I mean, the file was selected, and Windows was displaying a little preview on the left side of the window... Meaning Windows partially opened the file. But it didn't modified it, did it ? :-/

My best guess is that it happend because the file was modified. You know ? Some attributes do get changed...
Right click - Properties shows me "Modified: Today, February 17, 2007, 11:45:53 AM" did that caused the crash ? It never happend before so that's why I'm asking. This is the first Send/Don't send crash I've had in quite a while.

Poor me... :'(

LE: Haali Media Splitter (31.01.2007) was trying to read from an old OGM container via Avisynth v2.5.7 ...
# Set DAR in encoder to 37 : 20. The following line is for automatic signalling
global MeGUI_darx = 37
global MeGUI_dary = 20
DirectShowSource("D:\Encodes\x01.ogm",fps=23.9759856527702,audio=false)
#deinterlace
#crop
Spline36Resize(640,352) # Spline36 (Neutral)
#denoise

check
18th February 2007, 02:01
Other programs should have no effect upon x264, unless you are doing something along the lines of overwriting the output or stats file with said program.
Please also be aware than fansubs violate rule 6, so don't come back and ask for help with them later :^)

bond
18th February 2007, 13:33
closed for rule 6