PDA

View Full Version : Suggestion to improve VFAPI speed

DVDHack
8th February 2002, 01:23
I might be alone in this but I have rarely (never I think) had CCE freeze during the VAF file creation. Is it possible that DVD2SVCD could use avisynth to create the VAF and then use VFAPI for the actual encode process - it would save between half and hour and an hour in the encode process.

My PC does vaf at 0.9 using VFAPI but about 1.45 using avisynth.
markrb
8th February 2002, 02:30
DVD2SVCD only uses VFAPI if you use safemode. Other than that it uses Avisynth.

Mark
DVDHack
8th February 2002, 02:34
My point is that when using safe mode it is unnecessary to use VFAPI to produce the vaf file as that does not seem to cause a problem.

So...

avisynth for vaf
and vfapi for mpv

in safe mode.
DDogg
8th February 2002, 04:41
My point is that when using safe mode it is unnecessary to use VFAPI to produce the vaf file as that does not seem to cause a problem.

I see what you are driving at, but think it out just a little more. The safe mode is there to provide removal of the direct AVS transfer of the data to CCE. It might work for you but this would negate the main purpose which is providing an alternate method. Also, this would not work on 2.62 which is another reason it was put in.

I would also think D2S would be way against creating a VAF with one method and encoding with another as the VAF has to be a guide for the encode that is dead nuts accurate.