x264 BD compliant "perfect" settings

[X5gb]

Valeyard, spoRv, I'm a little confused now, do I need to include the threads and the other items Valeyard mentions, also other items in spoRv's script are different in Valeyard's, please both confirm what I need to include, I'm over halway through the encode now and would rather cancel and restart if anything is wrong with the original script.

[spoRv]

Well, those so-called "perfect" settings were studied, tried, examined by many, and they *should* be perfectly BD-compliant; thread setting, AFAIK, must affect only encoding speed.

Even if most probably that weightp set to 1 should not affect BD compliance, but improve a bit overall quality, as our "perfect settings" work well for a lot of us, I'd stick with them for the moment. IMHO!

[Valeyard]

Correct me if I'm wrong, but isn't the command lines executed one after the other?

I mean, if I include --bluray-compat, it will of course set various other commands, but if I place another one AFTER that, that change those commands value, aren't them changed? Or they are simply overridden by the previous one, because is "stronger"?

No, --bluray-compat overrides a few settings that would otherwise break BD compatability, and enforces a couple of BD-specific tweaks. And the preset you use, e.g. "veryslow" is set before everything else no matter where it appears in the commandline.

Valeyard, spoRv, I'm a little confused now, do I need to include the threads and the other items Valeyard mentions, also other items in spoRv's script are different in Valeyard's, please both confirm what I need to include, I'm over halway through the encode now and would rather cancel and restart if anything is wrong with the original script.

The main thing you need to include is the threads, when you do your next encode set the threads to 2x the number of CPU cores and see if your encoding time improves (it should).

[X5gb]

I've decided to restart the encode and include the threads, an extra eight hours is no big deal to me.

[X5gb]

Got the following warning in Simple:

resize [warning]: converting from rgb24 to yuv420p

Should I of picked a different colorspace in lagarith, I left it at the default RGB, or is this normal for Simple to convert.

[spoRv]

Nope, you should select yv12

[deleted user]

Unless you want to preserve full chroma resolution (like I usually do), in which case RGB is the better option. YV12 will give smaller files tho

Edit: You could of course argue that your typical Blu Ray only comes in 4:2:0 anyway, but when you do various processing on it that includes displacing the image in units smaller than 2, arguably you now have "more" information worth preserving just to keep the original quality level. Combine two sources via AutoAlign and you actually have more information, kinda.

[X5gb]

Thanks spoRv and TomArrow, but again a little confused, what should I do, Don't care about the file size being bigger but do I lose anything by leaving the lagarith at RGB and then let x264 do the conversion or should I start over and export from Premiere the lagarith using yv12 and convert again to x264. Sounds like based on what you say TomArrow, leaving as RGB is the better option.

[deleted user]

Well, RGB is essentially completely lossless - aside from rounding errors in converting the original YUV to RGB and possible different coefficients in the conversion in Premiere vs. x264, which you could control with AviSynth:

You can export as RGB and then wrap the resulting lossless RGB Lagarith in an AVS script that converts it to any colorspace you prefer with all the fine tuning you wish to use -> then simply encode that AviSynth script with x264.

Simplest wrapper imaginable: AVISource("RGBLagarith.avi").ConvertToYV24()

That would be for YV24, a 4:4:4 version of the YUV thingy. YV12 also works, but is only 4:2:0. But if you are doing a Blu Ray compatible encode, you can pretty much only use 4:2:0 anyway, so you may as well export straight as YV12 ... questions over questions. But if you already have an RGB export anyway, I'd simply go with that.

Thing is, I personally like to do 4:4:4 encodes. Not Blu Ray compatible, but I never cared.

OR, you know, just check the result and see if the colors look correct compared to the original - if they do, there's nothing further you need to do.

[X5gb]

Thanks, TomArrow.

I'll have a look, once the encode finishes in three hours, but it will be eating at me I haven't done it right and more than likely go back and redo the export as yv12 and encode again.