Log in

View Full Version : meGui 0.2.10xx does not like avs files.


Pages : [1] 2

Hobojobo
27th December 2006, 18:59
I was wondering whether I am the onlyone who has got this problem:

Windows 2k plus SP4
MS .net 2.0
avisynth 2.56

meGui 0.2.4.10xx refuses to open avs files.
I get an error message:

The file .... .avs cannot be opened.
Please make sure it's a valid AviSynth script and that....
Error message for your reference: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

This happens even with a simple version() avs file.

meGui 0.2.3.2192 works though.
Funny, eh?

Any suggestions?

Adub
27th December 2006, 19:11
yeah, you are the only one.

What script are you using?

Hobojobo
27th December 2006, 19:21
For example:

DGDecode_mpeg2source("D:\13\VTS_01_1.d2v",info=3)
ColorMatrix(hints=true)
#blank deinterlace line
crop( 8, 2, -8, -2)

LanczosResize(704,400) # Lanczos (Sharp)
#denoise

Xplode
27th December 2006, 19:34
I have the same problem with 0.2.4.1022, but with another error message.
0.2.4.1019 and earlier versions works fine with the same .avs file.

Adub
27th December 2006, 20:04
can you play the avs in a different program like vdub or MPC?


You may also try updating to the latest avisynth. 2.57 rc2.

Hobojobo
27th December 2006, 20:10
Yep. I can play it in WMP and MPC.
And, as I said, in meGui 0.2.3.2192

anonymez
28th December 2006, 12:47
i get it too, 0.2.4.1023 :

http://img405.imageshack.us/img405/1073/clipboard1xt3.png

the script works fine in vdub etc, script consists of mpeg2source() and crop.

Gord
29th December 2006, 06:16
I've been getting that error since I updated to the 0.2.4.* series about 2 days ago.

I also get it when trying to load a d2v into the AVS Creator which is even stranger.

Hobojobo
29th December 2006, 14:41
latest version doesn't want to load avs scripts files on the OS drive, in this case C:, giving this error:

http://img405.imageshack.us/img405/1073/clipboard1xt3.png

works fine when moved to either of my other two drives. more info here (http://forum.doom9.org/showthread.php?t=119897)

EDIT: spoke too soon, worked a few times. stopped working again, regardless of drive. if i disable automatic preview in settings, it loads and encoding runs smoothly

Now I can queue and run the encoding jobs again.
Set up a avs file, especially cropping without a preview is kind of difficult though.

Thank you for the work around.

ChronoCross
29th December 2006, 16:42
make sure your using an up to date version of avisynth... I can't get this bug to appear. Anyone try using a debug version of megui with VS to see where the code fubars?

Hobojobo
29th December 2006, 17:56
I would try, but I haven't got the slightest idea how to do it.

debug version of meGui.

Is there a simple instruction for that?

Sharktooth
29th December 2006, 18:04
cant reproduce it...:(

ariga
29th December 2006, 18:09
I too face the same problem. First it complained of missing MediaInfo.dll (Not sure since when MeGUI required that, hadn't update MeGUI in ages.)

An avs with just AviSource() throws this error.

Henrikx
29th December 2006, 18:15
@Hobojobo
German Version MeGUI Wiki
http://gleitz.info/wiki/index.php/MeGUI
Mabey something changed by the Point Settings/Program Path
http://gleitz.info/wiki/index.php/MeGUI#Program_Path

Avisynth
http://sourceforge.net/project/showfiles.php?group_id=57023

Sharktooth
29th December 2006, 18:16
i repeat... it works here.
it must be something on your end.
http://www.webalice.it/f.corriga/temp/test.png

Ensure you updated ALL required files (including libs) with the Auto-Update feature...

Adub
29th December 2006, 21:22
Again as stated above, make sure that everyone is using an up to date avisynth build.

anonymez
29th December 2006, 23:34
avisynth is already updated (2.5.7 RC2), all required files (core, data, libs, avswrapper, dgdecode) are too

bob0r's build from x264.nl incase it's relevant

Hobojobo
30th December 2006, 00:17
It is beyond me.

I did the auto update.
I installed .net framework 2.0 and avisynth 2.56 and I tryed 2.57 RC2.

I tryed 2 computers. An Athlon XP 3200+ and a PIII 866 Mhz.
The OS on both is WIN2k.

I used the auto update.
Then I copied core 0.2.3.2192 into the meGui folder.
Everything works fine.

Then I replace the old build with core 0.2.4.1023.
The described error occurs. Everything else remains the same, settings, program paths...

Is there a problem with Win2k and the new build?

I just want to add: meGui rocks. Nice work and thank you for all the effort you put into it.

molpurgo
30th December 2006, 00:34
It is beyond me.

I did the auto update.
I installed .net framework 2.0 and avisynth 2.56 and I tryed 2.57 RC2.

I tryed 2 computers. An Athlon XP 3200+ and a PIII 866 Mhz.
The OS on both is WIN2k.

I used the auto update.
Then I copied core 0.2.3.2192 into the meGui folder.
Everything works fine.

Then I replace the old build with core 0.2.4.1023.
The described error occurs. Everything else remains the same, settings, program paths...

Is there a problem with Win2k and the new build?

I just want to add: meGui rocks. Nice work and thank you for all the effort you put into it.


I have same prob (Win2k, MeGui vers 0.2.4.1023), moreover in my machine, after alert,Megui crash.
thanks to all for hard workaround

http://img402.imageshack.us/my.php?image=meguicrashdt0.png

check
30th December 2006, 03:37
do you have a YV12 decompressor installed?

Sharktooth
30th December 2006, 04:56
I tried several avs scripts... but i still cant reproduce it.
I think it's something on your end...

Gord
30th December 2006, 05:11
The only thing that changed on my system between it working and not working was the updated core that allowed for multiple update servers.

It hasn't worked since then. I even updated to the latest AviSynth 2.5.7RC2.

Sharktooth
30th December 2006, 05:22
I dont know what to say. It's working perfectly here and if i cant reproduce the bug i cant fix it (supposing it's a megui bug...)

TwoToad
30th December 2006, 17:42
do you have a YV12 decompressor installed?

I am having the exact same problem too... Where might I check for a YV12 decompressor or where would one download one? Also, where can you find older versions of megui... x264.nl seems to only have the latest build.

Edit: er well, I found www.megui.org and tried using .1019 and no luck, I still come up with the same avs error. Not sure what the YV12 codec is yet... Going to try uninstalling avisynth, megui, updating .net 2.0, etc to see if that might fix anything....I'm only slightly retarded. =)

anonymez
30th December 2006, 21:07
i formatted my PC yesterday. just checked, meGUI now loads the script properly. same version as before the format

check
31st December 2006, 02:13
a YV12 decompressor can be found either as the 'helix YV12 codec' or as part of xvid.

TwoToad
31st December 2006, 03:04
i formatted my PC yesterday. just checked, meGUI now loads the script properly. same version as before the format

Ah, so wouldn't this mean that there is some software that is conflicting with megui / avs? I'll have to figure out what I've changed in the past few weeks...

check: Thanks! I didn't realize that Xvid was also a YV12 codec too. I did have Xvid installed. Also had CCCP installed too and thought there might be a conflict, so I uninstalled Xvid, but the error message was still there. *shrug*

check
31st December 2006, 04:17
hmm, you can use ffdshow as a decompressor too: open ffdshow vfw config, and in the codecs page, set uncompressed to 'all supported' (or just YV12 if you prefer).
Anyway, if that doesn't solve it, it does sound like some sort of conflict. Try removing all plugins from your avisynth dir and just opening a version() script.

molpurgo
31st December 2006, 18:24
what I do not succeed to understand is that the vers.0.2.3.1b work properly, but the last vers. not.
Both in the same machine.
Happy new year 4 all :))

seannyb
31st December 2006, 19:34
for the record, same problem here. Things worked fine just yesterday, then MeGui auto-updated some components just now, and now it doesn't want to open AVS files anymore -- including ones I've previously used w/ MeGui to encode stuff. I haven't manually installed any new codecs/components/etc. in between. Somehow the auto-update broke it today. I've deleted / reinstalled megui and avisynth to no avail.

edit: the error message I get -- "attempted to read or write to protected memory". Also very occasionally it'll pop up a slightly different error message about me being out of memory (I have 1.5 gigs though). If you're wondering about the yen signs, it might be worth noting I'm running windows in pseudo-Japanese mode.

http://www.seanny.net/junks/megui.png

TwoToad
2nd January 2007, 08:34
hmm, you can use ffdshow as a decompressor too: open ffdshow vfw config, and in the codecs page, set uncompressed to 'all supported' (or just YV12 if you prefer).
Anyway, if that doesn't solve it, it does sound like some sort of conflict. Try removing all plugins from your avisynth dir and just opening a version() script.

I'm sure it's a conflict somewhere, but it's weird that I can open the avs in Vdub or MPC, but it won't go through megui.

(attached is a shot of a vid I'm working on, will have to ask in another forum for help with a really cruddy dvd source.)

PsycoEwok
2nd January 2007, 09:20
I would just like to add that I, too, am having this same exact problem and have been having it since 2.4.x. However, I have my computer set to dual-boot Windows Vista and XP, so I tried it out in both operating systems. Interestingly, MeGui works just fine under XP, but not under Vista. It's only in Vista that I get this error. And again, I was NOT receiving the error under Vista until I updated to the 2.4.x versions.

I realize that maybe full support for Vista isn't really a priority at the moment, but I just thought I'd point it out since everyone has been saying that they're having this exact problem under Windows 2000. Just thought that maybe it's related somehow.

LoonyPhoenix
2nd January 2007, 23:32
Same here. Works in Windows XP, fails miserably in Vista.

Hobojobo
3rd January 2007, 00:32
I have got Win2k installed.
I even did a fresh installation without success.

Is there anybody running XP having trouble with 0.2.4.x ?
Could it be an OS related bug?

Sharktooth
3rd January 2007, 01:33
I dont have Vista to test it with.

ariga
3rd January 2007, 10:17
I face this problem on XP. Old versions of megui.exe work fine.

orangedude
3rd January 2007, 10:49
I have the same problem as original poster described ONLY on 0.2.10+ versions. I'm on Win2K SP4. Don't have XP to test it out with. MeGUI not only crashes when opening an avs file (same error msg as op) but also when trying to create one.

It works perfectly fine on 0.2.3.2193 and lower. No issues at all. Every component is upgraded to the latest EXCEPT the core. Then as soon as the core is updated, MeGUI just becomes broken on my system.

I registered on these forums JUST to report this bug. Who knows how many other people have got the same problem. I'm guessing it's crashing for every single Win2K user.

If someone out there has got Win2K and MeGUI new version working fine, please tell me how you got it working.

To the creators of MeGUI, I've gotta say it's the best tool out there for encoding X264 files right now. Keep up the great work but PLEASE fix this huge bug for all the win2k and vista users out there.


Edit: VirtualDub, Zoom Player, and older versions of MeGUI are all able to create/open up the avs files

Sharktooth
3rd January 2007, 14:48
http://forum.doom9.org/showthread.php?p=925820#post925820

Weltall
4th January 2007, 11:54
I have a similar problem. For me, what happens is that my system folders have unicode characters on them (I'm brazilian), and megui saves UTF-8 avs's files. When I save it again with notepad in ANSI format, I can open it. I wondered why that wasn't fixed, so I've noticed most of megui users don't have unicode characters on it. Is there a way to change that? Thanks.

Edit:
Wait, it's working now, megui is saving in ANSI nowwww. Who was responsible for this!?? Thanks!!

But I have another problem yet (as always): I can't open files which are in paths with unicode characters:
http://xs411.xs.to/xs411/07014/error.jpg.
Could you fix that Sharktooth, please!????

And one more: directshowsource weren't working for me with newers x264 versions (revs 6xx). I use avisource instead
cause I can use the avs to encode audio too. Could be an option to change to avisource (for avis, of course), instead of typing every everytime (I don't know why directshowsource has that audio=false, I think it's beacuse sound can't be encoded properly, am I right?). Since I convert various tvshows at once, I think it's very difficult to create avs, extract audio track to convert, join all. Someone knows a batch avisynth creator? Could megui create multiple avs at once (without that preview window), by selecting many videos, and put all that on queue with the same settings and bitrate, among with audio, using same avs and specified settings (just like autoencode but for multiple files at once)? That would be veeeeryyy great. Someone have the guts?

Sharktooth
4th January 2007, 14:36
remove the unusual characters from the path (and possibly from the filename too) and it will load.
the audio=false is there coz that's the script for Video... remove audio=false if you want to use the same script for audio. Also if directshowsource() doesnt work then you have problems with your codecs...
batch creation is not a megui feature but could be eventually implemented in future.

Weltall
5th January 2007, 00:23
I haven't problems with codecs. In previous versions of x264 I could get x264 working. I didn't test the last version yet, just 600 till 605. I saw some people having the same problem, I think it's the first pass. This is not a problem for me at all.

Anyway, about that path thing, that is an avisynth compatibility problem, not megui, so doesn't have so much to do with that thread.

About that I said, it'd be veeery nice, creating multiple avss for avis (avisource), queueing video and audio transcoding and muxing for everything o.O. Do you think it's hard to implement (I meant, that future is so distant)?

If I could save avisource (instead of directshosource+fps=*****+audio=false, I always have to edit that for avi conversion) by default in edit part of avisynth for avi's (like wildcards for extensions, using directshowsource for mkv, mp4, wmv and avisource for avi automatically), or resizing not marked automatically (like an option, cause I almost never resize encodes), that would be great too.

I know megui was created for dvdrip, but that implementatios could make megui even greater!

Thanks.

TwoToad
5th January 2007, 16:39
Ok, I found the solution that worked for me. It might work for others.

First uninstall avisynth and megui completely. Avisynth uninstall does not seem to remove the plugins directory, so you also have to manually delete (or move to a different location) the plugins directory.

Next reinstall avisynth and megui. This worked for me ONLY when I removed all my plugins manually (I moved them to my desktop temporarily).

There must be a plugin that autoloads and crashes megui. I haven't figured out which one yet, as I am going to put them back one at a time...

Edit: Just a thought, I wonder if you just removed all the filters, etc from the plugin folder, then re-added them one at a time would work. I think I read somewhere that the AviSynth autoloading plugin folder is limited to 50 plugins? So only keep the ones you use all the time there, and put the other filters in another location and use LoadPlugin("c:\otherplugins\filter.dll").

cockpit
6th January 2007, 03:53
well I just ran the update as well today and now I cant open d2v files with the avisynth script creator. I have checked the path 3 times to be sure, it is pointing to the correct folder.

the d2v opens fine with a simple script in vdubmod.
the error message megui gives also mentiones the memory error others have reported here.

check
6th January 2007, 05:36
twotoad & cockpit: sometimes there are avisynth namespace errors. I'd guess you have multiple plugins that use the mpeg2source() name. cockpit, try what twotoad said.

cockpit
6th January 2007, 17:28
I just did that too, and it still doesnt work.

migrena
31st January 2007, 22:13
its not avisynth plugins issue, removing them doesnt help
core 0.2.3.2193 is working ok, if i could get versions between 0.2.3.2193 and 0.2.4.1024 i could narrow down what causes this, where can i download them?

Sharktooth
1st February 2007, 15:04
when making a bug report please report your OS too and all the necessary info.

moadib2k
2nd February 2007, 00:54
Not sure if this is the same issue, I just posted to this thread

http://forum.doom9.org/showthread.php?t=95863&page=139

MaxPlanck
2nd February 2007, 05:56
experiencing the same exact error when loading avs...I'm running Windows Vista Ultimate

migrena
2nd February 2007, 11:05
ok i will ad system info here and in bug-report thread

machine: athlon xp 2500, 512MB, gf3ti 200 64MB
system: win2k sp4
other: cccp(06.12.15), real alternative(1.51), quicktime(7.14), xvid(1.2.127), avisynth(2.5.7rc3)

with older avisynth versions results were exacly the same

[edit]

hmm... why bug-report thread is closed?