Unable to open Avisynth scripts.

[maksik]

Hello, all!
Everything was fine, untill today. I can't open any avisynth script:
WMP - "Not enough storage to complete this operation" - !!!!
BSPlayer - "Unknown file format"
VirtualDub - "Avisynth open failure: Avisynth script open failure"
CCE2.50 - "AVIFileInfo - Unknown error"
What to do?
I have installed and reintalled Avisynth 2.07. No other versions of
avisynth.dll found...
:confused:

[Guest]

What happens with this simple script:

Version()

[maksik]

Thanks for answering.
Even on simplest script like Version() I got the same errors.

[maksik]

Originally posted by neuron2
What happens with this simple script:

Version()
Thanks a lot. I found solution with help of good people from forum.ixbt.com. There was a wrong .avs script it avisynth root directory...

[sh0dan]

@all: Should we modify AviSynth 2.5 and 2.0x, so that in order for an AVS-file to be auto-included from the plugin directory, it should have an ".avsi" extension?
(AviSynth Include or AviSynth Script Include, or whatever it stands for?)

This is beginning to annoy me!

[maksik]

Without kidding, I think the answer is YEs.
Why, as average level user, should I expect avisynth will autoload .avs files from plugin directory?

[frank]

Oh no. The extension avs means avs instructions.
Plugins are avs scripts.
Then it's better to implement a switch to disable the plugin directory.

[sh0dan]

@frank: But the average user doesn't know that AVS files in the plugin-directory are auto-loaded. And since many plugins are including sample files (a good thing!!) the user doesn't know they affect the scripts they are writing.

On the other hand, if they want to have some avs included, they know the feature exist, and therefore knows that they have to give it a ".avsi" extension instead. Also if someone is releasing scripts for the plugin directory, they will also know that it has to be called ".avsi". IMO we have everything to win, and nothing to loose.

[trbarry]

@all: Should we modify AviSynth 2.5 and 2.0x, so that in order for an AVS-file to be auto- included from the plugin directory, it should have an ".avsi" extension?
(AviSynth Include or AviSynth Script Include, or whatever it stands for?)

This is beginning to annoy me!

Strongly, YES.

- Tom

[hakko504]

I agree: My first thought was AVisynth Include, but that could create even more confusion...:rolleyes: :D :devil:

[Wilbert]

On the other hand, if they want to have some avs included, they know the feature exist, and therefore knows that they have to give it a ".avsi" extension instead. Also if someone is releasing scripts for the plugin directory, they will also know that it has to be called ".avsi". IMO we have everything to win, and nothing to loose.

Except that the avsi scripts still can contain errors. Besides that, the validity of those scripts can also depend on which version of AviSynth you use. Maybe it is better to disable the option "AVS files in the plugin-directory are auto-loaded" completely.

[Boulder]

Originally posted by sh0dan
@all: Should we modify AviSynth 2.5 and 2.0x, so that in order for an AVS-file to be auto-included from the plugin directory, it should have an ".avsi" extension?
(AviSynth Include or AviSynth Script Include, or whatever it stands for?)

This is beginning to annoy me!

All three thumbs up in here:D

[Evil Andy]

A plan with no drawbacks. Gets a thumbs up from me.