The good old game: Premiere in After Effects

Bauzi · Post by **Bauzi** » Sat Jan 05, 2008 1:56 pm

Alright. Today I wanted to try out if I could import my Premiere project file in After Effects. First of all I relinked my media files in Premiere to my fakeavis from ffdshow´s "makeavis". Worked fine... better than I thought.

Than I simply imported the project. Of course it didn´t worked =/ Well I didn´t got an error message or a default picture (you usualy get it when you try to import avs directly in AE), but I didn´t got any frames. Just a black screen for each clip. Bad.

Anyway I get screwy error messages from my system. Everytime I click on a fakeavi in Explorer:

My philosphy: Never change a running system.
Well it works in Premiere, it just doesn´t in AE and I´m wondering if there is a general problem in AE or with ffdshow.

Help?

mirkosp · Post by **mirkosp** » Wed Jan 09, 2008 2:54 pm

Try to use VFAPI to make the fake avi files. It's included in the AMVApp 3.0 so I think you already have it.
It's easy to use and to me works great on every program (it works very well both on premiere and on after effects, even when I import premiere projects etc.).
The only problem you might encounter is that when you click on add job, you can't add files as there is no file extension compatible. If that happens you, than you have to use the readavs.dll and add a registry key.
Nothing hard. Just download the readavs.zip from here, put the readavs.dll in the same directory of vfapi.exe (which should be "C:\Program Files\AMVApp\Support Tools") and edit the readavs.reg so that the line:

Code: Select all

"Avisynth"="D:\\TMPGEnc\\ReadAVS.dll"

becomes:

Code: Select all

"Avisynth"="C:\\Program Files\\AMVApp\\Support Tools\\ReadAVS.dll"

Which should be your file path. If your readavs.dll's file path is different, just use yours and be sure to use " \\ " and not just " \ " in the file path.
After editing the .reg file, double click it and see if vfapi works with .avs files now.

Bauzi · Post by **Bauzi** » Thu Jan 10, 2008 10:08 am

Oh. VFAPI that bitch

I remeber that it ran perfect before I setted up my PC again. Now there is an "unsolfable" problem. It´s the reason why I switched to "makeAVIs".

The only problem you might encounter is that when you click on add job, you can't add files as there is no file extension compatible. If that happens you, than you have to use the readavs.dll and add a registry key.

Ah. Looks like a solution.

*after some time*
Eh. It made it worse. VFAPI can only open *.tpr (tmpeg projects) now.

mirkosp · Post by **mirkosp** » Thu Jan 10, 2008 10:39 am

Bauzi wrote:Oh. VFAPI that bitch
I remeber that it ran perfect before I setted up my PC again. Now there is an "unsolfable" problem. It´s the reason why I switched to "makeAVIs".

The only problem you might encounter is that when you click on add job, you can't add files as there is no file extension compatible. If that happens you, than you have to use the readavs.dll and add a registry key.
Ah. Looks like a solution.

*after some time*
Eh. It made it worse. VFAPI can only open *.tpr (tmpeg projects) now.

o.O Never had a thing like that happening. And readavs.dll was specifically made to solve the .avs compatibility issue. Now I should suggest you to check if you have any virus/spyware/crappy things like those. Sometimes they ARE the problem.