d2v file will not open in TMPGEnc!!!!!!!!

[g child]

I ripped my files and saved the project in DVD2AVI but my problem is when I got to open up the .d2v file that I created in TMPG, it tells me that the file format is unsupported!

Can someone please let me know what the deal is? I am trying to follow the steps from DVD 2 DVDR for Dummies, and my dumb butt can't get past this part!

If anyone has a link to a simpler guide please let me know, thanks!

[Treebeard]

do you have the vfapi plugin for tmpgenc to read *.d2v files?
make sure it is in the TMPGEnc folder.

if still not work up the vfapi reader priority in the environemental settings

[g child]

Also, are there any better guides than DVD 2 DVDR for dummies? I've read the Newbie DVD to DVDR guide, No hacking VOB guide, Cretin's guide and a few other but seem to be having problems with all of them... I guess I'm just not that smart!

[g child]

Okay, the vfp file from DVD2AVI is now in the TMPG folder and it now sees the d2v file but when I try to open it it still tells me that the file is unsupported.

[DacaBBa]

I'm a newbie at this and I'd been getting the TMPGEnc error concerning D2V project files. Using CladXP I'd rip the VOBs and let it automatically frameserve them with DVD2AVI. The problem occured when I'd copy the D2V, WAV, and VOB (Do you need the VOB? Like I said I'm a newbie) onto another computer (over a LAN) so I didn't have to encode them on my main computer. Then that ugly "not supported" error kept popping up. When I used DVD2AVI and created the D2V project on the same computer it worked perfectly fine! Don't know why, but I thought this may help any other newbies that are copying there files to alternate computers before encoding them...

[BJ_M]

i tend to always do encoding across networked computers as it really speeds things up .. of course all the drives need to be shared and mapped .. i map all drives used for frame serving/encoding so they are the same on 4 computers .. so it doesnt mater on which machine frame serving is from or going to .

for example - W X Y and Z drive are each on a different machine and mapped to the same drive letter on each of the other machines ... vdub and dvd2avi frame serving is normally slows down things but do the serving on a different machine works very well ..

[mrhua]

I'm a newbie at this and I'd been getting the TMPGEnc error concerning D2V project files. Using CladXP I'd rip the VOBs and let it automatically frameserve them with DVD2AVI. The problem occured when I'd copy the D2V, WAV, and VOB (Do you need the VOB? Like I said I'm a newbie) onto another computer (over a LAN) so I didn't have to encode them on my main computer. Then that ugly "not supported" error kept popping up. When I used DVD2AVI and created the D2V project on the same computer it worked perfectly fine! Don't know why, but I thought this may help any other newbies that are copying there files to alternate computers before encoding them...

Yes, you need the VOB files; don't delete them. The D2V file is a pointer back into the VOB files.

Also, when you make the D2V file with DVD2AVI, it puts in the pathname embedded in the D2V file. I've never tried, but if you have the files in D:\DVDRIP\ on one computer, try copying all files to another computer in a D:\DVDRIP\ directory. If that doesn't work, then, I don't think it ever will.

If you just want to use another computers CPU, then, the best way is to rip the vob files, then move them to a 2nd computer, then use DVD2AVI on that 2nd computer, and it should work fine.

[medievil]

Not only does the d2v vfapi plug in need to be in the tmpeg folder, but you also need to start dvd2avi and make sure there is a check beside vfapi in the options menu. (You only have to open it once to make this check, cause it's held in the registry)