Premiere Pro CS5 - avisynth.dll error

[Bauzi]

When I try to import an AVS script I get the following error message: "Failed to load avisynth.dll. Please reinstall Avisynth."

I can import it, but I have no images of the video.

Yes I reinstalled the newest version of Avisynth. Can you help me?

[BasharOfTheAges]

Which version of avisynth did you install? AFAIK, you have to use a 64bit one with CS5.

[Bauzi]

Eh... yeah that sounds highly plausible! Of course I don't have an x64 version. Can I run both versions on my system... somehow? I would miss a lot of nice filters.

I thought that I always used avs in CS5 all the time. Maybe I didnn't? Weird...

[EvaFan]

You can use both versions, but from my experience for example, if you index your dvds with the 32bit dgdecode.dll you will have to use 32 bit plugins etc. If you index your dvds with the 64 bit dgdecode.dll version then you can only use the 64 bit plugins.

What I'm trying to say is, Decide what version of avisynth you need to use before you index cause you can't change after unless you reindex with the other version.

[Bauzi]

Well right now I use x264 mkvs. They don't work with x64 DirectShowSource. The frames skip forward and backward. At least the x86 version works and I can make lossless avis for CS5. Than again... my hardware is full again >_>

[EvaFan]

It is possible to edit with avs files on cs5 if space is an issue. You just need 64bit avs and plugins. I should really write up a sticky of the process I went through to get 64bit avisynth and MT to work if no one else will.

If your worried about framerates, all you have to do is leave your deinterlacing, IVTC, geometrical filters, and color filters on there for editing (this should give you an fps above 30 assuming you have a decent processor but I use multithreading avs so I don't know otherwise). The rest like grain, smoothing, temporal filters you can just add when you render.

[mirkosp]

Postprocessing a rendered amv is a bad idea since it'll fuck up the effects too, and also it won't have quite as much temporal information: it is quite different to have a whole 5 seconds sequence than a few frames cut of it... and since Bauzi tends to abuse noise and grain in his vids, from what I saw, filtering after he's done would be bad.
If you got avs64 working, then use the 64bit version of ffvideosource, TheRyuu made the builds for it anyway and they are available on the googlecode page here along with the others. Though, the version is a bit outdated compared to the 32bit one. Wonder if he'll bother making a newer build.
EDIT: Uh... nevermind, the 64bit version seems to be more recent than the 32bit one.

[EvaFan]

Postprocessing a rendered amv is a bad idea since it'll fuck up the effects too, and also it won't have quite as much temporal information

You misunderstand , I meant add those filters back into the script you imported into premiere for source before you render on whatever program your using. Not postprocessing.

This is what I do to edit full script videos without a single fps problem. Even If I'm having problems on a certain part of the video where there are large fx additions, I just use the render preview file option in premiere and that part plays flawlessly when previewing.

[Bauzi]

Oh you missunderstood me. I don't have frame drops. The frames jump back and forth in the x64 version.

Usually I have a set of scripts. The full ones with all the filters applied and the fast ones for editing. I just close the project. Swap the files with some copy+replace and reopen the program again. Due to the improvement of the Media Encoder in CS5 I can queue all my clips before I switch to full scripts. Spares a lot of time, because with full sripts, marking clips for output can get really slow.

[EvaFan]

buy the dvd's and don't edit by loading x264 mkvs with avs then