Log in

View Full Version : avisynth doesn't work anymore


Wilbert
29th December 2003, 20:03
Looks like my system is messed up. When I try to open an AviSynth script in wmp6.4 I get:

Ran out of memory

When I open it in vdubmod 1.4.13 I get:

Avisynth open failure:
Avisynth: script open failed!

Vdubmod 1.5.10 doesn't work at all anymore. If I try to open the program I get:

Microsoft Visual C++ Runtime Library

Runtime error!

Program: blabla

abnormal program terminiation

Why the hell is that, because I installed VC++ once?

Of course I installed vdmod and avisynth several times. Didn't help. Does that mean I have to reinstall W2K?

Schlumpf
29th December 2003, 20:26
I have a similiar problem atm.
My Virtual Dub Mod 1.5.10.1 doesn't crash right away, but whenever I change windows (with ALT+TAB , for example) it will crash with the message "An out-of-bounds memory access (access violation) occurred in module 'VirtualDubMod'."
This happens only with avs-files, not with avis.
Moreover, even if I close the preview-window (which apparently blocks the crash when changing windows), alter my avs-script and then try to reload the script, VDMod refuses to load it from time to time ("Unrecognized Exception"), although I didn't change something critical. Then I close the programm, restart, et voilą: The script is accepted again.

Win2K
Athlon 2600 XP
Avisynth 2.5.4 alpha from december, 19th

Leak
29th December 2003, 21:11
Originally posted by Schlumpf
I have a similiar problem atm.
My Virtual Dub Mod 1.5.10.1 doesn't crash right away, but whenever I change windows (with ALT+TAB , for example) it will crash with the message "An out-of-bounds memory access (access violation) occurred in module 'VirtualDubMod'."

You wouldn't happen to have the output pane deactivated all the time?

When I did this, it always crashed on me when I was ALT-tabbing to a different application. If I enable the output pane before loading an AVS script now it doesn't crash.

Strange, but at least it works.

np: T.Raumschmiere - Monoblock (The Great Rock'n'Roll Swindle)

Schlumpf
29th December 2003, 21:34
Originally posted by Leak
You wouldn't happen to have the output pane deactivated all the time?

Why... you're right. Since I use Avisynth filters almost exclusively nowadays, I found the output pane rather distracting and disable it by default.
But right now I have another problem: I can't reproduce the error :eek:
No matter how often I switch between windows now, nothing happens. I swear I still had a dozen of crashs this morning and I haven't (re)installed a thing since then.
I feel so dumb...

Leak
29th December 2003, 21:45
Originally posted by Schlumpf
Why... you're right. Since I use Avisynth filters almost exclusively nowadays, I found the output pane rather distracting and disable it by default.
But right now I have another problem: I can't reproduce the error :eek:

Well, the problem went away for me the instant I turned the output pane back on. Also, with the output pane turned off, playing the video for a second and stopping it again also cured the problem (up until the next reloading of the AVS file, of course...) - anyway, I've already mailed a bug report to Avery so I hope it'll work again in the next version. :)

np: Reinhard Voigt - Liebe Deine Musik (Total 5 comp.)

Lefungus
29th December 2003, 21:55
Some filters, just by their presence under the filter directory of avisynth create severe crashs, even if you don't call them.
Sometimes, it's best to just erase everything there, and see if it's better.

Wilbert
29th December 2003, 22:12
Some filters, just by their presence under the filter directory of avisynth create severe crashs, even if you don't call them.
Sometimes, it's best to just erase everything there, and see if it's better.
Thank god! That was the problem :) I will report which plugin was causing it.

edit: masktools 1.0.2 was causing this. Strange, did no one else have this problem with masktools?

edit2: it's a bit strange. I installed that plugin ages ago (and used AviSynth many times after that). I have no idea, why it suddenly gives problems.

Lefungus
29th December 2003, 23:11
The "guilty" plugin was also masktools for me :)

It's one reason why mftoon script was so unstable for me. Then vdub was crashing each time i closed an avisynth script.

Dreassica
30th December 2003, 00:10
Hmm..try the latest 1.4.2 masktools, that one doesnt make avs/vdubmod crash.

onesoul
17th September 2004, 00:44
Weird, I am glad I found this thread. I had same problem for a while, after reading I found that the troubled plugin was mergeclips.dll
But the weird part is that only started to happen after I intalled the latest alpha of avisynth 2.5.5.

ChronoCross
17th September 2004, 04:17
what I recommend to all users of mftoon is to use the Filters(Masktools and Warpsharp)that are linked in the mftoon thread as they have been tested for use with mftoon.

Manao
17th September 2004, 08:04
Latest masktools is 1.5.1, not 1.4.2 :sly: . However, for PIV users, with hyperthreading, beware of loading the masktools ( > 1.4.9 ) with loadplugin : it often makes avisynth report an error, though the cause is yet unknown.

Krismen
17th September 2004, 09:14
@onesoul

Take a look here:
http://forum.doom9.org/showthread.php?s=&threadid=82061

vcmohan
19th September 2004, 03:00
I have found that when I installed Avisynth 2.5.5 after I had DVX installation it did not work and gave same message as Script open Failure. I could trace the problem to the presence of "AntiBlink.DLL" in the plugins folder. I have posted this elsewhere in this forum.

Mtz
30th September 2004, 18:53
I had also this error in VdubMod. I deleted all the dll-s (54) from Avisynth Plugin Directory and then I restored them one-by-one and trying to open VDubMod after every dll restored.
The following dlls caused that
"Microsoft Visual C++ Runtime Library
Runtime error!
Program: blabla
abnormal program termination"

- Super8Equal.dll
- TCPDeliver.dll
- TemporalCleaner.dll

Hope this helps.

enjoy,
Mtz

Mug Funky
4th November 2004, 09:00
any news on the hyperthreading/masktools problem? i desperately want to use YV12lutxy on the box i'm on at the moment, but i just can't get it to work.

i only just discovered this problem because i'm using a different machine to the Old Faithful, p3 i'm used to.

Manao
4th November 2004, 09:08
Try these ones : i was desperatly in search of somenody with a p4 to test them :

http://jourdan.madism.org/~manao/MaskTools-p4.dll
http://jourdan.madism.org/~manao/MaskTools-p4-2.dll
http://jourdan.madism.org/~manao/MaskTools-p4-3.dll

The first one is expected to work, but doesn't have all the functionnalities of the two other ( it's 1.5.1, not 1.5.4 ). The other two are two attempts of 1.5.4 for p4, untested.

Note finally that I can't debug at all that bug, since it's not related to the masktools and since i don't own a p4. So anybody willing to test several versions of the masktools is welcomed ( the sad thing is that any new version will have chances to be bugged :(, and hence will require the same treatment ). Oh, finally, athlon's users can also use safely the p4 versions.

stax76
4th November 2004, 11:01
I have found that when I installed Avisynth 2.5.5 after I had DVX installation it did not work and gave same message as Script open Failure. I could trace the problem to the presence of "AntiBlink.DLL" in the plugins folder. I have posted this elsewhere in this forum.


the way how DVX deals with third party software was reimplemented from scratch. To avoid bugs the original setup routines and archives are downloaded and installed and to avoid system bloat and conflicts each module knows if it's required by the current project. Only software that is required by the default presets is included in the management console with excludes Autoblink, in the defaults are Decomb, AutoCrop, FluxSmooth, MPEG2Dec3 and DGDecode. Installing DVX should in no way harm or bloat the system, I've added to ask at uninstall if the settings should be deleted as well so it should leave no trace at uninstall (who would want to do that :D ).

Here are some screenshots:

http://www.planetdvb.net/dvx/dvx_paths_dialog_posted_at_doom9.png

http://www.planetdvb.net/dvx/dvx_paths_dialog_posted_at_doom9_2.png

MrTVideo
5th November 2004, 13:37
Don't know if this will help but I had a file on start up ctfmon.exe
I have disabled it but I do not know where it came from yet. With it running, Vdub crashes I have moved the file from the windows directory to the root directory just in case some application complains. All I know is that Vdub will not even load. Without it no worries.

Mug Funky
5th November 2004, 13:51
hmm. the office i was trying to run it on is full of p4 HT machines. only one of them still had HT turned on... the one i was on. i tried on one of the others and it worked. this is very strange... you wouldn't think Intel have broken backward compatibility with MMX?

i only just saw your reply :) i'll try it out as soon as i can (not sure when, maybe monday/tuesday)

Dali Lama
6th November 2004, 04:59
Originally posted by Manao
Try these ones : i was desperatly in search of somenody with a p4 to test them :

Manao, I have a Pentium M. Does that count as a P4? If so, what script should I use to test it (or just anything)?

Take Care,

Dali

Manao
6th November 2004, 09:43
Dali Lama : there is no hyperthreading with Pentium M if I'm not mistaken. Anyway, if when using the masktools ( either by making your own script or by using on of the several scripts made by peopole here ) you don't encounter unexpected behavior, then it's fine. Else, just post the script you were using. But you shouldn't have an issue, ( except if you use binarize(u=2,v=2), see http://forum.doom9.org/showthread.php?s=&postid=566564#post566564 ).