Which x264 version currently recommended for GUIs?

[stax76]

I was reading about some problems with some new features so I wonder which version is stable enough to be used in GUIs. I've version 1310 atm.

[Dark Shikari]

r1342. If you want a "stable before weightp" revision, that'd be r1318.

[stax76]

weightp is enabled by most presets so I understand you as weightp is stable enough.

[Sharc]

weightp is enabled by most presets so I understand you as weightp is stable enough.
I have done a number of encodes with r1342 including weightp until now and I didn't find any problems. The surprise might more be with those who want to decode/watch the clip with CoreAVC 1.9.5 which fails with --weightp 2, unless they can take advantage of CUDA (nvidia GPU). So you might get some complaints about blocks which however have nothing to do with the stability of x264 with weightp.

[Lyle_JP]

r1342. If you want a "stable before weightp" revision, that'd be r1318.

I know Jeeb's compiled an r1318, which is popular with those who aren't ready to mess with weightp (like me), but I've been using r1319 from x264.nl (which is the last non-weightp they make available).

So, was there anything buggy introduced in r1319 (or is there anything inherently better about Jeeb's compiles) that would make you recommend r1318 over r1319? Or should I stick with what I've been using?

[nm]

How about using the latest version and switching weightp off, if you have players that don't support it.

[Lyle_JP]

How about using the latest version and switching weightp off, if you have players that don't support it.

Well, because I'm using Megui and they haven't created a checkbox for that yet. :o (Yeah, I know, I'm pathetic for not being a CLI lover).

[nurbs]

Put --weightp 0 in the custom command line box on the last tab of the x264 configuration dialog in megui.

[panark]

Put --weightp 0 in the custom command line box on the last tab of the x264 configuration dialog in megui.

I did a test encode using MeGUI 0.3.1.1056 and the latest version of x264 downloaded from x264.nl [x264 core 79 r1354 636f98f].

I disabled (unchecked) the option "Weighted Prediction for B-frames" under the "Frame-type" tab of MeGUI.

I then added this to the custom command line: --weightp 1

"Encoding settings" from MediaInfo gives me: ...../ wpredb=0 / wpredp=1 /.....

Does this mean that weightp is disabled completely or that it is enabled with a value=1?

Thanx in advance.

[buzzqw]

in HDC i can use the most update x264

the profile editing is very simple, just a txt

and.. the default preset are:

X264;1;UltraFast;--preset ultrafast
X264;2;VeryFast;--preset veryfast
X264;3;Faster;--preset faster
X264;4;Fast;--preset fast
X264;5;Medium;--preset medium
X264;6;Extreme Quality;--preset medium --trellis 0 --ref 4 --deblock -1,-1 --subme 9 --direct auto --me umh --b-adapt 2 --no-chroma-me
X264;7;Slow;--preset slow
X264;8;Slower;--preset slower
X264;9;VerySlow;--preset veryslow
X264;10;Placebo;--preset placebo


BHH

[J_Darnley]

Encoding settings" from MediaInfo gives me: ...../ wpredb=0 / wpredp=1 /.....

Does this mean that weightp is disabled completely or that it is enabled with a value=1?

Thanx in advance.

It means you used weightp 1. What does weightb have to do with it?

[LoRd_MuldeR]

I disabled (unchecked) the option "Weighted Prediction for B-frames" under the "Frame-type" tab of MeGUI.

I then added this to the custom command line: --weightp 1

"Encoding settings" from MediaInfo gives me: ...../ wpredb=0 / wpredp=1 /.....

Does this mean that weightp is disabled completely or that it is enabled with a value=1?

You disabled Weighted Prediction for B-Frames (via GUI option) and you explicitly set Weighted Prediction for P-Frames to mode 1 (via CLI parameter).

And that's exactly what you got: You requested weightb=0 plus weightp=1 and MediaInfo verifies that you got weightb=0 plus weightp=1. So what is the question here ???

[panark]

I'm awfully sorry, this was a misunderstanding on my end, i didn't notice the difference between Weighted Prediction for B-frames and P-frames :(

I know understand the difference.

All i wanted to do is manually set "wpredp=1" so that i won't have artifacts when using coreAVC to playback the encoded video.

I did the test encode again with the exact settings (this time "Weighted Prediction for B-frames" is enabled and i've put the following in the command line: --weightp 1) and MediaInfo now gives me: / wpredb=1 / wpredp=1 /

I no longer have artifacts when playing back the video using CoreAVC.

Thanx for the help and the clarification.