MeGUI: General Questions and Troubleshooting Thread

[awx]

I'm getting this error when I try to open a D2V with the AVS Script Creator:
Cannot open video input
---------------------------
The file E:\XYZ\VTS_01_PGC_01_1.d2v cannot be opened.

Please make sure it's a valid AviSynth script and that AviSynth is properly installed.

You can check the validity of your script and AviSynth installation by opening the file in your favorite media player.

If that works, try opening the video in VirtualDub(Mod) as well. If the former works and the latter doesn't, install a YV12 codec.

Error message for your reference: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

I've tried doing several clean installs of MeGUI, reinstalling AVISynth and switching to the development update servers.

Any ideas what is wrong? MeGUI was working great until the new version came out.

[kumi]

Ditto, I reported it on the bug tracker.

[awx]

Ditto, I reported it on the bug tracker.
Where is your bug? I just checked the tracker on SF and cannot find it.

Also, I just finished a clean install of the .1038 version and this problem still exists for me.

[mroz]

Where is your bug? I just checked the tracker on SF and cannot find it.

Also, I just finished a clean install of the .1038 version and this problem still exists for me.

1832210 (https://sourceforge.net/tracker/index.php?func=detail&aid=1832210&group_id=156112&atid=798476)

[Sharktooth]

i "closed" the report since doing a clean install fixes the problem.
ensure you remove everything related to megui (including the update_cache folder) and then install the latest version.

[vtn54]

Dear Sharktooth, Clean install don't solve this problem, problem comes from the MediaInfoWrapper.dll in new version ,replacing it with old version solved this problem for me.

[kumi]

Confirmed, it's MediaInfoWrapper.dll.

MediaInfoWrapper.dll 0.7.5.3 = broken
MediaInfoWrapper.dll 0.7.4.4 = working again

Thanks vtn54.

[knary]

Hi

can you plz make MeGui doing 2-pass with Nero AAC

because that what i have read in NeroAACEnc docs


Multipass encoding:
-2pass : Enables two-pass encoding mode.
Note that two-pass more requires a physical file as input,
rather than stdin.
-2passperiod : Overrides two-pass encoding bitrate averaging period,
<number> : in milliseconds.
: Specify zero to use least restrictive value possible (default).


also here

I am pleased to announce the launch of FREE Reference Quality MPEG-4 Audio solution from Nero, in the command line form!

* First in the world FREE 2-Pass MPEG-4 AAC Encoder
* Compression Ratios ranging from ultra high (58 CDs fit on one!) to High-End Audio (2.5:1), for absolutely perfect audiophile encodings
* Crystal Clear, Award Winning Sound Quality at every compression ratio and bit rate!
* Support for Embedded Album Art (Covers, Booklets, Lyrics!)
* Store Entire Audio Album in a Single .mp4 File with all the Features of an Audio CD embedded inside, but at a fraction of the space!
* Reference Quality MPEG-4 Audio Codec
* Fully Compatible with the Latest Version of the State-of-the-art MPEG-4 Audio Standard (LC-AAC, HE-AAC and HE-AAC v2)

http://www.nero.com/nerodigital/eng/Nero_Digital_Audio.html

:thanks:

[Doom9]

@knary: that has been brought up a long long time ago. If you look at how megui works, you'd realize why it wasn't possible then and it's not possible now.

[ACrowley]

:eek: Time Remaining code is the same since the beginning...I didn't modify it.

Maybe your CPU was busy by multiple tasks ?


Mh... so far i can remember the Remaining Time was one static Value from encoding beginning on.
And the Value was more or less correct

In new Builds its sometimes 3h and later 30h again...it jumps around

I use Threads=0 on my X2 Dual Core for x264 encoding

But i dont think its a megui Problem :) I noticed the same on x264 cli

[DeathAngelBR]

Confirmed, it's MediaInfoWrapper.dll.

MediaInfoWrapper.dll 0.7.5.3 = broken
MediaInfoWrapper.dll 0.7.4.4 = working again

Thanks vtn54.

I get the error even with 0.7.4.4 :confused:

[ACrowley]

Thx for the new Update :=
Looks like the Remainig Time is stable now !
It starts with one Remaining Time and counts down to zero..
And the Encoding Time is correct

[oLex]

please, add ukrainian language to list of languages for muxing.

[SBaT]

0.3.0.1 dosent show in log tab for 1-pass or 2-pass any x264 [info] so no psnr,ssim or quants info. Same goes for log file that megui writes.

[berrinam]

Thx for the new Update :=
Looks like the Remainig Time is stable now !
It starts with one Remaining Time and counts down to zero..To be honest, I hadn't noticed any problems with this before. Out of interest, could you tell me what kind of job you were doing and what settings you used?

[ACrowley]

0.3.0.1 dosent show in log tab for 1-pass or 2-pass any x264 [info] so no psnr,ssim or quants info. Same goes for log file that megui writes.

Yes..
Is it bug or a "new Feature" ?! No x264 encoding Stast/Quants etc anymore with the newest Build

Its absolutly essentital for me to get my x264 Stats

Hope we get a fix soon!

[Kurtnoise]

http://forum.doom9.org/showthread.php?p=1069002#post1069002

[skystrife]

I had been running with --no-psnr and --no-ssim in the old version and was getting data on the quants. Hopefully this can be added back into the log?

TBH, I preferred the old, text-based log. Maybe there's a way to have the user choose what level of logging they want displayed?

[berrinam]

TBH, I preferred the old, text-based log.I found the old log a mess, with information everywhere. Why did you prefer it?

You know you can get a plain-text view of the log by going right-click->edit log?

[check]

Please return the full output from x264 to the MeGUI log. With the new log style it would presumably be added as a single collapsed element, so the cost is very little. Personally I find MeGUI almost useless without this information being available -- and I'd very much like to see it return.

[berrinam]

As I said in the development thread, any information missing from the new log is simply a bug. It has now been fixed in svn rev406. You'll have to wait for an update, though...

[check]

gwar, sorry for getting a little fired up then :p

[Sharktooth]

ill release an up to date build as soon as i can.

[avdw]

It still doesn't work, when converting the ac3 to mp3, it produces an mp3 that plays at about 50x the speed. Why Oh Why ?!?

AC3 plays perfect, problem must be in lame.

--[Information] [24/11/2007 21:21:16] Started handling job
--[Information] [24/11/2007 21:21:16] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\dgindex\dgindex.exe" -SD=< -AIF=<N:\My DVDs\Midnight Express 16-9\VTS_01_1.VOB< -OF=<N:\My DVDs\Midnight Express 16-9\VTS_01_1< -exit -minimize -OM=2
--[Information] [24/11/2007 21:21:16] Encoding started
--[Information] [24/11/2007 21:22:44] Running auto force film
---[NoImage] Film percentage: -1
--[Information] [24/11/2007 21:22:44] Job completed
--[Information] [24/11/2007 21:22:44] Postprocessing
-[Information] Log for job5
--[NoImage] Job type: audio
--[Information] [24/11/2007 21:23:27] Started handling job
--[Information] [24/11/2007 21:23:27] Preprocessing
--[Information] [24/11/2007 21:23:27] Encoding started
--[Information] Input
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 48000
--[NoImage] Commandline: C:\Program Files\megui\tools\lame\lame.exe -b 112 --cbr -h --silent - "N:\My DVDs\Midnight Express 16-9\VTS_01_1 T01 2_0ch 192Kbps DELAY 0ms.mp3"
--[Information] [24/11/2007 21:31:49] Job completed
--[Information] [24/11/2007 21:31:49] Postprocessing

[skystrife]

I found the old log a mess, with information everywhere. Why did you prefer it?

You know you can get a plain-text view of the log by going right-click->edit log?

The tree-based log may look pretty, but I honestly don't need to know the version info or the settings within the log, and the text-based log made it easier to see everything in one place rather than having to edit each and every tree to see my info.

Main beef atm is the lack of quant distribution info, but that will be fixed in the next update apparently.

I don't know really, I just liked it text-based. Maybe it's just because I've become used to it that way after so long, but the tree structure makes it more complicated than it was before (for me). Sure the log would get lengthy if you ran a ton of jobs in one session, but so long as you knew what each job was you could find your information fairly easily.

Also, with the current tree-based log, you're only getting minimal info at a glance. I preferred to be able to flip to my log tab and quickly be able to tell what job was what by looking at the input and see what my quant distribution was like after finding the correct job. Granted, I suppose I can get this by editing the log, but it's one extra step and I'm lazy I guess. =P

EDIT: Also, while I'm here, a neat feature that could be added to the bitrate calculator came to my mind. It currently allows user-inputted target filesizes, but doesn't seem to save these (at least, it doesn't on my system). If you could allow the user to save his/her own target filesizes that would be kind of neat. (I know a common size is 1/3CD or 233MB, it would be nice to have that as easily accessible as the 175MB.)

Just a thought, figured I'd share it. =)

[berrinam]

The tree-based log may look pretty, but I honestly don't need to know the version info or the settings within the log,That's debug information for bug-reports, not for the users. :)

and the text-based log made it easier to see everything in one place rather than having to edit each and every tree to see my info.Perhaps you would like a feature which opened every node of the treeview?

I don't know really, I just liked it text-based. Maybe it's just because I've become used to it that way after so long, but the tree structure makes it more complicated than it was before (for me). Sure the log would get lengthy if you ran a ton of jobs in one session, but so long as you knew what each job was you could find your information fairly easily.I believe that finding the job is much easier in the new tree-based log; simply because so many more jobs fit on one page, so you don't have to scroll. But perhaps you would be able to see more "at a glance" if we added some information to the job's root node -- instead of just calling it "Log for job33", we could call it "Log for job33 (video, InputFile -> OutputFile)". Would that be more useful?

From a technical point of view, I believe the new log is definitely superior as it provides better error logging capabilities. Also, it should make it easier to find jobs with warnings or errors, since the error/warning icons stand out from the standard info icons.

However, the main advantage of the new log is that it handles parallel job encoding correctly, whereas the old log just put the messages in the order they came, so multiple parallel jobs would clash with each other's log messages.

EDIT: Also, while I'm here, a neat feature that could be added to the bitrate calculator came to my mind. It currently allows user-inputted target filesizes, but doesn't seem to save these (at least, it doesn't on my system). If you could allow the user to save his/her own target filesizes that would be kind of neat. (I know a common size is 1/3CD or 233MB, it would be nice to have that as easily accessible as the 175MB.)This was added in version 0.3.0.1. The custom filesizes you select will be remembered and available next time you open the bitrate calculator.

[mroz]

Perhaps you would like a feature which opened every node of the treeview?

I was just going to suggest that.

Do nodes have different classifications, such as a distinction between debug levels or debug vs user info? If so, then options to expand/collapse nodes according to class would be handy, perhaps.

[skystrife]

That's debug information for bug-reports, not for the users. :)

Oh, alright then. =P

Perhaps you would like a feature which opened every node of the treeview?

That might be nice. I had an idea though, specifically regarding getting the quants information. I really don't like the idea of having to edit the log to find my quants info, so maybe I can expand the tree at some level in the job and see the quants info there?

I believe that finding the job is much easier in the new tree-based log; simply because so many more jobs fit on one page, so you don't have to scroll. But perhaps you would be able to see more "at a glance" if we added some information to the job's root node -- instead of just calling it "Log for job33", we could call it "Log for job33 (video, InputFile -> OutputFile)". Would that be more useful?

That would be an awesome feature and would make it really easy to figure out which job you actually wanted to be looking at! =)

From a technical point of view, I believe the new log is definitely superior as it provides better error logging capabilities. Also, it should make it easier to find jobs with warnings or errors, since the error/warning icons stand out from the standard info icons.

However, the main advantage of the new log is that it handles parallel job encoding correctly, whereas the old log just put the messages in the order they came, so multiple parallel jobs would clash with each other's log messages.

That's true; I didn't think about parallel encoding logging issues. The new log is most likely a step in the right direction but it could use some little adjustments here and there to make information just a bit more readily accessible.

This was added in version 0.3.0.1. The custom filesizes you select will be remembered and available next time you open the bitrate calculator.

Oh, nice. I'll have to grab it when the next build is put out (I can't use the current version because I need to have access to my quants info in the log, so I downgraded to the most recent stable).

[berrinam]

Do nodes have different classifications, such as a distinction between debug levels or debug vs user info? If so, then options to expand/collapse nodes according to class would be handy, perhaps.There are currently 4 levels: NoImage, Information, Warning, and Error, each of which is associated with an icon (or no icon, in NoImage's case). It's hard to add more levels because there are no system icons, so someone would have to make one for us.

It would be possible to filter the log by level, but I don't think that's particularly useful since the warnings and errors already stand out.

That might be nice. I had an idea though, specifically regarding getting the quants information. I really don't like the idea of having to edit the log to find my quants info, so maybe I can expand the tree at some level in the job and see the quants info there?I think you've misunderstood what I meant by going to edit log, but when 0.3.0.2 comes out I hope you will understand.

[avdw]

Dang, even that stupid avimux_gui can't produce a normal avi, what a pile of misconfigured horsesh1t

[sillKotscha]

you show a great source of knowledge here... as avimux_gui is THE tool for avi processing...

if you don't know what you are doing don't blame neither anyone else nor tools for your ignorance...

and as said 100red of times to you... if you don't like it don't use it - easy, isn't it ;)

and if you don't understand that and just wanna troll around, well here is the best place for people like you :)

cheerio

[mroz]

Dang, even that stupid avimux_gui can't produce a normal avi, what a pile of misconfigured horsesh1t

What don't you like about it? If you can be more descriptive & perhaps suggest how it should be configured by default, you could help everyone by filing an appropriate bug report.

I only use avi as an xvid container for standalones. For this I need no OpenDML & no RecLists, so I need to change the default config. Currently this requires a one off launching of AVIMux_GUI directly to permit the config, though this is more of a hassle if you need to change configs. Better would be if a Megui profile handled the config.

[MrAngles]

This seems like just an avisynth issue but I didn't see an avisynth troubleshooting thread so I figured I'd post it here.

After reinstalling windows on my pc I installed the K-Lite codec pack, .net framework, Avisynth 2.57 and the latest version of MeGUI. When I try to load a d2v into the avs script creator I get this message: AviSynth script error:
Script error: there is no function named "DGDecode_Mpeg2Source"
Looking in the plugins folder I saw that there were only 3 files (colors_rgb.avsi, DirectShowSource.dll and TCPDeliver.dll) which seemed odd, so I copied the plugins folder from a different pc, but that resulted in a different error: The file D:\CSI\2x13\VTS_02_1.d2v cannot be opened.
Please make sure it's a valid AviSynth script and that AviSynth is properly installed. You can check the validity of your script and AviSynth installation by opening the file in your favorite media player. If that works, try opening the video in VirtualDub(Mod) as well. If the former works and the latter doesn't, install a YV12 codec. Error message for your reference: External component has thrown an exception.

Anyone have any idea what I'm missing here? Everything works fine on my other PCs and worked great before I reinstalled windows.

[saint-francis]

The 24 hour + problem in the status window still persists. I thought this issue was addressed.

http://forum.doom9.org/showthread.php?p=1067743#post1067743

0.2.6.1039

- (Kurtnoise) [ProgressWindow] New format for Time Elapsed/Remaining.


Not that it's really a big issue.

[ACrowley]

The 24 hour + problem in the status window still persists. I thought this issue was addressed.

http://forum.doom9.org/showthread.php?p=1067743#post1067743

0.2.6.1039

- (Kurtnoise) [ProgressWindow] New format for Time Elapsed/Remaining.


Not that it's really a big issue.

yes, its fixed now, as he said with 0.2.6.1039

With this Build the Elapsed Time works again for +24h.
And the Remaining Timer works stable again too

To bad that the x264 Quants Log wont appears anymore ..otherwise i would be satisfied with megui ,for now

@Kurtnoise
please, can you make a fix for x264 Quants/log ?

[Kurtnoise]

@Saint-Francis: are you serious ? what does it look like ?

@ACrowley: it has been fixed. So, wait an update.

@MrAngles: you should install also DGdecode...

[ACrowley]

@ACrowley: it has been fixed. So, wait an update.


OK THX :)

0.3.0.1001 (includes 0.2.x branch fixes)
- (berrinam) Add missing output streams back to log (fixes #1836281)
- (Kurtnoise) [AutoEncodeWindow] mainform was being referenced in default constructor before it had ever
been assigned (#1836041). patch by Eamonh.
- (Kurtnoise) Removed unused code
- (Kurtnoise) more Audio Input FileType.

The x264 Quants/Infos are in Log/standard output stream/standard error Stream ? Why is it called "error stream" ?

[saint-francis]

@Saint-Francis: are you serious ? what does it look like ?


I am completely serious. I had just started encoding right before I made that post and the status window told me there was a little more than 1 hour left. This was clearly not the case since It was moving at about 2 fps. Maybe 15 minutes later it was at about 23 hours left. I can't post a screenshot right now because I'll be encoding for the next 20 hours or so but maybe I can later in the week.

[Sharktooth]

The x264 Quants/Infos are in Log/standard output stream/standard error Stream ? Why is it called "error stream" ?
http://en.wikipedia.org/wiki/Standard_streams

x264 uses stderr for quant info...

[Kurtnoise]

@Saint-Francis: what can I say...It works for somebody else. So, it should work also for you. Did you overclock your PC or something ? you're running multiple tasks ?

The x264 Quants/Infos are in Log/standard output stream/standard error Stream ? Why is it called "error stream" ?
stdout = standard output
stderr = standard error

This is the usual way to name console redirections when processes are running. depends mainly on the internal code used by the cli tools. Basically, stderr is used to return errors and stdout some other things.

[MrAngles]

@MrAngles: you should install also DGdecode...

Well I assumed that was the case, which is why I copied DGDecode.dll along with the rest of my plugins folder from one of my other PCs' installation of AviSynth. Should I be installing it a different way? And isn't it supposed to automatically come in the AviSynth installation? I don't remember manually installing it previously.

Also, I can't even encode audio to aac either... jobs error out immediately when I try to run them...

------------------------------------------------------


Starting job job1 at 2:49:18 AM

Starting preprocessing of job...

Preprocessing finished!

successfully started encoding

Processing ended at 2:49:19 AM

------------------------------------------------------

Log for job job1



Error:

------------------------------------------------------

End of log for job1
------------------------------------------------------

Maybe I should try different installation packages... I've got megui-0.2.6.1038.exe and Avisynth_257.exe, maybe there are problems with them

[Kurtnoise]

well...

0/ Remove everything.
1/ Install Avisynth.
2/ Install MeGUI package.
3/ Run the update.

and that should be fine...

[saint-francis]

@Saint-Francis: what can I say...It works for somebody else. So, it should work also for you. Did you overclock your PC or something ? you're running multiple tasks ?


Yeah the PC is pretty seriously overclocked and I always do a lot of other things with it at the same time. Nothing too intensive though; browse the internet, use Skype for voice chat, etc. Also I'm using an experimental script that I'm not really sure about. I'm still getting a handle on how avisynth and all of these exotic filters work.

[MrAngles]

well...

0/ Remove everything.
1/ Install Avisynth.
2/ Install MeGUI package.
3/ Run the update.

and that should be fine...

Honestly not trying to make things difficult here, but I've already done that a few times with the same results. My installation file for AviSynth has got to be bad because it only includes those three plugins files I mentioned earlier. Unless I'm crazy I remember AviSynth coming with all the main plugins used by MeGUI. I've tried three different installation packages for MeGUI, and each one errors out when trying to convert audio.

Maybe it would be helpful if somebody could send me links for working installation packages for both programs.

[Sharktooth]

where did you get megui?
you can get megui from the official page: http://sourceforge.net/project/showfiles.php?group_id=156112
also ensure you let it auto-update or you wont get the required avs filters...

[vtn54]

Honestly not trying to make things difficult here, but I've already done that a few times with the same results. My installation file for AviSynth has got to be bad because it only includes those three plugins files I mentioned earlier. Unless I'm crazy I remember AviSynth coming with all the main plugins used by MeGUI. I've tried three different installation packages for MeGUI, and each one errors out when trying to convert audio.

Maybe it would be helpful if somebody could send me links for working installation packages for both programs.
Which Windows you use? Vista or XP?

[MrAngles]

Which Windows you use? Vista or XP?
XP

where did you get megui?

Don't remember, but it's version 0.3.something. It appears that that was the problem, because using 0.2.6.1040 from your link took care of everything. Thank you, and I'll keep track of the link this time. I must have gotten a beta version by mistake.

Anyway, thanks for all the help, I'm back up and running.

[Sharktooth]

yes, 0.3.x is the development branch (consider it a sort of alpha). however im glad it works now:)

[rack04]

Is there anyway that MeGUI AviSynth script creator will accept raw h264 streams?

[Sharktooth]

have a look at this thread: https://forum.doom9.org/showthread.php?t=122598