Log in

View Full Version : DGVfapi plugin question


ScottZ
10th July 2005, 03:01
I'm trying to get an avs into After Effects and looks like vfapi is the only way to go for now.

Using the 1.50EN version of Vfapi and the plugin that comes with 140rc6, I'm able to create a d2v vfapi avi, but getting a vfapi error for avs.

Of course the errors in vfapi are just ???? so don't know what the true error is.

Is there anything else needed to be done for avs in vfapi?
Assume the ReadAVS dll is not needed as the DGVfapi handles this.

I've made sure the DGIndex vfapi registry entry is pointing to the right place (and it's the only vfapi plugin entry there). DGIndex shows the vfapi checked in help.

Anything else?

Guest
10th July 2005, 03:18
Try putting ConvertToRGB24() at the end of the script. If that doesn't work please post your script.

ScottZ
10th July 2005, 03:45
I'm using the following 2 avs files for testing:


MPEG2Source("C:\temp\ROBD\hpdf\robd_1_ff.d2v",cpu=6)
ConvertToRGB24()
and


AVISource("c:\temp\junk.avi")
ConvertToRGB24()

They work fine in VirtualDub.

Still no go in VFAPI... Anything else to look at?

tritical
10th July 2005, 05:15
Some quick questions that could narrow things down. What version of avisynth are you using? When does the error occur? (when you click "Add Job" in vfapiconv.exe and try to open the avs file or when you click "convert"). When you click "Add Job" in vfapiconv.exe and select the avs file does the "files of type" box say "DGindex or AviSynth File (*.d2v;*.avs)" ?

I tested out loading and converting an avs file with just:

avisource("source.avi")

and it worked fine. The resulting avi opened in vdub fine as well, I don't have after effects to test though. Also, you shouldn't need to add converttorgb24() at the end unless you need to call it with interlaced=true or non-default matrix because dgvfapi will call it automatically if the output of the script isn't rgb24.

Guest
10th July 2005, 05:57
@tritical

>Also, you shouldn't need to add converttorgb24() at the end unless you
>need to call it with interlaced=true or non-default matrix because dgvfapi
>will call it automatically if the output of the script isn't rgb24.

It's not always converting correctly, it seems. I put ConvertToRGB32 at the end of a script and it converted fine to a pseudo-avi, but when I open it, it gave a black screen. Here is the script:

version
converttorgb32

Change it to converttorgb24 and it works fine.

Is there a bug you should fix? :)

tritical
10th July 2005, 06:09
It is definitely a possibility :), but I just tried a script with:

version
converttorgb32

and it looks fine when I open the psuedo avi in vdub or mpc. Perhaps it is a version problem with avisynth, I never throughly tested it with anything but 2.5.6. Unfortunately, I no longer have the source code for dgvfapi, could you post it somewhere?

ScottZ
10th July 2005, 06:58
AVISynth version is 2.55

VFAPI - it let's me add the avs to the job list, but errors when I hit run.

Files of Type - There are two choices:

Movie Files (*.d2v,*.avs)
DGIndex or AviSynth File (*.d2v,*.avs)

Works with d2v files and creates a vfapi.avi for them

tritical
10th July 2005, 07:17
Alright, I duplicated neuron2's problem when using v2.5.5 so there does seem to be a problem between versions on the converttorgb24 call. I think I might know where the problem is.

Guest
10th July 2005, 14:11
Cool. I put the current source here:

http://neuron2.net/misc/DGVfapi140rc7.zip

Guest
10th July 2005, 14:15
@scottz

Open TMPGEnc 2.5 and select Options/Environmental settings/VFAPI Plugin. You apparently have two D2V readers enabled. Get rid of all but DGVfapi. Also, be absolutely sure you are invoking the correct versions of DGVfapi and DGDecode.

tritical
10th July 2005, 22:03
Try this: [link removed]. Switching the order of the invoke calls to flipvertical/converttorgb24 seems to fix the problem with the official v2.5.5 release. Don't ask me why though :p... when I compiled v2.5.5 to see what was happening my compiled version worked fine with the original order.

ScottZ
10th July 2005, 22:27
Running an old DVD2AVI (1.77.3) does put another entry in the vfapi registry key.

I had checked the HKEY_CURRENT_USER->Software->VFPlugin registry key and made sure there was only the DGVfapi entry, but still wasn't getting anywhere.

Regardless, I changed some hardware around last night and reloaded XP from scratch. Saw your note after the fact.

I put vfapi105 and dgmpgdec104rc6 in their own directories and it worked fine with d2v and avs. For grins, I ran the old DVD2AVI again, removed it from the registry key, and still works fine... sooo... moving on.

NEXT!

BTW - As always - Many Thanks for the help guys - much appreciated

tritical
11th July 2005, 00:23
Here is the changed source: [link removed] for the version I posted before. All other files are the same. Like I said before all I did was change the order of the invoke calls and added a little bit more safety around the avs file opening. I tested it with v2.5.6 and v2.5.5 of avisynth.

Guest
11th July 2005, 23:02
Thanks, tritical. It's working good for me. I will absorb it into 1.4.0.