MeGUI Presets discussion

[Sharktooth]

Once we used to have multiple presets for multiple target. Today we have the "Quality/speed" slider that adjusts most of the x264 settings... but... I feel the new x264 presests for MeGUI are really... crap.
If you have any suggestions OR you find some errors in current presets, don't hesitate to write them down here.
Thanks

[Atak_Snajpera]

Who needs "100" presets? Look at ripbot. 4 profiles and everybody is happy.
[BASE 3.0] iPOD . iPhone . Zune
[BASE 3.1] AppleTV
[MAIN 3.0] SD . PSP . iPAD
[HIGH 4.0] HD . BluRay . Consoles

[Sharktooth]

i guess you're right but... look at megui and think again.
megui lets you tweak everything (or almost), why would you use simplified/stripped down presests that "works" but cant squeeze the juice out of your device?

[Audionut]

While you were away, the x264 devs changed the behavior of the cli. It now includes --profile --preset and --tune options.

The idea was to do away with gui's. Cause quite frankly, megui fell to shite again when you left for quite awhile and before Zathor took it over.

The slider you are talking about is simply a --preset (read: speed adjuster) of the cli.
http://img341.imageshack.us/img341/7673/x264t.png

There are still hardware based presets available in megui.
BTW, the x264 devs will soon be adding a --device option to the cli.

[Atak_Snajpera]

but cant squeeze the juice out of your device?
examples?

[Sharktooth]

@audionut: i know about the --profile, --preset, --tune... and the addition of --device.
the idea is to move those options in the main configuration page of the encoder and have a checkbox to show the advanced settings to tune up manually.
the problem however is different... look at the xbox360 preset... now, tell me if in your opinion that will work without buffer restrictions... im not even sure xbox360 supports b-pyramid... go figure...

[Audionut]

The only thing that doesn't support b-pyramid from memory was the psp. So it was decided to add it as a default option due to it's benifits, much to the disgust of a few psp owners that complained about having to turn it off manually for that 1 device.

[Atak_Snajpera]

the problem however is different... look at the xbox360 preset... now, tell me if in your opinion that will work without buffer restrictions... im not even sure xbox360 supports b-pyramid... go figure...
HD profile works on every device. BLU-RAY/PS3/XBOX360/DXVA/WD/POPCORN/AND so on ...
BTW . I always disable b-pyramid because it may only cause decoding problems and quality does not suffer at all. (unless you are not human)

The only thing that doesn't support b-pyramid from memory was the psp.
Maybe i'm wrong but i think that b-pyramid belongs to HIGH profile. PSP supports only MAIN. So no wonder that it does not work.

[Audionut]

Oh and yes, I don't own an xbox360 but it's got something like a 10mbps limit right. Where are the buffer restrictions indeed.
Imo all this will be fixed with the --device option.

TBH, I think gui's will be a tool for people who can't enter a simple command line like

x264 --tune film --device xbox360 --crf 20 -o x:\output.mkv x:\input.whatever

BTW, x264 accepts nearly any input now, and will soon have inbuild resize and crop functions.

The devs are also planing to add audio encoding. Personally I think that's beyond the scope, but will make the cli and all in one encoding solution.

[Atak_Snajpera]

The devs are also planing to add audio encoding. Personally I think that's beyond the scope, but will make the cli and all in one encoding solution.
No need to invent a wheel again. FFMPEG does that already ;)

[Audionut]

BTW . I always disable b-pyramid because it may only cause decoding problems and quality does not suffer at all. (unless you are not human)

It was brought to forum consensus ages ago. Virtually every device known was tested and the only thing that failed was the psp.

Why disable something based on an assumption "because it may", particularly considering that it was tested well before being enabled by default.

HD profile works on every device. BLU-RAY/PS3/XBOX360/DXVA/WD/POPCORN/AND so on ...

Yes, but devices have bitrate limits. And if a preset, profile whatever isn't limiting the bitrate?

[Atak_Snajpera]

Virtually every device known was tested and the only thing that failed was the psp.
PSP does not support high profile! ONLY MAIN. I remeber that xbox 360 had some problems with b-pyramid.

Yes, but devices have bitrate limits. And if a preset, profile whatever isn't limiting the bitrate?
Most HD devices are at least 4.0 compatible. Besides who will encode at 25MBps (level 4.0 limit ;)

[Audionut]

PSP does not support high profile! ONLY MAIN.

b-pyramid is enabled in main profile.

Most HD devices
Besides who will encode at 25MBps (level 4.0 limit ;)

That's a large assumption based on the fact that a fair percentage of users using a gui do so cause they don't know or understand x264 options or the cli.

And the xbox360 has a limit of 10mbps right.

[nurbs]

PSP does not support high profile! ONLY MAIN.Which has nothing to do with b-pyramid. I remeber that xbox 360 had some problems with b-pyramid.You remember it wrong (http://forum.doom9.org/showthread.php?t=152761).

[Atak_Snajpera]

You remember it wrong.
So new firmware must fixed that or newer x264.

And the xbox360 has a limit of 10mbps right.
If I had x360 i would just check if 10mbps+ works...

[Sharktooth]

the old preset i made had 24000 bps buffer and maxbitrate limit. but there were several updates to the xbox360 firmware... and it doesnt lack the hardware capabilities...
however, as i said, every device has its own limit. including video cards.
some have DXVA that supports level 4.1 others have no restrictions... in this case, differencies are negligible but an example is you have the same (main) profile for PSP and iPad IIRC supports HIGH profile with some limitations and since the iPad display is way bigger that the one on a PSP you're crippling the iPad quality just coz you want to have 4 presets and no dedicated ones.
that could be acceptable for ripbot or staxrip or easy-to-use GUIs, but megui is not made for that purpouse. it's for the power users and ppl who want to learn.
the subsequent step is CLI (and batch files)...

[Audionut]

If I had x360 i would just check if 10mbps+ works...

Honestly, I personally don't use ripbot, but I'm sure many users are grateful for your contribution with your program.

But seriously, how on earth can you have a console preset that you don't know if it's compatible or not?

And as Sharktooth points out, the ipad supports high profile. I can only guess that you limit it for users who transfer their files with itunes.

[Atak_Snajpera]

But seriously, how on earth can you have a console preset that you don't know if it's compatible or not?
Well I have support from users ;) Personally I have PSP and i had access for some time to PS3 and Samsung blu-ray players.

since the iPad display is way bigger that the one on a PSP
WOW! Shity iPAD has amazing 4:3 resolution of 1024x768. it is not even a HD. I would just save space and used 720x576 (or 1024x576 if you don't like anamorphic resolutions)

[Sharktooth]

That's the reason i created this thread. I wish to know the limitations for several devices and eventually create a preset for megui until the --device option will be available in x264.

[Audionut]

I would just save space and used 720x576 (or 1024x576 if you don't like anamorphic resolutions)

But what if a user wants something different?

Forgive me as i've never developed a gui before, but I would have assumed that you wouldn't limit a users options based on your own ideals.

[Audionut]

create a preset for megui until the --device option will be available in x264.

Honestly, afaik DS is pushing for the support patches for the --device option fairly hard. I wouldn't be surprised to see --device in x264 very soon.

It is worth the effort to compile the list yourself and code the gui for such little time benefit!

[Sharktooth]

But what if a user wants something different?

Forgive me as i've never developed a gui before, but I would have assumed that you wouldn't limit a users options based on your own ideals.
the point is, there is already a GUI for the "tweakers".
Ripbot is fine as it is coz it just fits for the beginner, the average and even some pro users.
MeGUI is not for the beginners... and hardly for the average. So everything fits in its own place.

[Atak_Snajpera]

But what if a user wants something different?
Like stupid 1280x720 which would be always downscaled on iPAD?


Forgive me as i've never developed a gui before, but I would have assumed that you wouldn't limit a users options based on your own ideals.
You can always create your own profile if you are not happy with defaults. Profile in contrast to megui is just a plain .txt file.

but megui is not made for that purpouse. it's for the power users and ppl who want to learn.
Yes I know. Almost everything must be done manually ;)

[Sharktooth]

Exactly. So, look at it as a learning software... it doesnt make it easy for you, but at least it is a tool that connects all what you need in a single program.
If you think at it that way, once you learn how to do things in MeGUI you will automatically know what software you need and what to do if you have to do an encode "manually".
So, MeGUI doesnt "help" you making the biz easy, but just have shortcuts to make you do your stuff faster.

Edit: ... and one of those shortcuts are presets...

[Atak_Snajpera]

My philosophy is that Graphic User Interface is supposed help user with his task. Example. How many of you use command line DVD/CD burning program (cdrecord.exe for example) and how may of you use imgburn/nero/Windows burning system? Another problem is MEGUI also rely on DirectShow codecs but it does nothing to fix any problems with codecs. For example. It does not check if ffdshow is forced in Windows 7 as default decoder for AVC/vc-1/mpeg2/ and so on. For optimal vc-1 decoding ffdshow must be set for wmv9 instead of libavcodec (interlacing decoding is not supported in libavcodec)

[Audionut]

Like stupid 1280x720 which would be always downscaled on iPAD?

You think that's more stupid than,

and used 720x576

And have the device upscale instead:confused: So instead of shrinking any artifacts and making them harder to notice, you propose to enlarge them?

Wow, Just Wow. Bye.

[Sharktooth]

Honestly, afaik DS is pushing for the support patches for the --device option fairly hard. I wouldn't be surprised to see --device in x264 very soon.

It is worth the effort to compile the list yourself and code the gui for such little time benefit!
DS first talked of the --devices support several months ago, even before i had my health problems.
it's still missing... however it would be not a big problem adding a new option and converting the presets.

[Sharktooth]

My philosophy is that Graphic User Interface is supposed help user with his task. Example. How many of you use command line DVD/CD burning program (cdrecord.exe for example) and how may of you use imgburn/nero/Windows burning system?
i usually burn CD/DVDs from linux but it's also hard i burn them... so i hardly use GUIs. i just mount the iso filesystem in a directory and...

edit: however, you know there are 2 philosopies about GUIs... one is yours, the other is mine.
you will find the same differencies about, for example, windows and desktop for linux.
windows makes things easy... kde, for example, exposes a lot of options...
users must have a choice. no one is "right" in this discussion and that's why i always supported other GUIs other than MeGUI... and that's why if a user doesnt understand what to do i usually point him to ripbot or staxrip of auto*** (damn they're too much), etc.

[Atak_Snajpera]

And have the device upscale instead So instead of shrinking any artifacts and making them harder to notice, you propose to enlarge them?
ideally you should use 1024x....

[Audionut]

DS fist talked of the --devices support several months ago,

Yeah, it was planned to be done around the start of march I believe. AFAIK, blu-ray support took precedence and was a PITA.

[Sharktooth]

who wrote the blu-ray specs was a psycho...

[Audionut]

ideally you should use 1024x....

Of course, and getting back to the original discussion, afaik, high profile nets you about %10 better compression.

Which, in turn, if you were shooting for lowest bitrate,

I would just save space and

You would want to enable. Ok, this will cause some, Hey, itunes doesn't support files encoded by your gui. But surely, encouraging users to dump the crap ass apple software in favor of vastly (atleast 10%) increase in quality of their encodes for no effort at all, is a good thing!

[Audionut]

who wrote the blu-ray specs was a psycho...

Yeah, apparently, lol.

Due to a staggering display of braindamage in the Blu-ray spec

http://git.videolan.org/?p=x264.git;a=commit;h=40c8c4926a78a705c263e042a780d63ca24687f4

I believe there's a few more references like that in other blu-ray specific commits.

[Sharktooth]

LOL... im not alone then...

@atak_snajpera: i have edited my post after you replied... http://forum.doom9.org/showthread.php?p=1415122#post1415122

[Atak_Snajpera]

who wrote the blu-ray specs was a psycho...
amen brother! Thank god that AVCHD is not that ridiculous. No need to use slices. Even long gop works :)

[shon3i]

Even long gop worksIt works but not by spec.

AVCHD is more restrictive and ridiculous than Blu-Ray.

Things that worked for you (and other people) is just because most players follow full H264 specs not AVCHD or Blu-Ray

[Atak_Snajpera]

Things that worked for you (and other people) is just because most players follow full H264 specs not AVCHD or Blu-Ray
true. This explains why DTS is still supported in AVCHD by players;) BTW. AVCHD was designed at the begining mainly for HD camcorders.

[FraGTaLiTy]

I can't get my old presets to work after the update even when I re-add them afterwards. Is anyone else having this problem? And if so, will it be fixed in a future update?

[Sharktooth]

The problem comes from a change in the latest build (it's a development build after all...). That's due to the NAL-HRD option that became an integer (it was a boolean). So the OLD presets cant be read.
As i posted in the MeGUI patched build treads that update broke the old presets. However MeGUI should have made a backup of your old presets. So open the presets, find the HRD option and change it from "true" or "false" into ,respectively, "1" or "0", then save the file and put it back into the appropriate folder.

[Zathor]

I can't get my old presets to work after the update even when I re-add them afterwards. Is anyone else having this problem? And if so, will it be fixed in a future update?
Yes, there will be an upgrade path in one of the next builds so that the stable build users wont have this problem.

[Sharktooth]

Just did an overhaul to the x264 presets (that's for the dev version of megui).

[Sharktooth]

A whole bunch of new presets are available for the dev version of MeGUI.

[Emp3r0r]

I like the quality speed slider and don't think it is "crap"

I just want to choose a profile and then choose really slow settings :)

[Sharktooth]

i didnt meant that. i meant the presets are not what they used to be ...

[WorBry]

Thanks for the new Blu-Ray presets in Tx264 version 4.7

Minor typo - Blu-Ray 567p25 probably should be 576p25 ?

Would this preset also be suitable for 576p50 e.g a bob-deinterlaced Pal SD source?

Edit: Might be nice if the SD presets included respective sar values for standard (4:3) and anamorphic (16:9) sources, although easy enough to add to the command line oneself.

Edit2: ...but there again, that would mean 8 separate presets just for SD sources....so probably better to leave (as you have done) at default SAR 1:1 and let folks modify as they wish.

Also, the 576p50 query is maybe misplaced, as these are 'BluRay compliant' presets after all. Although, one wonders why the BluRay spec doesn't make provision for SD 50p/60p streams, as they seem to play OK on many BD standalones.

[Sharktooth]

yep, a typo... new presets are coming though ;)
Sadly 576p50 is not allowed in the BD specs. but maybe you can fool it by adding the --fake-interlaced flag (now there is a checkbox to add it).
About AR, adding them will double the presets... maybe i'll add an AR control in the x264 config window.

[Sharktooth]

New presets uploaded. More Blu-Ray presets and some fixes.

[WorBry]

Sadly 576p50 is not allowed in the BD specs. but maybe you can fool it by adding the --fake-interlaced flag (now there is a checkbox to add it).

I was wondering about that.

... maybe i'll add an AR control in the x264 config window.

Great, that would be useful. While you are at it, any possibility of the same for the colormatrix, colorprim and transfer parameters ?

[Sharktooth]

yes. i was just wondering if there is need for 3 separate controls for colormatrix, colorprim and transfer options or just one that sets those 3 to the same value.

[WorBry]

Separate control might be preferable since the original production color primaries and transfer characteristics of the source may not be known and cannot necessarily be assumed.

I guess that poses a bit of a dilemma for your presets though. Is it 'safer' to 'assume' or 'not assume'? Most of my material is self-produced camcorder footage, in which case it's reasonable to assume that the three parameters are the same. I dunno, what do other folks think?

Edit: Out of interest, what do BD players (typically) 'assume' when the colormatrix is defined, but the colorprim and transfer info is not?

[chris.beswick]

Is there something wrong with the --presets and --tune offered by the current builds of x264.exe, or is it just that the current MeGUI doesn't support working "that way"?

[Lyle_JP]

Is there something wrong with the --presets and --tune offered by the current builds of x264.exe, or is it just that the current MeGUI doesn't support working "that way"?

Not sure what you mean by "current MeGUI", but the current dev build of MeGUI (0.3.5.3) uses the tunings and presets of current x264 builds. The "speed slider" chooses the --preset value, and if you need a certain --tune, just use the Tunings drop-down box.

[chris.beswick]

Not sure what you mean by "current MeGUI", but the current dev build of MeGUI (0.3.5.3) uses the tunings and presets of current x264 builds. The "speed slider" chooses the --preset value, and if you need a certain --tune, just use the Tunings drop-down box.

Aww my problem seems to be being clueless, I've not really used MeGUI, I'm really looking at how the profiles that are being referenced to here are being decided upon. From what I can tell the "slider" does set the --preset and the dropdown the --tune but it seems to change / add other settings to the list below as well.

Really what I'm looking for is a "profile" for lets say blu-ray 1080p, which will ensure that my preset and tune etc are tweeked to ensure compatability (for example adding colormatrix's aud max bitrates etc, but not changing the settings that do not effect compability and relate to the speed/quality of the encode)

[Sharktooth]

x264 config window is being reworked as we speak. however, rest assured when it will be finished, the "advanced options" will be set after the "--preset" and "--tune" options, so it will be possible to have, for example, --preset placebo --ref 3 a working combination. now the problem lies with the "default" settings, so for example --ref 3 is not in the generated commandline coz it's the default and it makes megui unable to generate previous example (--presest placebo --ref 3)...

[alexcel]

HI:

I am a rather unexperienced encoder, so I have some basic questions about new presets. Basically because I use them as I guide to my encodings

So, here we go:

1.- In previous versions, megui presets switched to crf encoding. I understood that as a hint so as the new preferred encoding should be one-pass crf. Now we are back to 2-pass enconding...Are you recommending 2-pass instead of one-pass crf? What do you recommend as a general rule?

2- Both DXVA presets HD and SD share the same bitrate 1000. I understood that 1000 was a nice bitrate to happy SD encodings, and I have been encoding at that bitrate since the beginning. Now your DXVA HD preset is targeted at 1.000 and your DivX HD at 10.000. I'd rather suggest to have both presets sharing a "recommended" bitrate in their presets...someting like 6.000 bitrate.

I know that everybody can change this values while configuring the encode, but many users like me just simply use the values defined in the presets as "the best you can use if you do not know enough"

Thanks for your help. I am really grateful for your work

[Sharktooth]

1- it's not a matter of recommendation. it's a matter of filesize. if you're encoding to fill a DVD (for example BD5 and BD9 presets) you need two passes. Same story for Blu-Ray... filesize is a costraint. For other devices PSP, IPod etc... usually there are SD cards or other memories with fixed capacity, so filesize matters again...

2- bitrate is not indicative in presets since most users would use the auto-encode feature. however, yes, i forgot to update those presets bitrates ;)

[hubereevez]

PSP preset seems to be broken...

[Zathor]

In previous versions, megui presets switched to crf encoding. I understood that as a hint so as the new preferred encoding should be one-pass crf. Now we are back to 2-pass enconding...Are you recommending 2-pass instead of one-pass crf? What do you recommend as a general rule?

CRF encodings are the way to go if file size does not matter. As soon as you define somewhere in MeGUI a specific target size the encoding mode will automatically be switched to 2/3pass mode (depending on your default settings) with the calculated bitrate to match this desired file size.

Therefore the default encoding mode in the profiles is CRF.

[Lyle_JP]

I have been doing some testing with Open GOP on r1666 and have come to some conclusions regarding PS3 compatibility. This could be important since Dark Shakiri has hinted that GOP Normal could soon be the default setting for x264 in the future. If that is to be the case then the PS3 profile in MeGUI will need some changes.

My conclusion: Don't use --open-gop if you intend to play the file on a PS3. Although you will create a spec-compliant mp4 file that will technically play back without error, if you try to fast forward, rewind, or use the Square button to seek to a time, you will hang up playback. Thankfully, it doesn't crash the player as the stop key will still work, but once you stop the movie, odds are you will be tossed back to the beginning if you try to play it again.

So, long story short, if encoding for the PS3, don't use --open-gop. Period Although you can play back a file with --open-gop, all seek features seem to be disabled.

[Underground78]

PSP preset seems to be broken...

Hum I'm not sure the preset itself is really broken. I think it's more a problem caused by Megui because as "--ref 3" is default, "--ref 3" is not added to the command line even if the preset is changed to something else than medium.

[hubereevez]

Hum I'm not sure the preset itself is really broken. I think it's more a problem caused by Megui because as "--ref 3" is default, "--ref 3" is not added to the command line even if the preset is changed to something else than medium.

Thanks. What should I do the time it's being fixed ?

[Shevek]

Not sure if this is the correct thread for this question, please point me in the right direction if not!

Which is a good current preset for encoding Blu-Ray to 720p MKV for playback on Windows 7 Media Center?

Unrestricted? DXVA-High Def.?

Sample AVS script created using Script Creator:

LoadPlugin("C:\Program Files\MeGUI\tools\dgindexnv\DGMultiDecodeNV.dll")
DGMultiSource("H:\T1_Video.dgi",fieldop=0, resize_w=1280, resize_h=720)
crop( 0, 94, 0, -94)

[Sharktooth]

Yes, DXVA-High def. would definatly fit.

[hippo88]

Sharktooth,

Could you please recommend a MEGUI preset for encoding mpeg-ts (cap from cable TV) to mkv with ac3 audio.

The footage is sport (football 1920x1080i) 2 hours long. I keep everything the same just want to shrink the video to about 8000kbps/sec.

I've tried various preset and I noticed on passing play (ball movement does not look smooth/crisp) some areas have motion artifacts.

I test same footage on trial version of Sorenson Squeeze 6, encoded as mp4 - this is what I want (no motion artifacts)

Thank you.:confused:

[Sharktooth]

there are no specific presets for sports. what you need is a high compression ratio, so, if you dont care about the encoding time and/or HW compatibility, make a new megui preset and rise the x264 preset bar to veryslow or higher.

[ZEXEL]

dear Sharktooth,
I've new Samsung Monte (GT-5620), it's using MP4 video/audio format which like this:
General
Complete name : H:\Videos\TRIVIUM - Shattering The Skies Above.MP4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 17.8 MiB
Duration : 4mn 44s
Overall bit rate : 526 Kbps
Encoded date : UTC 2010-10-10 14:47:38
Tagged date : UTC 2010-10-10 14:50:15

Video
ID : 1
Format : MPEG-4 Visual
Format profile : Simple@L1
Format settings, BVOP : No
Format settings, QPel : No
Format settings, GMC : No warppoints
Format settings, Matrix : Default (H.263)
Codec ID : 20
Duration : 4mn 44s
Bit rate mode : Variable
Bit rate : 392 Kbps
Maximum bit rate : 790 Kbps
Width : 320 pixels
Height : 240 pixels
Display aspect ratio : 4:3
Frame rate mode : Constant
Frame rate : 15.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.341
Stream size : 13.3 MiB (75%)
Language : English
Encoded date : UTC 2010-10-10 14:47:38
Tagged date : UTC 2010-10-10 14:50:15

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Format settings, SBR : No
Codec ID : 40
Duration : 4mn 44s
Bit rate mode : Variable
Bit rate : 129 Kbps
Maximum bit rate : 134 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Stream size : 4.39 MiB (25%)
Language : English
Encoded date : UTC 2010-10-10 14:47:38
Tagged date : UTC 2010-10-10 14:50:15
Do you think it's available preset like that format or maybe almost same with MegUI?

When using converter from Samsung Kies/PC-Suite it's not customizable like MegUI.

[Sharktooth]

yes, it is. however it will be a MPEG-4 ASP preset (from what you posted). that means MeGUI supports it thru xvid.

[hardkorn]

I've posted this in another thread but thought of posting this here also as this thread is updated regullary.

quantum5uicid3 posted his megui custom command line:
program --tune film --pass 2 --bitrate 5277 --stats ".stats" --slow-firstpass --thread-input --b-adapt 2 --rc-lookahead 24 --merange 64 --me umh --direct auto --subme 10 --partitions all --trellis 2 --no-fast-pskip --aq-mode 4 --profile high --level 4.1 --bframes 3 --ref 6 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 17000 --vbv-maxrate 17300 --output "output" "input"

My questions were:

Is it necessarily for 6 reference frames(as I've read somewhere it breaks bluray/1080 compatibility - "If you want the target to be Bluray/AVCHD compatible, Ref Frames must be 4.") ?
Also the nb of frames to lookahead you've set it to 24 instead of the 40-50 default value. Is there a reason you did that? Will it not decrease the video quality?

The merange value you've set it to 64. Any reason ?

He also disabled the Color primaries BT.709, Transfer BT.709 and Color Matrix BT.709. Is that recommended?

I've encoded a segment of a bluray disc I got laying around here with his exact profile (which I expected to take forever to finish) and dragged it to mediainfo. I have a Nominal Bitrate field that I couldn't see in all the 720 encodes are floating the web. Is that due to specifying the Bitrate? But there's a huge different from what I've set in my profile 5700 and the real output, shown by mediainfo, Bitrate 6552, Overall Bitrate 6554. And most of the 720 encodes I've looked at, are encoded without the CABAC option enabled? Again, noob question, is that recommended?

What about the Tune Film option? Will that increase the quality of the encoded output?

Sharktooth, can you please guide me on setting megui for the best 720 encoding using a high bitrate somewhere around 5000-5500? The mewiki and all the settings explanations are too tech for me.

Thank you.

[Sharktooth]

too much questions and 1 simple answer. there is no best as per forum rules.
however i still dont understand if you want a x264 preset or a xvid preset.
from the data you posted you need a xvid preset but you quote a x264 commandline...

[hardkorn]

I need a x264 preset, not a xvid one.

[Sharktooth]

I need a x264 preset, not a xvid one.
omg... sorry. i erroneously mixed 2 posts while reading.
all the blu-ray settings are mandatory for compatibility with blu-ray specs.
there are some "less picky" players but it is recommended to leave all the settings there if you want 100% BR compatibility.
however, 1080p and 720p have different "max values". so, check THIS (http://forum.doom9.org/showthread.php?t=154533) page for optimal settings.
the merange 64 seems to me a bit of an overkill but im not an expert of sports encodes, so it may be better than defaults.
however colorprim, matrix and transfer should not be removed (for BD players compatibility).
about the bitrate, what you set in the x264 profile is VIDEO bitrate... the final filesize/bitrate will also depend on the AUDIO bitrate.
CABAC should be always ENABLED as it gives a better compression ratio.
the tune film option is meant for films/movies not for sports.

[hardkorn]

Thank you for the explanations.

I know that the bitrate I set in x264 is the video bitrate and not the overall one. However, what is with the nominal bitrate I keep seeing in mediainfo?

Some say that setting deblocking strength to -2 gives better results. On mgui wiki there is posted this link http://forum.doom9.org/showpost.php?p=810932&postcount=1 where *.mp4 guy says "f you wan't to give your encodes a more detailed look and don't mind the occasional block try a setting of -2:-1. If you like a clean picture and don't mind a little bluriness try 1:2. "

What about -2, -2? I've been using this for a while

[nurbs]

Is it necessarily for 6 reference frames(as I've read somewhere it breaks bluray/1080 compatibility - "If you want the target to be Bluray/AVCHD compatible, Ref Frames must be 4.") ?
The allowed number depends on the resolution. There is a sticky in the H.264 subforum.

The merange value you've set it to 64. Any reason ?
Not really. The inbuilt presets in x264 never use more than 24. It would probably be better to use a slower --me setting if you want better quality, e.g. --me tesa --merange 24.

Also the nb of frames to lookahead you've set it to 24 instead of the 40-50 default value. Is there a reason you did that? Will it not decrease the video quality?
--rc-lookahead can't be higher than --keyint, but there is no reason to set it since it will limited by the --keyint setting anyway.


--aq-mode 4 doesn't exist anymore. What used to be --aq-mode 4 is now --aq-mode 2.

[hardkorn]

Thanks nurbs

The x264: AVCHD default profile has Maximum GOP size of 24 and a minimum of 2, the default being max 250 and a min of 25.

However the x264: DXVA High Def.'s default GOP sizes are the default ones, 250 and 25.

What should I look here for?

Thank you.

edit: Is the --me umh setting deprecated? I have the Multi Hex setting. Is this the same as --me umh?

[hardkorn]

Ok, I've tweaked the profile a little bit. Here's what I have now:

program --preset slow --tune film --pass 2 --bitrate 4000 --stats "work.stats" --slow-firstpass --deblock -2:-1 --open-gop bluray --aq-mode 2 --merange 24 --me esa --subme 10 --partitions all --trellis 2 --no-fast-pskip --level 4.1 --bframes 3 --ref 6 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-maxrate 30000 --vbv-bufsize 15000 --weightp 0 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --output "output" "input"

What do you think guys?

[poisondeathray]

Ok, I've tweaked the profile a little bit. Here's what I have now:


program --preset slow --tune film --pass 2 --bitrate 4000 --stats "work.stats" --slow-firstpass --deblock -2:-1 --open-gop bluray --aq-mode 2 --merange 24 --me esa --subme 10 --partitions all --trellis 2 --no-fast-pskip --level 4.1 --bframes 3 --ref 6 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-maxrate 30000 --vbv-bufsize 15000 --weightp 0 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --output "output" "input"


What do you think guys?

is this 1280x720p23.976 and for blu-ray compatibility ?

you need to add:

--sar 1:1



if your target bitrate is only 4000 , you can use 2sec GOP settings - this way you don't need slices 4, both changes will make your encoding slightly more efficient. I would make these changes:

--vbv-maxrate 15000 --vbv-bufsize 15000 --keyint 48 --level 4 --slices 0 (or just delete --slices 4, becaues 0 is default)

[hardkorn]

What is the minimum bitrate for which I need to set the nb of slices by frame? Let's say I'd set the video bitrate to 6000.

Found the wikipedia link.

[poisondeathray]

What is the minimum bitrate for which I need to set the nb of slices by frame? Let's say I'd set the video bitrate to 6000.

For L4.1 blu-ray you need 4 slices
For L4.0 blu-ray you don't need slices
More slices slightly reduce efficiency

"2sec gop" blu-ray settings require maxrate and bufsize <15Mb/s

see
http://forum.doom9.org/showthread.php?t=154533

If you were using a target bitrate of 6000 , I would still use the 2sec GOP settings. The slices make less of a difference, but the difference between --keyint 24 and 48 can be very large (of course , depends on the source)

[hardkorn]

I'm sorry, I'm kind of lost here. What do you mean by "2sec GOP" setting? The minimum GOP size?

[poisondeathray]

I'm sorry, I'm kind of lost here. What do you mean by "2sec GOP" setting? The minimum GOP size?


maximum gop size.

ie. --keyint

Normally for blu-ray is 1 sec. So for 23.976p its 24

see the link posted earlier

[hardkorn]

Ok, got it.

Thanks.

[hardkorn]

Is the --me umh setting deprecated? I have the Multi Hex setting. Is this the same as --me umh?

[Sharktooth]

same stuff.

[hardkorn]

If I select Multi Hex, the command line doesn't change. Does that mean that multihex isn't applied or is that the default command and needs no extra switch? Should I add --me umh?

[Sharktooth]

it means it's the default.

[poisondeathray]

If something isn't working as to your expectations, I would also double check the custom command line box ; megui has some things hardcoded in there with some presets - this will override the other GUI settings