View Full Version : MeGUI Bug-Report Thread
spunch
14th June 2006, 22:13
I have a problem with MeGUI that's been around for quite a while and I feel like I need to report it.
I use the OneClickEncoder feature of MeGUI a lot, but I don't use it for single videos, I have a batch script that generates many OneClickEncoder jobs for many short clips. The problem is MeGUI doesn't handle so many OneClickEncoder jobs at a single time very well.
I tend to get many errors (and eventually a fullscale crash) in the OneClickEncoder innitiation routine - when MeGUI creates many jobs out of the OneClickEncoder job (the time when MeGUI also decides which deinterlacer to use, cropping, etc...).
I get these errors when I have more than 15~ OneClickEncoder jobs in the queue and MeGUI processes them sequentially.
To get around this problem I simply suspend/pause all the OneClickEncoder jobs after 15, and let MeGUI process the first 15. I then restart MeGUI, unpause the next 15 in queue, and I continue this cycle until everything is processed. Not very convenient but it works.
I think MeGUI needs to reset something in itself after every OneClickEncoder job to avoid these errors and crashes.
The sort of errors I get:
Source detection failed
Eroor opening analysis script External component has thrown an exception.
Check to make sure you have TIVTC.dll in your AviSynth plugins directory.
External component has thrown an exception.
Error opening analysis script Script error: there is no function named DGDecode_mpeg2source
Check to make suree you have TIVTC.dll in your AviSynth plugins directory.
Script error: these is no function named "DGDecode_mpeg2source"
The input clip for source detection could not be opened.
External component has thrown an exception.
Error opening analysis script Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Check to make sure you have TIVTC.dll in your AviSynth plugins directory.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
vendol21
15th June 2006, 06:32
Autoencode latest version calculator bug : Desired filesize 500MB - Projected file size 2GB. I'm using HQ-Slowest sharkstooth profile and CT-AAC 48 kbps for audio.
~bT~
15th June 2006, 14:04
I keep getting this error when trying to analyse the source...
I have all the .dll's in the plugins folder.
http://img133.imageshack.us/img133/8568/untitled3ou.jpg
Please help...
Update: Sorted it out.
bratao
15th June 2006, 17:38
Hi,
Where is the "use mencoder to xvid " option ??
I hate xvid_encraw, and like to use mencoder ;-(
Adub
15th June 2006, 17:46
they are under the settings menu. It is a drop down list. There is also the option to use Mencoder instead of x264 commandline as well.
bratao
15th June 2006, 20:49
Merlin7777,
i know this and always use mencoder,
but the lastest version(0.2.3.2167) do not have it !
berrinam
15th June 2006, 23:21
What is wrong with xvid_encraw that makes you not want to use it?
acrespo
16th June 2006, 03:19
My AVS scripts can't be recognized by xvid_encraw. I already post my script here and nobody can explain this problem.
ChronoCross
16th June 2006, 03:23
There is nothing wrong with xvid_encraw. I'll take a look at your script and see if I can narrow it down.
P.S. mencoder currently doesn't work using the latest avisynth versions. Which is why it is a bad idea to use it.
Repost the avs that is giving you problems. I can't seem to find it.
acrespo
16th June 2006, 06:29
The latest megui stable version work with mencoder perfectly to me.
I have avisynth 2.56 installed here. I don't know if this is the reason for my xvid_encraw problem.
ChronoCross
16th June 2006, 06:40
2.5.7 doesn't work with mencoder due to mencoder being broken. something about planar alignments (I forgot exactly what the problem was).
xvid_encraw should function correctly for all versions of avisynth currently in use. what problems are you having that you think it's broken?
berrinam
16th June 2006, 07:27
Error opening analysis script Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Check to make sure you have TIVTC.dll in your AviSynth plugins directory.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
I know this is annoying, but all I can say is that, since MeGUI is in a managed language (C#), this is probably AviSynth's fault. Maybe someone else can help more. I'll look into it in a little while, though, to see if anything obvious crops up.
berrinam
16th June 2006, 07:38
3-) XviD encoding is wacko it seems. No matter what quantizer you enter (CQ mode), it always uses 8. Also, some checkboxes don't work--that is, even if you check Cartoon Mode, when you hit OK, it is then automatically unchecked. Thus, every encode I do is forced into Q8, and many options can't be selected--no cartoon mode, no chroma optimization, etc...
Whenever you have a problem, the easiest solution is simply to hide it. The options which didn't work are hidden (because they aren't supported in xvid_encraw) and CQ is fixed.
holzi
16th June 2006, 11:30
To Bad Multi Pass Bug still not fixed :(
Ok let's wait for another new version :)
berrinam
16th June 2006, 13:20
1-) When I do a AVI encode, the container selected in "Automatic Encoding" window is MP4 and not AVI.I think you are misunderstanding the meaning of the comboboxes. The filetype combo-box in the main window is unrelated to the one in the mux window.
And in the "Adaptative Mux Window" the Output selected is MKV, not AVI.Not sure what you mean. It is whatever you choose.
2-) When I don't encode the audio, I choose "Add additional content" in "Automatic Encoding" window. Then I choose my .MP4 or .MP3 file and click in "Go" button. Nothing happens. Then I change the file name and press "Go" button again to function correctly.I confirm this, and you can expect a fix soon.
acrespo
16th June 2006, 13:43
I think you are misunderstanding the meaning of the comboboxes. The filetype combo-box in the main window is unrelated to the one in the mux window.
Not sure what you mean. It is whatever you choose.
In latest stable version, when I choose AVI container in main screen and press autoencode, all combo boxes was set to AVI (in Auto Encoding window and in Mux window too) it's not occuring now, in Auto Encoding window the MP4 container is always pre selected and in Mux window MKV is pre selected (the container combo box fill only after choose the audio file and I choose MP3. the options in combo is MKV and AVI but MKV is pre selected).
2.5.7 doesn't work with mencoder due to mencoder being broken. something about planar alignments (I forgot exactly what the problem was).
xvid_encraw should function correctly for all versions of avisynth currently in use. what problems are you having that you think it's broken?
I receive a error from xvid_encraw when I do any encode when the source is a AVS script. It can't detect de video fps (fps = 0.00000000000) and exit after the error. I already post the error here. I don't know if it's related with the avisynth version, I only inform the version instaled here.
berrinam
16th June 2006, 14:00
In latest stable version, when I choose AVI container in main screen and press autoencode, all combo boxes was set to AVI (in Auto Encoding window and in Mux window too) it's not occuring now, in Auto Encoding window the MP4 container is always pre selected and in Mux window MKV is pre selected (the container combo box fill only after choose the audio file and I choose MP3. the options in combo is MKV and AVI but MKV is pre selected).I am aware of that, but what I'm saying is that there is no point in choosing the video format in the main form unless you are encoding from there: you might as well just select it in the Adaptive mux window or the autoencode window. It's no more work for you, and it means there needn't be an internal conversion between filetypes, because they are stored differently on the main form from on the other windows.
acrespo
16th June 2006, 14:44
I am aware of that, but what I'm saying is that there is no point in choosing the video format in the main form unless you are encoding from there: you might as well just select it in the Adaptive mux window or the autoencode window. It's no more work for you, and it means there needn't be an internal conversion between filetypes, because they are stored differently on the main form from on the other windows.
Ok, for me it's not a problem. I can select AVI again, but when people that use the stable version today will upgrade to latest version will guess that it's a bug, because tha stable version assume the main form settings in auto encode.
berrinam
16th June 2006, 22:05
@acrespo: I see your point, but I think they will just have to deal with it, like you do. :D
Now I think in 2169 I've fixed all reported bugs except:
15 One Click Encodes in a row causes Source Detection crashes
xvid_encraw AviSynth bugs, which I don't think are to do with MeGUI
Is there anything I've missed?
unskinnyboy
17th June 2006, 02:11
Ah, I think I managed to crash MeGUI. :D
Build is 0.2.3.2146 from ChronoCross. OS is Win XP 5.1.2600 SP2 Build 2600.
What I did:
Tools -> AviSynth script generator -> Options -> Video Input.
I selected a VOB file instead of a .d2v file and poof! MeGUI crashed (Don't ask me why I did it).
http://img98.imageshack.us/img98/5899/meguierror0ly.png
Ideally, you should throw a dialog asking the user to select the .d2v and not the .vob.
Reproducable error. No logfile produced. Let me know if you need to see the dump which Windows produced. I hope this wasn't reported before - I did a small search in this thread but didn't see it.
ChronoCross
17th June 2006, 02:21
you should try updating to a later version and see if it stil occurs.
the latest version of megui is 2169.
unskinnyboy
17th June 2006, 02:35
Where is 2169? Before I submitted this report, I saw berrinam saying "Now I think in 2169 I've fixed all reported bugs except", so I checked for 2169 in your site, but it wasn't there. If I had gotten it, I would have definitely tried with it too.
Your site is down btw.
Adub
17th June 2006, 03:09
Is it just me or does the Deinterlace analysis do one pass, show the correct/needed information with the recommended settings, and then keeps doing multiple passes for no reason?
ChronoCross
17th June 2006, 04:10
Where is 2169? Before I submitted this report, I saw berrinam saying "Now I think in 2169 I've fixed all reported bugs except", so I checked for 2169 in your site, but it wasn't there. If I had gotten it, I would have definitely tried with it too.
Your site is down btw.
I've removed all builds as there is no reason to have them anymore. the auto updater does everything that's needed. Hence why the page doesn't load lol. I'll post an auto updater build on my site now so people can start there.
http://www.chronocrossdev.com/apps/MeGUI-0.2.3.2169.rar
ChronoCross
17th June 2006, 04:11
Is it just me or does the Deinterlace analysis do one pass, show the correct/needed information with the recommended settings, and then keeps doing multiple passes for no reason?
It does 2 passes and then stops. I'm not sure the reason for the second pass but I assumed it had to do with error checking to make sure the first pass's results were accurate.
unskinnyboy
17th June 2006, 04:27
I've removed all builds as there is no reason to have them anymore. the auto updater does everything that's needed. Hence why the page doesn't load lol. I'll post an auto updater build on my site now so people can start there.
http://www.chronocrossdev.com/apps/MeGUI-0.2.3.2169.rar
OK, I am on 2169 now (the autoupdater is lovely), but the bug I reported is still there, which isn't surprising if it wasn't reported by anyone else before and subsequently fixed. What I'd like for someone to do is to check to see if they get the issue too, just to ensure it isn't mine alone.
Adub
17th June 2006, 04:28
Right. Okay, thanks ChronoCross.
ChronoCross
17th June 2006, 04:33
OK, I am on 2169 now (the autoupdater is lovely), but the bug I reported is still there, which isn't surprising if it wasn't reported by anyone else before and subsequently fixed. What I'd like for someone to do is to check to see if they get the issue too, just to ensure it isn't mine alone.
It doesn't crash on my system. Megui throws an error that says
"Directshowsource: The filter graph manager won't talk to me"
Perhaps you have a Directshow vob decoder that's crashing avisynth and thus megui. Or it could be the vob itself. Does it happen with other vobs?
berrinam
17th June 2006, 04:44
Is it just me or does the Deinterlace analysis do one pass, show the correct/needed information with the recommended settings, and then keeps doing multiple passes for no reason?The second pass is used to find the field order. Since it's only required in some places and it uses a different script, it is done in a different pass, but only when the field order is needed (interlaced/film/hybrid sources)
unskinnyboy
17th June 2006, 05:31
It doesn't crash on my system. Megui throws an error that says
"Directshowsource: The filter graph manager won't talk to me"
Perhaps you have a Directshow vob decoder that's crashing avisynth and thus megui. Or it could be the vob itself. Does it happen with other vobs?
You are right. It was my MPEG-2 decoder after all. I had installed Darim DVMPEG the other day and looks like it took over MPEG-2 decoding without permission. :rolleyes: I have uninstalled Darim and now Nero's video decoder took over. But I must admit I am still not satisfied with the state of affairs, because now I am getting a script error: there is no function named "DirectShowSource" as if AviSynth itself is not installed. Instead of even letting AviSynth into the picture (and I am sure if I remove Nero from the chain, the error will be something else), can't we simply throw a dialog to the user based on the file extension itself? "Not a .d2v file" or something like that?
ChronoCross
17th June 2006, 06:37
You are right. It was my MPEG-2 decoder after all. I had installed Darim DVMPEG the other day and looks like it took over MPEG-2 decoding without permission. :rolleyes: I have uninstalled Darim and now Nero's video decoder took over. But I must admit I am still not satisfied with the state of affairs, because now I am getting a script error: there is no function named "DirectShowSource" as if AviSynth itself is not installed. Instead of even letting AviSynth into the picture (and I am sure if I remove Nero from the chain, the error will be something else), can't we simply throw a dialog to the user based on the file extension itself? "Not a .d2v file" or something like that?
well one of the things that people had been clamoring for in the avisynth script creator was to be able to put whatever file they wantd in there.
.d2v is handled by Mpeg2source
.avi is handled by AVISOURCE
everything else is handled by Directshow source.
It's a give in take in this instance. I do however in all instances thing that .vob should be handled exclusively by DGindex. However IDK if it's possible for megui to have both the d2v creation screen and avisynth script creator open at the same time.
unskinnyboy
17th June 2006, 06:54
Well then, things don't look very peachy here. d2v opens alright, but avi, avs all give "there is no function named "DirectShowSource"" error. :-|
As for your question about the 2 windows, if I open an MPEG-1 file in AviSynth script generator, DGIndex Project Creator window pops up, and so yes, they can co-exist, but with DGIndex Project Creator as a modal window.
ChronoCross
17th June 2006, 08:27
do you have AVISYNTH installed? it seems wierd that it would continue throwing that message.
berrinam
17th June 2006, 08:45
It sounds like you do have AviSynth, but it sounds like you are missing the DirectShowSource plugin and/or the registry location for the AviSynth plugins folder is wrong. Check that the AviSynth plugins folder which MeGUI tells you in the settings contains DirectShowSource. Also, try reinstalling AviSynth
holzi
17th June 2006, 11:56
When I want to mux an xvid/avi file with AC3 Audio I get stucked. When I load the avi I can choose avi as the Container Format. But as soon as I add the AC3 Audio file I can only choose MKV. Which doesn't work for me :)
Or should I use the Divx Avi Muxxer?
This one dosn't work for me either because it changes the fourCC to dv50.
Greetings Holzi
berrinam
17th June 2006, 12:34
In that case, no muxer can be found. It's simply not supported unless you want to use a dv50 fourCC, so either make do with that or consider another container, like mkv, for instance.
holzi
17th June 2006, 13:41
well Ok then I just go with avi mux gui or virtual dub mod.
Thx anyway
unskinnyboy
17th June 2006, 15:24
It sounds like you do have AviSynth, but it sounds like you are missing the DirectShowSource plugin and/or the registry location for the AviSynth plugins folder is wrong. Check that the AviSynth plugins folder which MeGUI tells you in the settings contains DirectShowSource. Also, try reinstalling AviSynth
My bad, yes. DSS was missing. I had moved all the plugins from the plugin folder couple of days back because of some DLL conflicts. I also falsely assumed autoupdater took care of it. Again, my bad. Had I checked the autoupdater window, I would have seen that DSS isn't one amongst them because it comes installed with AviSynth.
I have a related question which I will post in the feature request thread.
Cantello
18th June 2006, 11:25
While trying to generate an AVS script wiht MeGUI, it gives the following error message but does not crash.
Programs used: MeGUI 0.2.3.2116, AviSynth 2.56a.
The file I was trying to generate an avs script for is a standard xvid avi file with AC3 sound, which I encoded before from a DVD, which worked well.
http://img119.imageshack.us/img119/7206/clipboard014pn.th.png (http://img119.imageshack.us/my.php?image=clipboard014pn.png)
Could I be missing something? Reinstalling AviSynth did not help, even different versions (2.55).
Thanks for any hints!
HieiYYH
18th June 2006, 15:00
i have a xvid raw 23.976fps, i tried to encode in twopass to h264 raw (*.264) in normal profile, i only changed the Subpixel refinament to mode 7 rdo level 2 (slower), all the 2 passes are done with no warnings or errors, but there is a error, some random ones, look at the picture... i encoded a 28:40 video to 60mb, maybe the bitrate (250kbps) is too low for avc and so give this crap error or maybe a error in the avysynth script? i tried encode 4 times, and always give those erros :/ any help
http://xs302.xs.to/xs302/06240/videoerror.jpg
my script:
AVISource("video.avi", audio=false)
LoadPlugin("VSFilter.dll")
textsub("encode.ass")
check
18th June 2006, 15:04
Does the error exist in the avs file when you play it back in a media player? If so, check the original avi is ok and try without the subtitles to see if vsfilter is broken.
HieiYYH
18th June 2006, 15:08
Does the error exist in the avs file when you play it back in a media player? If so, check the original avi is ok and try without the subtitles to see if vsfilter is broken.
raw doesn't have any error, i checked already, the subititle that i used has only 1 line, for credits, can be the vsfilter?
ps: i'm using the latest version of megui and x264 codec CLI
yamb log
Adjusting AVC SizeLength to 16 bits
AVC-H264 import - frame size 512 x 384 at 23.976 FPS
Saving to video.mp4: 0.500 secs Interleaving
-----------------------------------------------
* Movie Info *
Timescale 600 - Duration 00:28:40.960
Fragmented File no - 2 track(s)
File Brand isom - version 1
File has root IOD
Scene PL 0xff - Graphics PL 0xff - OD PL 0xff
Visual PL: AVC/H264 Profile (0x15)
Audio PL: AAC Profile @ Level 1 (0x28)
No streams included in root OD
Track # 1 Info - TrackID 1 - TimeScale 24000 - Duration 00:28:40.885
Media Info: Language "und" - Type "vide" - Sub Type "avc1" - 41260 samples
MPEG-4 Config: Visual Stream - ObjectTypeIndication 0x21
AVC/H264 Video - Visual Size 512 x 384
Self-synchronized
Track # 2 Info - TrackID 2 - TimeScale 48000 - Duration 00:28:40.960
Media Info: Language "jap" - Type "soun" - Sub Type "mp4a" - 40335 samples
MPEG-4 Config: Audio Stream - ObjectTypeIndication 0x40
MPEG-4 Audio AAC LC - 2 Channel(s) - SampleRate 24000 - SBR SampleRate 48000
Synchronized on stream 1
ps 2: the turbo option in x264 cause some problem if used?
i really want to know why those errors ;~~
foxyshadis
18th June 2006, 21:02
http://forum.doom9.org/showthread.php?t=54130
Is the error on the same frame every time? If not and you're getting random, unrepeatable corruption, try this, as you may be pushing your system too near its limits. If so, it might be a bug in x264 and you should go back a couple versions.
You should also check that your command line doesn't contain anything related to aq, which are of unknown stability. (And no, turbo's fine if you're just going to drop the first pass.)
berrinam
18th June 2006, 22:43
While trying to generate an AVS script wiht MeGUI, it gives the following error message but does not crash.
http://img119.imageshack.us/img119/7206/clipboard014pn.th.png (http://img119.imageshack.us/my.php?image=clipboard014pn.png)
There's something up on your end with DirectShow which is causing problems. All I can really do is let MeGUI provide a more standard error message in that situation.
EDIT: That's what I've done in 0.2.3.2170. Can you test it to find out if it does just give a DirectShow error message instead of a crash? Since I can't reproduce the crash, i can't test it.
jellysandwich
18th June 2006, 22:43
sorry
js
HieiYYH
19th June 2006, 03:28
http://forum.doom9.org/showthread.php?t=54130
Is the error on the same frame every time? If not and you're getting random, unrepeatable corruption, try this, as you may be pushing your system too near its limits. If so, it might be a bug in x264 and you should go back a couple versions.
You should also check that your command line doesn't contain anything related to aq, which are of unknown stability. (And no, turbo's fine if you're just going to drop the first pass.)
i don't think is my pc, i used to encode with x264 in virtualdub with 8fps average in mode 7 (rdo) without any errors, in megui the encode goes about 10-12, and i'm using LOW priority (maybe this?)
ps: tried to encode again in profile HQ-Insane, 3passes, the video errors are there again on 2nd and 3rdpasses (and it is random) :/ i think i'll go back to vdub -_- (No there's no AQ in command line) go back some versions? which version i should get?
even with the errors, i tried mux the video in yamb, i don't know why, the video has the same fps, same time, but the audio is playing too late (or the video is too fast) i don't understand -_-
Symptoms for hardware problems include:
- random reboots, system crahes often
- programs freeze, do not respond to user actions
- certain programs freezing during heavy use (e.g. when encoding)
i don't have those problems, the encode goes very well, and i can even play some emus :P
ps: the raw was a 120fps wmv9 one, so i reconverted to xvid 23.976fps, dunno if can be this too
berrinam
19th June 2006, 05:59
Have you tried multiple players, because I've had similar problems with VERY old versions of libavcodec.
Morte66
19th June 2006, 13:57
Bug report for 0.2.3.2170 AviSynth script generator. Examples are in the attachments. The story...
Create a AVS profile (e.g. Deinterlace No-Denoise.zip) that uses "Clever Anamorphic Encoding" with the Encode "non-mod 16" option. Close the "AviSynth script generator".
Open the "AviSynth script generator" again, and open a D2V file, like in AvsGen1.jpg.
Switch to the "Edit" tab, like AvsGen2.jpg, and you'll see # Set DAR in encoder to -1 : -1. The following line is for automatic signalling
global MeGUI_darx = -1
global MeGUI_dary = -1...which is not the right DAR.
Switch back to the "Options" tab, change your clever anamorphic option to "Resize to mod16" and back to the "Encode non-mod16" you started with. Switch over to the "Edit" tab, like AvsGen3.jpg, and you'll see that the script now says:
# Set DAR in encoder to 175 : 96. The following line is for automatic signalling
global MeGUI_darx = 175
global MeGUI_dary = 96...which is just what we need.
So it seems that the code to plant the aspect ratio in the script is not triggered all the times it should be.
It doesn't seem specific to non-mod16, I got the same problem when I created a profile that started with the option set to "Overcrop to achieve mod16", I still had to fiddle the option to get the DAR to propagate into the "Edit" tab.
acrespo
19th June 2006, 15:12
Thanks berrinam. Now I can press "Go" button in adaptative mux window.
I still have problem with mux AVI files. Both Autoencode or manual mux (Divx Mux window) can't mux avi files correctly. When I open the final video in virtualdub I receive this message:
Error decompressing video frame 0: An unknown error occurred (may be corrupt data). (error code -100).
If I open in Media Player Classic, it shows a gray screen.
The file size is 5 Mbytes less than a video muxed in virtualdub.
The log:
Starting job job4 at 10:58:51
encoder commandline:
-v "C:\encodes\Yu-Gi-Oh 199.avi" -a "C:\encodes\2006-05-02\ygh199.mp3" -o "C:\encodes\Yu-Gi-Oh 199a.avi"
successfully started encoding
Processing ended at 10:59:16
----------------------------------------------------------------------------------------------------------
Log for job job4
DivXMux: Version 6.1 Build Num: 36
Output File Streams:
TrackId 0: Video Stream: From AVI
Frame Rate: 23.976024
Resolution: 320x240
TrackId 1: Audio Stream: From MP3
SamplesPerSec: 48000
BlockAlign: 1
Creating Index...
----------------------------------------------------------------------------------------------------------
Job completed successfully and deletion of intermediate files is activated
Cantello
19th June 2006, 17:02
There's something up on your end with DirectShow which is causing problems. All I can really do is let MeGUI provide a more standard error message in that situation.
EDIT: That's what I've done in 0.2.3.2170. Can you test it to find out if it does just give a DirectShow error message instead of a crash? Since I can't reproduce the crash, i can't test it.
I don't have access to a binary of 0.2.3.2170. Is it available somewhere?
Or does anyone know about other methods to diagnose DirectShow problems and how to solve them?
edit: Nevermind, I found it. Will try with 0.2.3.2170 tonight and report my experiences.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.