PDA

View Full Version : Convert X264 "Encoding settings" to a MeGUI profile


[ReX]
7th September 2008, 01:11
There's a easier to convert "Encoding settings" (in MediaInfo) to MeGUI profile other than manually?

Example:
cabac=1 / ref=3 / deblock=1:-3:-2 / analyse=0x3:0x113 / me=umh / subme=6 / brdo=1 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=0 / threads=1 / nr=0 / decimate=1 / mbaff=0 / bframes=2 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / wpredb=1 / bime=1 / keyint=15 / keyint_min=1 / scenecut=40 / rc=2pass / bitrate=1235 / ratetol=1.0 / rceq='blurCplx^(1-qComp)' / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=29400 / vbv_bufsize=9781 / ip_ratio=1.40 / pb_ratio=1.30

Maybe someone can code a utility to do that... :p

martino
7th September 2008, 02:31
Couldn't you just do a replace of "/ " to "--" and feed that to x264 (and add pass1/2/we differences)?

EDIT: Oh... you want MeGUI... nm then.

Sharktooth
7th September 2008, 02:39
actually, no.

[ReX]
7th September 2008, 22:45
Couldn't you just do a replace of "/ " to "--" and feed that to x264 (and add pass1/2/we differences)?

EDIT: Oh... you want MeGUI... nm then.

But some of them aren't the same thing at command line.

Ranguvar
8th September 2008, 01:29
;1180798']But some of them aren't the same thing at command line.

Um, yeah, they are... MeGUI just uses x264.exe command-line...

Replace all /{SPACE} with --, and replace all = with a space... got yourself a CLI...

Sharktooth
8th September 2008, 02:04
nope... expecially for the listboxes...

J_Darnley
8th September 2008, 02:41
Um, yeah, they are... MeGUI just uses x264.exe command-line...

Replace all /{SPACE} with --, and replace all = with a space... got yourself a CLI...

No. All of the following will fail. x264 doesn't like underscores, deblock is not specified like that, neither are deadzones, and interlaced encoding, weighted b frame, rate control and rceq is an obsolete option.

What really surprised be is that you can actually specify --analyse in this manner 0x3:0x113

deblock=1:-3:-2
mixed_ref=1
me_range=16
chroma_me=1
cqm=0
deadzone=21,11
chroma_qp_offset=0
decimate=1
mbaff=0
b_pyramid=1
b_adapt=1
b_bias=0
direct=3
wpredb=1
keyint_min=1
rc=2pass
rceq='blurCplx^(1-qComp)'
vbv_maxrate=29400
vbv_bufsize=9781
ip_ratio=1.40
pb_ratio=1.30

Anyway, in the time that we have all been discussing this, the OP could have already created his own MeGUI settings using MeGUI.

Comatose
9th September 2008, 16:21
It doesn't really take that long, but it would be nice to be able to paste a commandline in MeGUI's config window and have MeGUI modify the options in the window.

[ReX]
12th September 2008, 18:34
No. All of the following will fail. x264 doesn't like underscores, deblock is not specified like that, neither are deadzones, and interlaced encoding, weighted b frame, rate control and rceq is an obsolete option.

What really surprised be is that you can actually specify --analyse in this manner 0x3:0x113

deblock=1:-3:-2
mixed_ref=1
me_range=16
chroma_me=1
cqm=0
deadzone=21,11
chroma_qp_offset=0
decimate=1
mbaff=0
b_pyramid=1
b_adapt=1
b_bias=0
direct=3
wpredb=1
keyint_min=1
rc=2pass
rceq='blurCplx^(1-qComp)'
vbv_maxrate=29400
vbv_bufsize=9781
ip_ratio=1.40
pb_ratio=1.30

Anyway, in the time that we have all been discussing this, the OP could have already created his own MeGUI settings using MeGUI.

Yes, i could but that's not my point.