There is no function called....

Corran · Post by **Corran** » Fri Sep 07, 2007 3:50 am

If I had to guess, I would say that the registry key that points to the plugin folder was somehow pointing in the wrong location...

RDphantom · Post by **RDphantom** » Fri Sep 07, 2007 6:26 pm

Corran, any idea why the registry key would suddenly not function correctly? I'd like to avoid this problem in the future if I can.

RD

Corran · Post by **Corran** » Fri Sep 07, 2007 8:51 pm

If the new version of avisynth was installed to a different location than the original install it would change the pointer.

Say for example if used to be installed C:/Program Files/AviSynth 2.5 but is now installed in D:/Program Files/AviSynth 2.5 the pointer in the registry would point to D:/Program Files/AviSynth 2.5/plugins. No matter how much you verified that you had the correct plugins in C:/Program Files/AviSynth 2.5/plugins, you would always get the mpeg2source function does not exist error.

To fix it without resorting to a system restore, you could go to Start -> Run And type regedit.exe and hit enter.

The key is located at:
HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth

Either copy the plugins you need to the location pointed to by the plugindir2_5 key or modify the key to point where you want it. Keep in mind though if the old plugin directory has outdated plugins, it would probably easier to just copy the few plugins that you need to the new plugin directory rather than changing the registry key or copying all of the old plugins to the new location.

This has personally happened to me once. I used to keep avisynth installed on my D drive and when I installed a newer version to the C drive, changes to my plugin directory on the D drive were not doing anything. I don't know really how your registry key may have been changed, this is just a guess based on what caused it for me. If you installed avisynth via the amvapp, it should have copied the plugins to the correct folder for you. If so then I'm a little confused as to why you had a problem like this.

RDphantom · Post by **RDphantom** » Sun Sep 09, 2007 7:40 pm

Corran, I did install avisynth via the amvapp, and have not changed my drives at all. I don't know if that was the issue or not, but I will most certianly keep your fix in mind if this problem happens again. Thanks so much for your input.

RD