Log in

View Full Version : What's wrong with my x264 commands?


VERTIGGO
16th January 2009, 11:30
I am using this batch to compress a vc-1 in .mkv to AVC in .mkv.
I used a "trim" function and successfully pulled 400 frames from the middle and the quality was great, but when I left it overnight on the entire clip, there was no output and the cmd had disappeared (crash i guess). The pc had not restarted.

x264 --pass 1 --bitrate 9500 --bframes 3 --b-pyramid --direct auto --deblock -3:-3 --subme 1 --analyse none --me dia --threads auto --thread-input --progress --no-psnr --no-ssim -o NUL HDDVD.avs

x264 --pass 2 --bitrate 9500 --progress --threads auto -b 3 --b-bias 5 --b-pyramid --weightb --subme 6 -8 -t 1 -o "C:\_RIPPED\HDDVD Hybrid.mkv" HDDVD.avs
pause

Is there something obviously wrong with this code or would it be codecs or do I need to blame the overclock or something?

Thanks!

dat720
16th January 2009, 15:01
Are you sure the PC didn't restart? cos even if x264 crashed the command window should still be there with that pause command waiting for you to press any key.

VERTIGGO
16th January 2009, 17:10
taskmanager was running (the only other process) so cmd crashed or ended, with no output but the pc didn't crash.

Currently I'm halfway through this code:

x264 --pass 1 --bitrate 9500 --progress --threads auto -b 3 --b-bias 5 --b-pyramid --weightb --subme 1 -8 -t 1 -o NUL HDDVD.avs

x264 --pass 2 --bitrate 9500 --progress --threads auto -b 3 --b-bias 5 --b-pyramid --weightb --subme 6 -8 -t 1 -o "C:\_RIPPED\HDDVD.mkv" HDDVD.avs
pause

The difference to me is that the first code ran much faster, which I don't understand. I used these from a guide here but had to replace the bime and rdo commands with subme 6 etc. because of the new x264.

nurbs
16th January 2009, 20:08
In your first post you didn't have trellis on in the first pass end you used --me dia, the default is hex. That's why it's faster.