AviSynth not working?!

[an3k]

Hi,

i'm ashamed. I can't get AviSynth working.

I've done a fresh installation of Windows XP Prof. SP3 with all security updates. I installed QuickTime Pro. I installed AviSynth (important files goes to C:\Program Files\AviSynth, not to Windows directory). Im logged in as Administrator.

I create a test.avs with Version() in it. I open it in Media Player 6.4 or 11 but it tells me there is no Codec installed required for playback.

There is a AviSynth_Template.reg in the AviSynth directory. If i apply it and check the registry some information are not added (like HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth\plugindir2_5="%INSTALLDIR%\plugins") and some are added (like HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth\@="%INSTALLDIR%")

I already tried replacing %INSTALLDIR% with the correct directory (%PROGRAMFILES%\\AviSynth 2.5\\) but this also doesn't help.

One of my old, previously working avs-scripts doesn't work too. It only contains OpenDMLSource("uncompressed.avi"). If i play uncompressed.avi in the same player, the file is played back well since its not compressed with any codec.

What's going on here? Thank you very much!

[an3k]

Got it working now. The AviSynth setup is not correctly working.

If you choose "Standalone" the whole setup is broken, even if you're administrator. No information are added to registry, no uninstall information are added, etc.

[IanB]

:EDIT: Apologies, the German version of the text for the "Standalone Unpack files only" has been truncated in translation to just "Standalone", this is obviously confusing.

What is it with people and the standalone unpack type install recently. The "Standalone, Unpack files only" type of install is exactly what it states, Unpack files only. No information is added to registry. No uninstall information is added. No files are added to the system directory.

This install type is intended for people who cannot gain administrative access to the target machine. It provides all the files and information for an advanced user to manually install Avisynth.

If you want a working Avisynth install then choose the "Standard" type of install.

[an3k]

What is it with people and the standalone unpack type install recently. The "Standalone, Unpack files only" type of install is exactly what it states, Unpack files only. No information is added to registry. No uninstall information is added. No files are added to the system directory.

This install type is intended for people who cannot gain administrative access to the target machine. It provides all the files and information for an advanced user to manually install Avisynth.

If you want a working Avisynth install then choose the "Standard" type of install.I re-checked the setup. The guy who translated it made a big failure! He just dropped "Unpack files only", thus German translation only shows "Standalone" and cause of the entry "AviSynth Base (required) > Install files in product directory" you think that all files will be installed into the product directory.
Not my fail!

If you cannot gain administrative access you don't have access to the registry, thus you cannot apply the registry settings you need in order to get AviSynth working. The Standalone "Setup" is somehow useless then.

[talen9]

If you cannot gain administrative access you don't have access to the registry, thus you cannot apply the registry settings you need in order to get AviSynth working. The Standalone "Setup" is somehow useless then.

You don't "need" the registry key for AviSynth scripts to work correctly. Note what IanB wrote:

It provides all the files and information for an advanced user to manually install Avisynth.


The scripts will work correctly, provided that you explicitly load each and every plugin needed (via LoadPlugin() ) specifying the entire path to the DLL.

[stax76]

It means installing AviSynth not the key for the plugin dir. The hook VFW provides to make applications like AviSynth possible is COM based so it will definitively involve writing to a area in the registry that needs admin privileges for write access.

[an3k]

If you don't tell windows to use avisynth.dll + devil.dll (and perhaps msvcp60.dll) for avs scripts you cannot use AviSynth. The only way to tell Windows that information is the registry!

On this computer i used "Standalone" too and i tried the following script some seconds ago:

# Prints out version information
LoadPlugin("C:\Programme\AviSynth 2.5\avisynth.dll")
LoadPlugin("C:\Programme\AviSynth 2.5\devil.dll")
LoadPlugin("C:\Programme\AviSynth 2.5\msvcp60.dll")

Version()

IT DOES NOT WORK!

[buzzqw]

i don't need to load devil and msvcp...

BHH

[an3k]

i don't need to load devil and msvcp...

BHH

Did you installed AViSynth using "Standalone"?

[stax76]

You was already told to use the standard install type so what is the problem now? Did you really expect you can pass anything other than a AviSynth plugin to the LoadPlugin function?

[an3k]

Warum dreht heute eigentlich jeder Idiot am Rad?

You was already told to use the standard install type so what is the problem now? Did you really expect you can pass anything other than a AviSynth plugin to the LoadPlugin function?

1) Read carefully.
On this computer i used "Standalone" too ...So hard to understand? Especially for you: I have two computers here. On the first one (on which i'm working) i used "Standalone" and figured out to use "Standard" BEFORE anyone wrote a reply. On my second computer (on which i normally play games, browse the web, watch videos, listen to music, etc.) i still have the "Standalone" setup and on this one i tried what advanced user talen9 said....loading the required files.

I know that these aren't AviSynth plugins and loading them is stupid but since you guys (especially the WTF developer of AviSynth! (btw. get parents who can give you some education)) cannot provide any information on how to get AviSynth working using "Standalone" i tried that.

2) Sorry that i try to figure out if the developer has to fix something in the setup or not. At least he has to fix the wrong translation.

[stax76]

The Standalone setup type is for advanced user, it's quite obvious you are a not a advanced user so this type of setup is not intended to be used by you.

[an3k]

The Standalone setup type is for advanced user, it's quite obvious you are a not a advanced user so this type of setup is not intended to be used by you.

Instead of being unfriendly you could do whats the forum is for: helping other people!

It means installing AviSynth not the key for the plugin dir. The hook VFW provides to make applications like AviSynth possible is COM based so it will definitively involve writing to a area in the registry that needs admin privileges for write access.

You said it yourself. I need admin privileges to get AviSynth working but wait ... "Standalone" is for users who cannot gain administrative access ...

[stax76]

Your behavior isn't any better. ;)

[Leak]

You said it yourself. I need admin privileges to get AviSynth working but wait ... "Standalone" is for users who cannot gain administrative access ...
Applications are free to load AviSynth.dll themselves and use it directly; you only need to tweak the registry if you want opening AVS files via VfW to work.

ffdshow for instance uses AviSynth directly and couldn't care less if AVS scripts are registered with VfW/Windows or not...

np: Squarepusher - My Red Hot Car (Warp20 (Chosen) (Disc 1))

[an3k]

Your behavior isn't any better. ;)

No, mine isn't right.

The first reply i got began with WTF.
The second reply stated i'm not an advanced user, thus a novice.
Then your reply stating indirectly me to shut the fuck up because others already replied.

I wasn't the one who started being unfriendly.

Glaub mir Kleiner, du hast echt das Fass zum überlaufen gebracht. Dich such ich mir raus und dann kannste dir überlegen wie du jemals noch ein Update für StaxRip rausbringen willst.

[an3k]

Applications are free to load AviSynth.dll themselves and use it directly; you only need to tweak the registry if you want opening AVS files via VfW to work.Thanks for your reply and yes, you're right.

BUT

As the other guys said. Standalone is for people who cannot gain administrative access = cannot write to the registry.

But if i cannot write to the registry i cannot open avs files via VfW, thus the "Standalone" is completely useless.

@ IanB: Btw. advanced users just extract the files contained in the setup, they don't need such a stupid setup option.

[stax76]

@an3k

Please read the forum rules again, in particular rule 4 and 13.

[an3k]

@an3k

Please read the forum rules again, in particular rule 4 and 13.

@stax76

Please read the forum rules again, in particular rule 2, 4, 17.

However, we'll meet us, if you want or not.

[stax76]

@an3k

I'm sorry for being not nice but I think you are going to far, please tell me how exactly do we meet?

[MuLTiTaSK]

@stax76

it's better to leave it alone cause sometimes trying to help someone leads to confusion :o

[IanB]

I re-checked the setup. The guy who translated it made a big failure! He just dropped "Unpack files only", thus German translation only shows "Standalone" and cause of the entry "AviSynth Base (required) > Install files in product directory" you think that all files will be installed into the product directory.
Not my fail!
Yes, you are right, the other instances were German also. I apologise on behalf of the translation team for this omission. :o


Can you provide an improved translated text?


If you cannot gain administrative access you don't have access to the registry, thus you cannot apply the registry settings you need in order to get AviSynth working. The Standalone "Setup" is somehow useless then.
And yes without the HKCR keys the VFW interface to Avisynth cannot work.

Applications that use only the C or C++ API interfaces can be encouraged to work with a little help

:search: Search for "Portable Avisynth" for a fuller discussion on getting around the no admin access problem. This was why the "Standalone Unpack files only" type install was created.