MeGUI: General Questions and Troubleshooting Thread

[SacredCultivator]

Okay, I shall try that out along with disabling AQ. And will post back.

---
EDIT:
Okays finished and I have to admit, this definitely helped greatly, as the subs look quite seamless in the video... Although the filesize has increased by roughly 30MB's, so gonna try again with a .5 AQ and see what that does.

(Mind I communicate withy ou via MSN? {Added you})

[krosswindz]

I just upgraded my MeGUI to the latest version and I started to notice this error. Not sure if this is an xvid_encraw or MeGUI issue.

http://forum.doom9.org/showpost.php?p=1224368&postcount=417

[Sharktooth]

Okay, I shall try that out along with disabling AQ. And will post back.

---
EDIT:
Okays finished and I have to admit, this definitely helped greatly, as the subs look quite seamless in the video... Although the filesize has increased by roughly 30MB's, so gonna try again with a .5 AQ and see what that does.

(Mind I communicate withy ou via MSN? {Added you})
i tend to not use IMs lately.

[Sharktooth]

I just upgraded my MeGUI to the latest version and I started to notice this error. Not sure if this is an xvid_encraw or MeGUI issue.

http://forum.doom9.org/showpost.php?p=1224368&postcount=417
it's the xvid core that's crashing. let's continue on the other thread.

[SacredCultivator]

@Sharktooth: That's fine, as I found sorta a balance between the two (clear subs + quality).

But I was doing a few 'final' encodes to finalize my new settings and couldn't help but ask...

Apart from Encoding Time, do the number of:
Number of Reference Frames: (I use 5), and I tried 16, but not too sure what benefits that brings.
Number of B-Frames: (I use 5), and I tried 16, but again same as before.
^Basically not sure if making it any higher is worth it

And I'm just gonna leave the AQ at .5, trellis at 2, Psy-RD Stength at 1, and Psy-Trellis Strength at 0

(Not too sure if the M.E. Range matters much, but using 32.)

[Sharktooth]

"Apart from Encoding Time, do the number of: blah blah"... what? what's the question?

[SacredCultivator]

Oh sorry misworded it... Basically for the Ref. Frames/B-Frames, if I'm using a setting of 5, if I changed to anythign higher, is there much 'use' of it as I know anything higher just increases encoding time.

[Sharktooth]

anything higher increases encoding time AND compression (that usually means also quality).
the problem is the quality increase is NOT proportional to the time increase.
at some point, to obtain a 1% more quality it will take something like some hundreds % encoding time...

[SacredCultivator]

Gotcha, then I'll just leave the Ref at 5, and B-Frames at 4 then.

[Sharktooth]

good choice :)

[carlo_0000]

hello

i udate megui to 3.0.3012

but sins i got an error with D2V project creator

"megui cannot find audio track information, audio tracks selection will be disable"

what's wrong ?, i tested more video's so it s not my input video what as a problem

does i need to update AviSynth 2.5 or something else ?
i m under vista 64

[Sharktooth]

i cant check it right now, but it sounds weird.
ill have a look at it tomorrow.

[Kurtnoise]

hello

i udate megui to 3.0.3012

but sins i got an error with D2V project creator

"megui cannot find audio track information, audio tracks selection will be disable"

what's wrong ?, i tested more video's so it s not my input video what as a problem

what kind of video files did you try ? vob ? mpg ? ts ?

[Sharktooth]

i assumed it was a dvd source... if not, then that message has a meaning...

[dbzj14]

I am having a problem with the video's I encode with MeGUI. The encodes I produce look fine, but they take forever to load in vlc or any other media player. Am I doing something wrong in the encoding that makes my encodes take 15+ seconds to load videos 22 minutes long? I'll compare my encode to someone else's of the same episode and their's will load instantly while mine just sits there for a minute. Any help would be greatly appreciated.

[Sharktooth]

no idea, and pretty weird. just compare the settings and x264 versions used from the other encodes and yours.

[nurbs]

mkvs produced by x264 take long to load, but since you probably mux them with audio later i doubt that is the problem.

[Sharktooth]

infact. maybe the problem is mkvmerge. ill update it ASAP.

[nurbs]

Just to clarify, the mkvs x264.exe outputs take long to load. IIRC akupenguin posted that it has something to do with them being written on the fly, so they are somewhat different from those produced by mkvmerge. Since audio is muxed anyway later this is usually not a problem. I don't have long load times if I mux them with megui.

[tfa]

mkvs produced by x264 take long to load, but since you probably mux them with audio later i doubt that is the problem.

I've noticed this too. If i encode a video to x264 and set megui to make it an mkv without any audio, the video often takes forever to load and seek. As soon as the mkv is remuxed with the audio, it works fine.

[Sharktooth]

that's why, in that case, the output comes directly from x264. while if you add an audio track, then megui invokes mkvmerge to remux.
ok, i think we've got a winner then... there's some mkv output problem in x264.

[squid_80]

It's not really a bug, the mkv files are spec compliant but they don't have complete size or seek info (I forget what the proper name is for matroska). xvid_encraw's output mkv files are similar.

[Sharktooth]

ok. so i assume it's better to ALWAYS remux with mkvmerge.

[TheTooleMan]

I just spent a couple of hours trying to get MeGUI to run a script with the greyscale option turned on. The greyscale checkbox is sitting plain as day on the Xvid configuration dialog, but I finally figured out that checking that box was causing my jobs to fail. "Grey" is not on the list of options that dumps out in the "standard error stream" in the log. So what's it doing in the configuration dialog? If that's a part of MeGUI, and not coming from Xvid, then could it either be removed or (preferably) turned on?

I found in the closed "MeGUI bugs" thread a couple of references to the missing greyscale parameter dating back to 2006, so I'd say it's about time to address this one. (Say, why is that "bugs" thread closed - have all the bugs been fixed? :rolleyes: )

I also found the entries in the "xvid_encraw - Patched with AviSynth input support" forum that describe how to use zones for greyscale, but it looks like a convoluted work-around. Could we just have a working checkbox and a parameter that works instead?

[Kurtnoise]

explain in what it fails your jobs...because command lines are not dumped to the stderr.

[Capsbackup]

I recently tried to reencode a Blu-Ray .m2ts to .x264 to fit on a BD-5 disc with MeGui and the AVCHD-standalone .x264 profile. However, I forgot to change the container setting to RAWAVC so it encoded with the default .mp4 setting. Bummer!! Can I convert this .mp4 to .x264 without reencoding and not screw it up? It takes quite some time for a 2-pass encoding. If I have to reencode, can I perform just the 2ND pass since I have the .stats file that was generated from MeGui? Any help or guidance will be much appreciated.

[Kurtnoise]

just extract the raw stream from the mp4 within yamb...

[Capsbackup]

Thanks Kurtnoise13, saved me hours!! I don't know how I missed your program, but I am very greatful. Great forum, great members. I will keep learning with all your help.

[TheTooleMan]

explain in what it fails your jobs...because command lines are not dumped to the stderr.
I presume you're talking to me... I never saw a forum organized like this one.

This is part of the log:

--[NoImage] Job commandline: "C:\Program Files\megui\tools\xvid_encraw\xvid_encraw.exe" -i "C:\Users\My Stuff\Videos\Nveexport.avs" -pass1 "C:\Users\My Stuff\AppData\Roaming\MeGUI\stats" -bitrate 1256 -kboost 100 -chigh 30 -clow 15 -overhead 0 -turbo -max_key_interval 250 -nopacked -vhqmode 4 -qtype 1 -closed_gop -lumimasking -interlaced 1 -grey -notrellis -imin 1 -pmin 1 -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -bmin 1 -threads 4
--[Information] [12/18/2008 7:30:27 PM] Encoding started
--[Error] An error occurred: Usage : xvid_encraw [OPTIONS]
--[NoImage] Standard output stream: xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003
--[NoImage] Standard error stream
---[NoImage] xvid_encraw built at 10:22:53 on Aug 31 2007
---[NoImage] Input options:
---[NoImage] -i string : input filename (stdin)
---[NoImage] -type integer : input data type (yuv=0, pgm=1, avi/avs=2)
---[NoImage] -w integer : frame width ([1.2048])
---[NoImage] -h integer : frame height ([1.2048])
---[NoImage] -frames integer : number of frames to encode
---[NoImage] Output options:
---[NoImage] -dump : save decoder output
---[NoImage] -save : save an Elementary Stream file per frame
---[NoImage] -o string : save an Elementary Stream,
---[NoImage] or AVI file,
---[NoImage] or MKV file,
---[NoImage] based on filename extension
---[NoImage] -avi string : save an AVI file for the complete sequence
---[NoImage] -mkv string : save a MKV file for the complete sequence
---[NoImage] BFrames options:
---[NoImage] -max_bframes integer : max bframes (2)
---[NoImage] -bquant_ratio integer : bframe quantizer ratio (150)
---[NoImage] -bquant_offset integer : bframe quantizer offset (100)
---[NoImage] Rate control options:
---[NoImage] -framerate float : target framerate (25.0)
---[NoImage] -bitrate [integer] : target bitrate (700)
---[NoImage] values <= 10000 are treated as kbit/s
---[NoImage] values > 10000 are treated as bit/s
---[NoImage] -size integer : target size in kilobytes
---[NoImage] -single : single pass mode (default)
---[NoImage] -cq float : single pass constant quantizer
---[NoImage] -pass1 [filename] : twopass mode (first pass)
---[NoImage] -full1pass : perform full first pass
---[NoImage] -pass2 [filename] : twopass mode (2nd pass)
---[NoImage] -altpass2 [filename] : twopass mode (2nd pass alt)
---[NoImage] -zq starting_frame float : bitrate zone; quant
---[NoImage] -zw starting_frame float : bitrate zone; weight
---[NoImage] -zones : see xvid_encraw -help zones
---[NoImage] -max_key_interval integer : maximum keyframe interval (300)
---[NoImage] Single Pass options:
---[NoImage] -reaction integer : reaction delay factor (16)
---[NoImage] -averaging integer : averaging period (100)
---[NoImage] -smoother integer : smoothing buffer (100)
---[NoImage] Second Pass options:
---[NoImage] -kboost integer : I frame boost (10)
---[NoImage] -kthresh integer : I frame reduction threshold (1)
---[NoImage] -kreduction integer : I frame reduction amount (20)
---[NoImage] -ostrength integer : overflow control strength (5)
---[NoImage] -oimprove integer : max overflow improvement (5)
---[NoImage] -odegrade integer : max overflow degradation (5)
---[NoImage] -chigh integer : high bitrate scenes degradation (0)
---[NoImage] -clow integer : low bitrate scenes improvement (0)
---[NoImage] -overhead integer : container frame overhead (24)
---[NoImage] -vbvsize integer : use vbv buffer size
---[NoImage] -vbvmax integer : vbv max bitrate
---[NoImage] -vbvpeak integer : vbv peak bitrate over 1 second
---[NoImage] Other options
---[NoImage] -noasm : do not use assembly optmized code
---[NoImage] -turbo : use turbo presets for higher encoding speed
---[NoImage] -quality integer : quality ([0..6]) (6)
---[NoImage] -vhqmode integer : level of R-D optimizations ([0..4]) (1)
---[NoImage] -bvhq : use R-D optimizations for B-frames
---[NoImage] -qpel : use quarter pixel ME
---[NoImage] -gmc : use global motion compensation
---[NoImage] -qtype integer : quantization type (H263:0, MPEG4:1) (0)
---[NoImage] -qmatrix filename : use custom MPEG4 quantization matrix
---[NoImage] -interlaced [integer] : interlaced encoding (BFF:1, TFF:2) (1)
---[NoImage] -nopacked : Disable packed mode
---[NoImage] -noclosed_gop : Disable closed GOP mode
---[NoImage] -lumimasking : use lumimasking algorithm
---[NoImage] -hvs_aq string : use custom adaptive quantisation equation
---[NoImage] -hvs_lmb string : use custom lambda equation
---[NoImage] -stats : print stats about encoded frames
---[NoImage] -ssim [integer] : prints ssim for each frame ([0..4]) (2)
---[NoImage] -ssim_file filename : outputs the ssim stats into a file
---[NoImage] -debug : activates xvidcore internal debugging output
---[NoImage] -vop_debug : print some info directly into encoded frames
---[NoImage] -nochromame : Disable chroma motion estimation
---[NoImage] -notrellis : Disable trellis quantization
---[NoImage] -imin integer : Minimum I Quantizer (1..31) (2)
---[NoImage] -imax integer : Maximum I quantizer (1..31) (31)
---[NoImage] -bmin integer : Minimum B Quantizer (1..31) (2)
---[NoImage] -bmax integer : Maximum B quantizer (1..31) (31)
---[NoImage] -pmin integer : Minimum P Quantizer (1..31) (2)
---[NoImage] -pmax integer : Maximum P quantizer (1..31) (31)
---[NoImage] -drop integer : Frame Drop Ratio (0..100) (0)
---[NoImage] -start integer : Starting frame number
---[NoImage] -threads integer : Number of threads
---[NoImage] -nothreadedinput : Disable threaded input reading
---[NoImage] -progress [integer] : Show progress updates every n frames (10)
---[NoImage] -par integer[:integer] : Set Pixel Aspect Ratio.
---[NoImage] 1 = 1:1
---[NoImage] 2 = 12:11 (4:3 PAL)
---[NoImage] 3 = 10:11 (4:3 NTSC)
---[NoImage] 4 = 16:11 (16:9 PAL)
---[NoImage] 5 = 40:33 (16:9 NTSC)
---[NoImage] other = custom (width:height)
---[NoImage] -help : prints this help message
---[NoImage] -help zones : prints zones help message
---[NoImage] NB: You can define 64 zones repeating the -z[qw] option as needed.
--[Information] [12/18/2008 7:30:29 PM] Job completed

What were you saying about the command line?

You know, I could probably get a lot more done with this tool if it had something besides a link to a non-existent WIKI in the Help menu...

[Kurtnoise]

I see...it's because -grey command has been dropped with this xvid_encraw build. I'm updating the xvid gui then.

[TheTooleMan]

I see...it's because -grey command has been dropped with this xvid_encraw build. I'm updating the xvid gui then.
That would help as far as misleading people who want to use the greyscale filter, but why was it dropped? Seems like a perfectly useful and normal function which is now much more difficult to use with the zones workaround. Oh well...

[Sharktooth]

correct word would be "useless". just ensure you convert your source to greyscale before encoding.
colors wont be encoded if no color information is found on the source... the greyscale option, just drops color info...

[carlo_0000]

what kind of video files did you try ? vob ? mpg ? ts ?

all of them, there was probably something wrong during the last update

but i resolve the problem by copying the megui directory from windows xp to vista megui's directory

[pcjco04]

Using 0.3.0.3012 , I found the following crash :

When the bitrate calculator computes a very high bitrate (let's say 139536 for example) and if you choose to "Copy the calculated bitrate into video settings", then you cannot enter the current encoder config anymore :


MeGUI encountered a fatal error and may not be able to proceed. Reason: Value of '139536' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value Source of exception: System.Windows.Forms stacktrace: at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at MeGUI.packages.video.x264.x264ConfigurationPanel.set_Settings(x264Settings value)
at MeGUI.core.gui.ProfileConfigurationWindow`2.set_Settings(TSettings value)
at MeGUI.core.gui.ProfileConfigurationWindow`2.videoProfile_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at System.Windows.Forms.ComboBox.set_SelectedItem(Object value)
at MeGUI.core.gui.ProfileConfigurationWindow`2.set_SelectedProfile(GenericProfile`1 value)
at MeGUI.core.gui.ProfileConfigurationWindow`2.set_Profiles(Tuple`2 value)
at MeGUI.SpecificProfileType`2.ConfigureProfiles()
at MeGUI.core.gui.ConfigableProfilesControl.config_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[flebber]

So this is a general query about the one click encoder. I am happily using Megui..and I am happy :), then I thought why am I doing all these manually when I could use the one click encoder. So I tried it again, I hadn't for some time.

Appears to be two things stopping me using the one click encoder when I tried it and I wondered if these features were on the horizon at all.
1) There doesn't seem to be an option to enforce mod16 resizing - this causes some encodes to fail(avisynth script fails and reduces compression).
2) No autocrop.

Is there any chance these will feature on an updated one click encoder ?

[Kurtnoise]

all of them, there was probably something wrong during the last update

fyi, this part hasn't been modified in the lastest commits...


Using 0.3.0.3012 , I found the following crash :

When the bitrate calculator computes a very high bitrate (let's say 139536 for example) and if you choose to "Copy the calculated bitrate into video settings", then you cannot enter the current encoder config anymore :
as you can see in the bug report, this value seems too high for megui. There are a min/max limit in this part. Probably for encoders...

@flebber: post your features requests on SF...

[daWsOn_s]

mp4 container now supports ac3 tracks?

[Kurtnoise]

yes...read the MP4 FAQ. :)

[MrVideo]

Whe I try and go to the wiki help via the Help menu in megui, I basically get a page not found.

It seems that the built in link is bad and needs updating.

EDIT: It looks like MeWiki is down, as the error is: 502 Bad Gateway
The error occur no matter how you try and get there.

[MrVideo]

Where can I find the commandline instruction to meGUI?

If it is the wiki user guide that contains the info, then I'll need a valid link, as explained above, the link within meGUI is broken.

I have a bunch of transport stream MPEG-2 files that fit a particular file size. Ultimately these files have some editing done and then they are converted to H.264 files and placed into MKV containers.

I have a script that runs a VBScript to control VideoReDo to do the editing. I then run dgindex to create the D2V file and edit a template AVS file to create the AVS script. The last piece in the auto-chain is to get meGUI to automatically encode and then MKV package the MP4 and MP2 files.

[Sharktooth]

megui is a GUI and has no commandline options hence it cant be controlled using the commandline.
if you want to use the commandline then use the necessary tools directly... you dont need a GUI.

[MrVideo]

if you want to use the commandline then use the necessary tools directly... you dont need a GUI.

I have no idea what meGUI is using to do what I do via the GUI.

Is there a way to get meGUI to spit out what it uses? I can then use that as a template to do the H.264 encoding and then the MKV muxing.

[MrVideo]

Is there a way to get meGUI to spit out what it uses? I can then use that as a template to do the H.264 encoding and then the MKV muxing.

D'Oh! Found it in the log. Damn those are long command lines :D

[Kurtnoise]

If it is the wiki user guide that contains the info, then I'll need a valid link, as explained above, the link within meGUI is broken.
the wiki link works for me...

[MrVideo]

the wiki link works for me...

Interesting, as pointed out in the posting, I get a "502 Bad Gatreway" error.

Well, I did get the error. The problem has been fixed, as the site now works.

[tebasuna51]

Interesting, as pointed out in the posting, I get a "502 Bad Gatreway" error.

Well, I did get the error. The problem has been fixed, as the site now works.

Using this link:
http://mewiki.project357.com/

I get now:
502 Bad Gateway
nginx/0.6.32

[Kurtnoise]

Yes, me too. I asked to Sharktooth to enable the wiki on SF to create a mirror...

[JohnnyFu]

Hi,

I'm looking for a Sony NWZ-A Series Walkman compatible MeGui Profile. Is there any profile compilation I might have missed while searching the internet?

I already played with MeGui but I totally failed, I think I screwed it up with AviSynth since my Audio enque fails and Mp4Muxer doesn't mux anything at all :)

Sony NWZ-A Series Video Specs:
File Formats : .mp4.m4v
Codec: AVC (H.264/AVC)
Profile: Baseline Profile Level: Max. 1.3, Bit rate: Max. 768kbps
MPEG-4 Profile: Simple Profile, Bit rate: Max. 2500kbps

Audio, AAC-LC:
Channel number: Max. 2 channels
Sampling frequency *: 24/32/44.1/48kHz
Bit rate: Max. 288kbps per 1 channel
File size: Max. 2GB

any help would me much appreciated!
Johnny

p.s. Sony has a great audio player with the NWZ-828 but when it comes to video this thing is nothing for rookies like me. I spend hours with converter tools but not a single one worked. I know it must work with MeGui, there are people on the internet who successfully converted their Sony NWZ videos with MeGUI.

[Sharktooth]

@kurtnoise: i enabled the wiki but i have no idea how it works...

[pcjco04]

as you can see in the bug report, this value seems too high for megui. There are a min/max limit in this part. Probably for encoders...
I knew that, I just report it for the developers. Maybe a check could be done, either when the calculator puts its bitrate value in the encoder settings, or when encoder settings panel is shown to cap the bitrate to the max allowable value.

In v0.3.1.1001, I found another problem using the "One click Encoder" with source type that cannot be detected using default settings :

If I have a video where source type cannot be detected (I tested in the AVS Script Creator using the tool to analyse the source type and it returns a window saying that it cannot detect the source), then the job created with the "One Click Encoder" will make MeGUI vanished after the audio encoding.
If I uncheck "Automatic Deinterlacing" in my One Click profile or if I change the source detector settings so that it can be detected (analyse 10% instead of 1% percent for example), then the One Click Encoder jobs are all created and processed.