vfapi problem .....

[0verd0ze]

Hey !

i wanted to teach my friend how to make a xvid encode ...but when he was gonna use "vfapi" , he got some strange language on it and vfapi could only add *.tpr files ... and i gave him the one i use .... anyone know why this happens ?

is there maybe another way to do it ?

why im using vfapi is to be able to use it in vdub ....

[jimmalenko]

The only time I can recall needing to use VFAPI to input a file to virtualdub is if you have a D2V ffrom DGIndex/DVD2AVI. As it stands, with the creation of virtualdubmod and virtualdub-MPEG2, all you need to do now is rip in IFO mode, outputting to one big VOB and then there's no need to frameserve.

What's the source ?

[0verd0ze]

Source is DVD and yes it DVD2AVi

[jimmalenko]

Do you think your friend might be better off with a more newbie-friendly app such as fairuse or AutoGK before learning the "manual" way ?

[0verd0ze]

hes knows some about that stuff ... but our problem is that he cant get vfapi to work at his place ...

[jimmalenko]

So you're trying to feed it a D2V and nothing happens ?

Does he have the same version as you ?

What version of DVD2AVI ? Tried DGMPGDec ? DGIndex ?


Details, man !

[celtic_druid]

If someone is still using VFAPI, then no offense but they don't know enough. VFAPI means a forced RGB24 colourspace conversion.

XviD is YV12, DVD is YV12. Keeping the entire encoding process YV12 increases both speed and quality.

Check out AVISynth/dgdecode.

[0verd0ze]

If someone is still using VFAPI, then no offense but they don't know enough. VFAPI means a forced RGB24 colourspace conversion.

XviD is YV12, DVD is YV12. Keeping the entire encoding process YV12 increases both speed and quality.

Check out AVISynth/dgdecode.

sound like too much work with AVISynth :P but i can try DGDecode

[Safesurfer]

It's very easy to generate an AviSynth .avs file automatically with DGMPEGDec if you set up a template file. You could then just load the .avs file directly in VDub instead of using the .d2v file and vfapi.

Here's the relevant part from the manual -

DGIndex can automatically generate an Avisynth script for serving your project.

Suppose you have a script that you use all the time. Maybe like this:

loadplugin("...\DGDecode.dll")
loadplugin("...\Decomb.dll")
mpeg2source("myvob.d2v",cpu=6)
fielddeinterlace()

Copy the following file to the same directory where DGIndex is located, and call it 'template.avs'. Then edit it to replace the D2V file name with __vid__ (that's two underscores before "vid" and two after). It should then look like this:

loadplugin("...\DGDecode.dll")
loadplugin("...\Decomb.dll")
mpeg2source("__vid__",cpu=6)
fielddeinterlace()

After performing a Save Project operation, DGIndex uses this file as a template and inserts the right file name whenever it sees __vid__.

DGIndex creates the AVS script file only if it does not already exist. The script file is created in the same directory as the d2v file.

[celtic_druid]

You also need to add cropping/resizing, etc. If you do that in VDub, then you may have well have just used VFAPI, since VDub filters require RGB24.

Too much work? Isn't that the point of doing things manually. No point cutting corners or you may as well go the AutoGK, FairUse, etc. route since it will give you better quality anyway.

[0verd0ze]

It's very easy to generate an AviSynth .avs file automatically with DGMPEGDec if you set up a template file. You could then just load the .avs file directly in VDub instead of using the .d2v file and vfapi.

Here's the relevant part from the manual -

DGIndex can automatically generate an Avisynth script for serving your project.

Suppose you have a script that you use all the time. Maybe like this:

loadplugin("...\DGDecode.dll")
loadplugin("...\Decomb.dll")
mpeg2source("myvob.d2v",cpu=6)
fielddeinterlace()

Copy the following file to the same directory where DGIndex is located, and call it 'template.avs'. Then edit it to replace the D2V file name with __vid__ (that's two underscores before "vid" and two after). It should then look like this:

loadplugin("...\DGDecode.dll")
loadplugin("...\Decomb.dll")
mpeg2source("__vid__",cpu=6)
fielddeinterlace()

After performing a Save Project operation, DGIndex uses this file as a template and inserts the right file name whenever it sees __vid__.

DGIndex creates the AVS script file only if it does not already exist. The script file is created in the same directory as the d2v file.

OK that doesnt seem to hard ...will def. try it ... but the audio is now a problem ... i dont know the right way to do it .. if i should add it in vdub with the *.avs or do it in nandub ...

[Safesurfer]

Sorry, I left out the bit about audio, but you can do that too.

You may also use the __aud__ specifier to generate the audio file name. Note that if you are generating more than one audio file, this specifier will refer to the last audio file that is opened. Therefore, to be sure to get the desired audio file, process just one audio stream.

So a basic Template script might be:-

loadplugin("C:\Program Files\DGMPGdec\DGDecode.dll")
video=mpeg2source("__vid__")
audio=DirectShowSource("__aud__")
AudioDub(video, audio)

Note I used DirectShowSource to load the audio instead of the command wavsource, so that AC3 or MPA audio can be loaded and not just WAV. Remember though that you'll need to have an AC3 decoder installed for VirtualDub, such as AC3 ACM Decompressor.

Hope this helps.

[0verd0ze]

on the first sample they got ,cpu=6 .... what does that mean... i have checked dg's manual "Post-Processing Quickset Options" ..but what does it mean ? what does it do ?

Loadplugin("F:\XviD-Apps\DGMPGDEC\DGDecode.dll")
Loadplugin("F:\XviD-Apps\AviSynth 2.5\plugins\Decomb.dll")
Video=mpeg2source("__vid__")
Audio=DirectShowSource("__aud__")
AudioDub(video,audio)
FieldDeinterlace(full=false) <--- Deinterlace method : blend ? .. possible to set that like in VDubmod
LanzcosResize(512,384)

is it possible to do some final settings in Vdubmod after you have opened the avs in vdub ?

[Safesurfer]

I'm no expert on this, have a look at the DGDecode Manual for what these options mean. I think if your source is MPEG2, you probably don't need to use any of these and my basic script will suffice. Similarly, only use the Decomb and deinterlace settings if you need to. Once the file is loaded in VDub, you can use any of VDubs features or filters, just as you would on a normal AVI file.

[celtic_druid]

Nic modified some plugins from I think TFM to create AVISynth plugins. You might want to check that out for the AC3.

NicAC3Source("FileName.ac3", int "Downmix")
2 for downmix will give you 2 channels.

Personally I would process it externally with say BeSweet or HeadAC3he though.

[manono]

Once the file is loaded in VDub, you can use any of VDubs features or filters, just as you would on a normal AVI file.

You could, but you wouldn't want to, as then you'll lose most of the benefits of using AviSynth in the first place.

You use VDub filters, you have to use Full Processing. You go AviSynth alone, you use Fast Recompress. The benefit of Fast Recompress? 25-30% faster encoding, no colorspace conversions, and better quality.

FieldDeinterlace(full=false) <--- Deinterlace method : blend ? .. possible to set that like in VDubmod

Yes, the default FieldDeinterlace setting is for Blend. If you set Blend=False, it'll interpolate. Both are lousy compared to other AviSynth deinterlacers, such as KernelDeint. And be real sure that your video is truly interlaced before using a deinterlacer, even if set for Full=False. Don't just rely on the DGIndex Statistics window. It tells you how it was encoded and not what the source is like, often 2 very different things.

Yes, read the DGDecodeManual for what the CPU settings mean. That was just an example. I, for one, would never even consider using CPU=6. And also read the DecombUsersManual. neuron2 (Don Graft) writes the best guides/tutorials for his filters in the business. You'll learn a lot by reading what he has to say, much more than asking a bunch of questions when you haven't even done your homework. And for more about AviSynth, read everything on the www.avisynth.org site.

[0verd0ze]

I'm no expert on this, have a look at the DGDecode Manual for what these options mean. I think if your source is MPEG2, you probably don't need to use any of these and my basic script will suffice. Similarly, only use the Decomb and deinterlace settings if you need to. Once the file is loaded in VDub, you can use any of VDubs features or filters, just as you would on a normal AVI file.

soo you saying that i dont need Video=mpeg2source("__vid__") ? and yes the source is mpeg2(dvd that is) .....

and about the audio part ... i would lose the benefits if i would add the audio in Vdub right ?

Once the file is loaded in VDub, you can use any of VDubs features or filters, just as you would on a normal AVI file.

You could, but you wouldn't want to, as then you'll lose most of the benefits of using AviSynth in the first place.

You use VDub filters, you have to use Full Processing. You go AviSynth alone, you use Fast Recompress. The benefit of Fast Recompress? 25-30% faster encoding, no colorspace conversions, and better quality.

FieldDeinterlace(full=false) <--- Deinterlace method : blend ? .. possible to set that like in VDubmod

Yes, the default FieldDeinterlace setting is for Blend. If you set Blend=False, it'll interpolate. Both are lousy compared to other AviSynth deinterlacers, such as KernelDeint. And be real sure that your video is truly interlaced before using a deinterlacer, even if set for Full=False. Don't just rely on the DGIndex Statistics window. It tells you how it was encoded and not what the source is like, often 2 very different things.

Yes, read the DGDecodeManual for what the CPU settings mean. That was just an example. I, for one, would never even consider using CPU=6. And also read the DecombUsersManual. neuron2 (Don Graft) writes the best guides/tutorials for his filters in the business. You'll learn a lot by reading what he has to say, much more than asking a bunch of questions when you haven't even done your homework. And for more about AviSynth, read everything on the www.avisynth.org site.

Yup, i sure that the source is interlaced ....
And hehe , i will read the manuals and check the website, but i just needed some help to get there :P

btw ... lets say i use BeSweet to convert the ac3 to mp3 ... should it still be "DirectShowSource" ?

[Safesurfer]

soo you saying that i dont need Video=mpeg2source("__vid__") ? and yes the source is mpeg2(dvd that is) .....

and about the audio part ... i would lose the benefits if i would add the audio in Vdub right ?

Um.....no, not saying that at all, without those lines the template avs file won't work!

I was just saying you could use a basic script (without any of the options) such as

loadplugin("C:\Program Files\DGMPGdec\DGDecode.dll")
video=mpeg2source("__vid__")
audio=DirectShowSource("__aud__")
AudioDub(video, audio)

If you want/need to deinterlace, add the deinterlace commands to this. If you want to import both video and audio via Avisynth into VDub, you need the video =__vid__ , audio=__aud__, and audiodub lines. If you add the audio via VDub, you don't lose anything, that only applies to the video part.

[0verd0ze]

ok ! thanx alot for all the help think i'll manage from here