View Full Version : MeGUI Bluray Presets Failing to Encode
audiohominis
30th June 2010, 08:26
So far I've tried x264: Bluray - Standard and x264: Bluray - Insane and it throws error.
[Error] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.5.0
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.x (3.1.21022)
--[NoImage] Avisynth Version : 2.6.0.1
-[Error] Log for job1 (video, script.avs -> output.mp4)
--[Information] [1/1/2005 12:50:03 AM] Started handling job
--[Information] [1/1/2005 12:50:03 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --trellis 0 --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 136:135 --output "output.mp4" "script.avs"
--[Information] [1/1/2005 12:50:04 AM] Encoding started
--[Error] An error occurred: x264 [error]: invalid argument: nal-hrd = --b-pyramid
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [1/1/2005 12:50:04 AM] Job completed
Inside that script.avs:
global MeGUI_darx = 16
global MeGUI_dary = 9
LoadPlugin("C:\Program Files\megui\tools\avisynth_plugin\Convolution3DYV12.dll")
AVISource("SomeLagarithRGB24File.avi", audio=false)
LanczosResize(1920,1088)
ConvertToYV12()
Convolution3D("movielq")
:thanks: in advance.
PS. as you can see, this system is different from the one specified in my sig.
shon3i
30th June 2010, 09:19
--[Error] An error occurred: x264 [error]: invalid argument: nal-hrd = --b-pyramid
You are use bit outdated MeGUI or preset, newer x264 have nal-hrd with sub option vbr or cbr. So you need to put --nal-hrd vbr instead --nal-hrd
Aslo --sar 136:135 is incompatible with Bly-Ray standard, in your case should be --sar 1:1, you don't need to resize to 1088, encoder will automaticly pad resolution for you. And outputing to mp4 is not great idea, none of Blu-Ray authoring tools won't accept it. Use raw 264 output.
Zathor
30th June 2010, 09:47
You have to import and use the new MeGUI profiles to reflect the changes in the x264 syntax.
audiohominis
30th June 2010, 11:40
Thanks guys. My MeGUI was up to date though. Do I import the presets manually now? Where do I find them? I checked the official thread but the version number was old.
flebber
30th June 2010, 11:51
Thanks guys. My MeGUI was up to date though. Do I import the presets manually now? Where do I find them? I checked the official thread but the version number was old.
I would suggest that with latest megui you use Avisynth 2.58. Avisynth 2.6 caused errors which I posted in the "Megui Patched thread". errors stopped when I went from Avisynth 2.6 to 2.58.
Zathor
30th June 2010, 12:50
Do I import the presets manually now? Where do I find them?
I do not have MeGUI here so I have to describe it from my memory (= may be wrong):
Select Settings/Update, scroll down in the new window until you see the tx264 profile, right click, select force reinstall and click on the update button. You should see the import window now. Select the profiles you want to import and click on import.
Sharktooth
30th June 2010, 13:25
Zathor, we should implement an "update" feature for old version profiles. that would solve most of those problems.
if you want to discuss it i have few ideas...
audiohominis
1st July 2010, 19:26
shon3i
Yup, the lacking vbr param was indeed the culprit. I addressed the compat issues you pointed out and exported in raw H.264. BTW, any ideas as to why after TSMuxer VLC reports double the actual FPS while GSpot doesn't get it at all?
Zathor
As it happens, given the aforementioned corrected command it does actually encode. For some reason forcing preset re-installation, re-updating and re-importing didn't fix it, so I'm currently having to modify each XML manually. :(
flebber
I quickly skimmed through that thread for your post but couldn't spot it. You were having the same issue? I'm considering downgrading but I'd like to try other things first.
plonk420
26th December 2011, 15:23
i've noticed with MeGUI latest (2050? update says that build is up-to-date) that if i choose NAL HRD VBR, it isn't added to the switch list. however, nor is --nal-hrd vbr listed on https://sites.google.com/site/x264bluray/home/1080i-p
is this assumed by the --bluray-compat checkbox? or is this bug and i'll need to manually type into custom command line?
my encodes aren't playing on blu-ray standalones burned as blu-ray.
also, even if i type in --nal-hrd vbr into custom command line, it doesn't put it in the switch list (but typing (or selecting the checkbox for) --nal-hrd cbr does)
edit: i'm also noticing --b-pyramid strict isn't appearing in the switch list, even if i type it into custom command line area, too.
edit2: oops, i guess i posted in the wrong thread. i'm using scratchpad.
Zathor
28th December 2011, 09:59
Yes, with --bluray-compat your mentioned switches will be applied automatically.
plonk420
29th December 2011, 18:53
any idea why this wouldn't play, then? :S (2pass and analysis switches removed)
--level 4.1 --bluray-compat --tune film --bitrate 7000 --keyint 24 --open-gop --b-adapt 2 --weightp 2 --slices 4 --vbv-bufsize 30000 --vbv-maxrate 40000 --rc-lookahead 120 --merange 24 --me tesa --direct auto --subme 10 --trellis 2 --colorprim bt709 --transfer bt709 --colormatrix bt709 --sar 1:1 --output xx y.avs
Zathor
29th December 2011, 23:50
There are a lot of switches which are not needed. Try to reset the preset to default and use only the bluray target device in MeGUI.
plonk420
30th December 2011, 09:04
just trying to squeeze the most out of x264 :/
the_weirdo
30th December 2011, 10:53
Try to remove --weightp 2. Maybe that'll help.
EDIT: It seems --bluray-compat has already reduced weightp to 1.
plonk420
3rd January 2012, 00:14
location of --bluray-compat location doesn't matter? (before weightp option vs after weightp)
tebasuna51
3rd January 2012, 15:52
Of course, the last parameter override any previous preset.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.