View Full Version : x264:rev385D=using megui is 1st pass turbo working?
loveholic
10th December 2005, 22:15
I just tried to encode something using x264's lastest daily build (Megui-x264 in the full package)...
The problem is that in 2pass mode with "turbo" checked, 1st pass is
3hrs long! I uninstalled this build and used 381 build, and the 1st
pass only took 1hr as usual (of course same setting) Nothing fence setting..
I didn't finish encoding with the latest build since i was afraid lol.
I mean with 3hr 1st pass, i would imagine 2nd pass would take about
5-6 hrs...
So my question is: is this normal?
Sharktooth
10th December 2005, 22:45
check the settings.
Doom9
10th December 2005, 23:27
even while encoding there's already some info in the log tab.. it would be really helpful to see that information ;) How's that line again? Oh yeah, no log no service.
loveholic
11th December 2005, 03:00
don't know why i didn't think of checking the logs before..
rev385 with turbo checked
Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 2068 --stats "C:\DVDrip\Scrapped15\test.stats" --keyint 300 --ref 10 --mixed-refs --bframes 3 --filter -2,-1 --subme 6 --b-rdo --weightb --analyse all --8x8dct --qcomp 0.8 --direct none --scenecut 60 --threads 2 --progress --no-psnr --output NUL "C:\DVDrip\Scrapped15\test.avs"
successfully set up video encoder and callbacks for job job1-1
rev381 with turbo checked same setting
Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 2068 --stats "C:\DVDrip\Scrapped15\test.stats" --keyint 300 --bframes 3 --filter -2,-1 --subme 1 --b-rdo --weightb --analyse none --qcomp 0.8 --scenecut 60 --me dia --threads 2 --progress --no-psnr --output NUL "C:\DVDrip\Scrapped15\test.avs"
successfully set up video encoder and callbacks for job job1-1
subme is 1 during 1st pass in 381 while its 6, so turbo not working?
charleski
11th December 2005, 03:26
Yes, that's a problem with commandline generation for turbo mode. There are a lot of things there that should be turned off. Which version of meGUI are you using? (the version number is displayed in the window title when you first run it).
Sirber
11th December 2005, 03:31
It's odd MeGUI got named by it's x264 version ;)
Sharktooth
11th December 2005, 04:48
385 has 0.2.3.1022
loveholic
11th December 2005, 04:50
I'm using MeGUI x264 0.2.3.1022 from sharktooth's x264:rev385D
Full package. I just tried another test, and this is what happens...
If i check "2pass-1st pass" instead of "automated 2pass", 1st pass
subme is 1.
And of course same settings as above logs:
Next job job3 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 2068 --stats "C:\DVDrip\Scrapped15\test.stats" --keyint 300 --bframes 3 --filter -2,-1 --subme 1 --weightb --analyse none --qcomp 0.8 --direct none --scenecut 60 --me dia --threads 2 --progress --no-psnr --output NUL "C:\DVDrip\Scrapped15\test.avs"
successfully set up video encoder and callbacks for job job3
It's the 1st pass using "automated 2pass" that doesn't seem to accept
turbo mode.. I just hope it's not my computer that's causing this problem lol.
Sharktooth
11th December 2005, 04:53
No, maybe there's a bug in the 3-state code since it has been just rewritten.
loveholic
11th December 2005, 04:57
Just did another test...
I replaced the Megui x264 in the r385 full package with the same version in
the Charleski's link, and it's working. 1st pass in "automated 2pass"mode's subme is 1.
Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 2068 --stats "C:\DVDrip\Scrapped15\test.stats" --keyint 300 --bframes 3 --filter -2,-1 --subme 1 --weightb --analyse none --qcomp 0.8 --direct none --scenecut 60 --me dia --threads 2 --progress --no-psnr --output NUL "C:\DVDrip\Scrapped15\test.avs"
successfully set up video encoder and callbacks for job job1-1
I honestly don't know why, but i'm happy it's working lol.
Thanks!
Results are great by the way :D
Sharktooth
11th December 2005, 05:07
what link?
loveholic
11th December 2005, 05:18
This is the link to his post, i got it from "Bin" (http://forum.doom9.org/showthread.php?p=749165#post749165)
Sharktooth
11th December 2005, 05:29
I updated the installer with the charleski binaries.
However, if mine is borked there should be something wrong in the sources charleski posted on the dev thread.
charleski
11th December 2005, 13:06
if (xs.EncodingMode != 2 || xs.EncodingMode != 5)
xs.Turbo = false;
Blame doom9 (http://forum.doom9.org/showthread.php?p=747480#post747480) ! :) (And blame me for not picking up on it, heh.)
Anyway, the error is definitely there in the source, I've posted a patch with the correction. Not sure why the bin I compiled works when it shouldn't, that's strange.
Doom9
11th December 2005, 13:26
uhh, what the heck did you change? EncodingMode = 2 : 2 pass first passs, EncodingMode = 5: 3 pass first pass. Did you mess around in JobUtil? It takes a job with such an EncodingMode, and splits it into two/three, changing the EncodingMode to 2/3 (2 pass first, 2 pass second) and 6/7/8 (or others depending on your 3 pass settings).. but the commandline in any job must never contain EncodingMode = 2 / 5.
charleski
11th December 2005, 13:34
(xs.EncodingMode != 2 || xs.EncodingMode != 5)will always evaluate to true. I changed || to &&.
Doom9
11th December 2005, 14:00
urgh, I must still be asleep :( Shows once more that you always need to test (I didn't test that method, I wrote it without even compiling and knowing it's incomplete.. I hope you completed whatever was missing.. I had to stop coding when the train reached my stop).
charleski
11th December 2005, 14:27
I've done the same thing many times :)
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.