MeGUI: General Questions and Troubleshooting Thread

[Jeff Flowerday]

DGIndex tells you how the stream is flagged (always), MeGUI will tell you what's actually in the content (except in weird cases). At 98.xx % film, it's generally safe to force film in DGIndex and not do any field matching or decimation in Avisynth. Try this, and if you don't get any ugly artifacts (usually because the non-film sections are all-black GOPs at the beggining or end or are actually progressive content flagged as interlaced), you're fine.

If you're seeing an intolerable amount of combing, then don't force film in DGIndex and let MeGUI's AVS creator handle it in "Mostly Film" mode using blend decimation.

On the actual run I'm using the NV version, which doesn't have force film implemented yet. I'm definately not getting any combing doing "Mostly Film", just not sure about the stutter.

So would using "Mostly Film" instead of "Film" cause any issues on "Film" content? My thinking was better safe than sorry, I don't want to have to watch every movie to make sure there isn't any combing.

[Inspector.Gadget]

What field operation are you using in the NV version? If it's "Ignore pulldown flags", and your source is anything other than 100% film or 100% video, then it's reasonable to expect you will have problems. When handling mixed content in the NV tools, for the moment, you must honor pulldown flags and process in Avisynth.

[Jeff Flowerday]

What field operation are you using in the NV version? If it's "Ignore pulldown flags", and your source is anything other than 100% film or 100% video, then it's reasonable to expect you will have problems. When handling mixed content in the NV tools, for the moment, you must honor pulldown flags and process in Avisynth.

I'm doing just that, honoring pull down flags and letting avisynth do the processing.

[dolphinjet]

Hello,

I'm reporting a problem encountered after CoreAVC 1.9.5 installed as the default decoder. My active window will become unresponsive whenever megui starts a new task, either video or audio encode. The window may return to normal when a new task started. Not 100% sure as I usually cannot wait that long.
Reinstalled build 1056 but still the same. May rollback CoreAVC later. Has anyone experience the problem with CoreAVC?

Windows XP SP3
Megui build 1056
CoreAVC 1.9.5

[Bard2]

Looks like MeGUI core 1057 is buggy: my x264 profiles aren't saved, even partially (due to features update in x264 from r1259M to r1309M, so I can't update profiles manually to match new x264 version).
Even so, I can't make a new profile for x264: MeGUI just does not save lots of tune.

First windowcap: I try to tune x264 through configuration dialog, and save a profile.
Second one: I try to open earlier saved profile to tune it (look at commandline) - obviously it does not save most of tunes (no, I'm not a troll).

Edit: oh, and I'm sooo slow...

Thanks for your attention.
WBR, Bard.

[blubberbirne]

1057 is evil :D

I'm going back to 1056

[wolfbane5]

I've got the exact same problem Bard2.

[saint-francis]

It doesn't even load for me. Immediately crashes. How could such large bugs slip by? We must be missing something here.

[Inspector.Gadget]

I'm doing just that, honoring pull down flags and letting avisynth do the processing.

Then you should be fine, assuming that you're using (the following applies to the true nature of the content, not the flagging in the MPEG2 stream) TFM/TDecimate with blend decimation to bring down any true video sections to the majority film framerate on mixed sources and an IVTC of your choosing on true hard telecined sources (100% VIDEO in DGIndex, TIVTC/Decomb IVTC in AVS script creator). Can you describe in more detail what goes wrong, visually, in the encoded file?

[SixKiller]

1057 is evil :D

I'm going back to 1056

Same for me . 1057 is not working for me here. Cannot Save Presets and the Settings for x264 are screwed up. If you change something, save and the reopen, all settings are reset, as if you never changed anything

[SacredCultivator]

Just to clarify, the settings do get SAVED, but to select it... You have to hit "Config" and SELECT the preset, click and select it, and your settings 'return'. And then okay out and encode.

But you can't just select the profile via the Main Window of meGUI, have to click on 'Config' and then select the preset.

[MrVideo]

It doesn't even load for me. Immediately crashes. How could such large bugs slip by? We must be missing something here.

While 1057 starts up, it spits out that it has a fatal error and lists 12 major errors.

Back to 1056 I go as well.

[MrVideo]

1057 is evil :D

I'm going back to 1056

OKay, how does one go back to 1056, when there isn't a backup? All of the other applications are saved to a backup, but megui does not?

[ncatt]

The problem is incompatible profiles. Get this corrected profiles collection and extract to "allprofiles" folder in MeGUI:
http://www.mediafire.com/?udmmwzn2nyi

:thanks: to Kurtnoise and MeGUI developers for the hard work and time.

[MrVideo]

Now I'm really screwed, the update to 1057 even deleted all of the H.264 profiles, even the ones that I created. Yes, I answered yes to each of the deletes, but didn't see mine, figuring it would replace them with ones that were right.

This 1057 release is a nightmare. I have work to get done and now it won't happen.:mad::mad::mad::mad::mad:

[MrVideo]

The problem is incompatible profiles. Get this corrected profiles collection and extract to "allprofiles" folder in MeGUI

No, that didn't solve the problem of MeGUI saying that it has 12 different errors at startup. It also doesn't solve the fact that MeGUI destroyed my profiles. If it didn't like them, it should have converted them. It should never destroy the hard work of users.

I don't know if I'm ever going to get them back to where they were. I made them so long ago, that what I've done is lost from memory.

[MrVideo]

OKay, how does one go back to 1056, when there isn't a backup? All of the other applications are saved to a backup, but megui does not?

Digging back through the posts, I found one that pointed to a server that had 1056 on it. I fetched that zip and installed it. Now MeGUI doesn't bitch about a ton of startup errors.

Now to figure out what profiles to use to fit what I had before. The profile names have all changed. :confused:

[radiant chains]

OKay, how does one go back to 1056, when there isn't a backup? All of the other applications are saved to a backup, but megui does not?

There's always
http://sourceforge.net/projects/megui/files/

[SacredCultivator]

I've learned to cope with the problems, no biggy for me. But definitely hope that a new version will be put out to fix this problem, as I know many that have already reported about it reverted back to 1056.

[MrVideo]

There's always
http://sourceforge.net/projects/megui/files/

I had to back out the x264 encoder as well. It failed immediately upon encoding startup.

The new profiles are making the once 1.5 hr first pass turn into a 3.5 hr first pass. Now to find the old profiles and see if I an find the one that I was using.

EDIT: No idea where to find the profiles that went with the previous version of x264.

[szabi]

Hi

I wrote yesterday about update the attached programs but skip main program update.
Now I see core version is 1056 but data and libs still 1051.
Only 1057 update available for them which I really do not want. :cool:
How could I update these to 1056?

Bye
szabi

[MatLz]

One thing guys...it seems Kurtnoise is actually the ONLY developer of the gui you all need....don't annoy him with words like 'this version is a nightmare...the devil...' or else bad feelings.
Just kindly report the bugs.
It's for you if I say that...

[Alf Bundy]

I converted AC3 to NeroAAC with the M4A extension.
Now I'm muxing those .m4a with MKVmergeGUI :

http://img23.imageshack.us/img23/8375/m4a.png

Is it to normal to find a chapter file in a .m4a converted from an AC3 track with MeGUI 1057 ?

[MrVideo]

Now I see core version is 1056 but data and libs still 1051.
Only 1057 update available for them which I really do not want. :cool:
How could I update these to 1056?

Go back a couple of pages and you'll see a couple of links to websites. Take the 2nd one and you'll find the lib 1056.

MeGUI 1056 works with libs 1057. At least it hasn't crashed on me yet.
Data is nothing but help.

[MrVideo]

One thing guys...it seems Kurtnoise is actually the ONLY developer of the gui you all need....don't annoy him with words like 'this version is a nightmare...the devil...' or else bad feelings.
Just kindly report the bugs.

Unfortunately, as you can see from the various postings, the 1057 update is a real mess. There is no pussy-footing around the issue. There is something drastically wrong with it. Minor bugs is one thing, major failure is another.

Obviously the author's working copy can't be this screwed up, otherwise it wouldn't be working either. Different platform configuration?

While I'm sure that the issue with MeGUI and x264 will get resolved soon, the issue of lost personal profiles isn't.

[RyaNJ]

I just installed the latest release and it has deleted all of the x264 profiles. Every time I try to reinstall them it says something along the lines of:

---------------------------
Error loading Job
---------------------------
File 'C:\Users\xyz\AppData\Local\Temp\mwext0wn.2ve\allprofiles\x264\x264_dp_ Animation.xml' could not be loaded. Delete?

Anyone have any ideas how to fix this little annoyance?

[szabi]

Go back a couple of pages and you'll see a couple of links to websites. Take the 2nd one and you'll find the lib 1056.

MeGUI 1056 works with libs 1057. At least it hasn't crashed on me yet.
Data is nothing but help.

All link I found on last 10 pages does not have 1056 update to libs and data.

Bye
szabi

[Lugia25000]

xvid_encraw_20090605..> 25-Oct-2009 22:11 387k

It is a bad idea to put the encraw version from alexins in the auto update..

The encraw has many bugs and no fps detection.
new xvidcore.dll + old encraw + aviwriter.dll work fine.

[PlazzTT]

I just installed the latest release and it has deleted all of the x264 profiles. Every time I try to reinstall them it says something along the lines of:



Anyone have any ideas how to fix this little annoyance?

I got this too. I get an error about one of the job .xml files, and then there's a run-time error and MeGUI doesn't open.

[RyaNJ]

Yeah. That's exactly what I got.

[meatwad666]

i made 1057 launch by allowing it to delete profiles and I also had to manually delete old job###.xml files. it crashes when i try to reupdate my x264 profiles.

[RyaNJ]

Deleting them makes the program run but defeats the point because the profiles are essential to most encodings. I've tried force reinstalling them and even that doesn't fix the issue.

[Carpo]

The problem is incompatible profiles. Get this corrected profiles collection and extract to "allprofiles" folder in MeGUI:
http://www.mediafire.com/?udmmwzn2nyi

:thanks: to Kurtnoise and MeGUI developers for the hard work and time.

Get the files from that post, del X264 profiles in the megui dir and copy them over and 1057 starts fine, does here anyway

[Alf Bundy]

i made 1057 launch by allowing it to delete profiles and I also had to manually delete old job###.xml files. it crashes when i try to reupdate my x264 profiles.

Well, you could simply remake your profiles.
And it's probably a good idea since Presets and Tunings are now really applied in 1057.

My old profiles were full of redundant commands because Presets and Tunings didn't work with previous versions.
Now, my new profiles have lot cleaner command lines .

The only annoying "bug" is that we have to select a profile from within the x264 conf. dialog (not applied if selected from the main window).

[MrVideo]

All link I found on last 10 pages does not have 1056 update to libs and data.

http://kurtnoise.free.fr/MeGUI/

Two pages ago. You don't need the data, as all it is is help.

[Emulgator]

Many thanks for mentioning any incompatibilities.
So I could switch off Auto-Update.
Phew...
And still thanks to Kurtnoise for bringing this "eierlegende Wollmilchsau" to life...

[SacredCultivator]

With 1057, I forgot to mention, even though I asked this already... If using mb-tree, best to DISABLE b-pyramid and not have it set at normal correct?

[mozzle]

With 1057, I forgot to mention, even though I asked this already... If using mb-tree, best to DISABLE b-pyramid and not have it set at normal correct?

Yes. B-pyramid is incompatible with mb-tree.

[Alf Bundy]

Yes. B-pyramid is incompatible with mb-tree.
But will be soon ...

MB-tree still doesn't support b-pyramid (but will soon).


And you dont have to disable B-pyramid manually because x264 automatically discard it if MBtree is used.

[Azazel4]

Is there anyway to disable the turbo option on automated 2pass/3pass on the x.264 config screen, I prefer to fine tweak the settings but have the ease of automated 2pass,

[SacredCultivator]

@Alf: Again, thank you, I guess I'll leave it at Normal, since it auto-disables as mentioned.

[Alf Bundy]

Is there anyway to disable the turbo option on automated 2pass/3pass on the x.264 config screen ?


You can add --slow-firstpass in "Misc" tab -> custom command line.

[rapscallion]

Using ver 1051 and have no problems creating AVCHD's using that preset and automated 2 pass..
Source has always been 720p or 1080p.

Today tried a source that was 1080i /29.970fps and use a avs script resizing to 720p. The result was a terrribly out of sync audio when the avchd was created (via tsmuxer).

The first pass normally takes about 3hrs.

I'm now going to encode again without resizing the 1080i. I don't know if this is going to work because the first pass estimate is now over 5 hrs!

Is there a way to handle 1080i encodes properly that I'm not seeing ?

[MrVideo]

I need to restore the x264 profiles that were unceremoniously deleted by the 1057 install.

With 1057 starting up with 12 errors (and not knowing if it will even run correctly) restoring to 1056 and using the latest x264 results in x264 crashing immediately upon start. I returned that to the previous version as will.

But now I'm using the new profiles with old code and, while it does appear to be encoding, the job is taking twice as long as it should.

Where can I find a zip file of the x264 profiles that worked with the previous version of x264 (I don't have the version number handy, as I'm currently at work)? I've been letting the auto-update do its thing, so it should be the last posted version, before this mess.

[aegisofrime]

I need to restore the x264 profiles that were unceremoniously deleted by the 1057 install.

With 1057 starting up with 12 errors (and not knowing if it will even run correctly) restoring to 1056 and using the latest x264 results in x264 crashing immediately upon start. I returned that to the previous version as will.

But now I'm using the new profiles with old code and, while it does appear to be encoding, the job is taking twice as long as it should.

Where can I find a zip file of the x264 profiles that worked with the previous version of x264 (I don't have the version number handy, as I'm currently at work)? I've been letting the auto-update do its thing, so it should be the last posted version, before this mess.

I seem to have a similar problem with jobs taking twice as long, or rather not finishing at all. I can tell that the job has stalled because the frame count no longer moves. It can't be AviSynth or x264: I didn't touch the former and used the exact same version before I updated to 1057.

[MrVideo]

I seem to have a similar problem with jobs taking twice as long, or rather not finishing at all.

In this particular case, the job finished, hours after it should have.

After muxing the audio and video, I discovered that the many hours it took to encode was a waste. Why? The audio was out-of-sync and got a little worse as the program progressed.

[mordorspfc]

Is it possible to output a x264 .FLV file using Megui ??

In case not, i read some people managed to put a MP4 file in a FLV container, how can i do this ??

Thanks a lot

[aegisofrime]

In this particular case, the job finished, hours after it should have.

After muxing the audio and video, I discovered that the many hours it took to encode was a waste. Why? The audio was out-of-sync and got a little worse as the program progressed.

I wonder how much of that is attributable to bugs in this build though. I might be wrong, but MeGUI is only a frontend. Can a frontend cause these errors?

With my particular job that stalled, a second run with the settings and everything eventually finished it. I still have no idea what caused the first run to stall :(

[MrVideo]

I wonder how much of that is attributable to bugs in this build though. I might be wrong, but MeGUI is only a frontend. Can a frontend cause these errors?

Yes, MeGUI is the front end. But, that front end is using the new profiles with the previous x264. It seems to have messed up something.

I have a script that has options for the previous version of x264 and I'm using that to do a run of this video and see what happens. It is going a little faster, but not much. We'll see when I get home for lunch where it stands for length of encoding.

I still need the old profiles.

[73ChargerFan]

I had similar problems with some of my first encodes, with audio going out of sync. I think it was a muxing issue though.