[user]

" 2) via real avi:
vob -> dvd2avi -> vfapi_avi -> VirtualDub creates a real (big) avi by Leadtools Mjpeg filter -> real.avi into CCE -> m2v

Both ways seem like pseudo avi to me since they both use vfapi. And since VDub can work with Avisynth directly there's really no reason to use (the SLOW) vfapi. Replacing vfapi with Avisynth on the "real avi" method should speed things up even more. "




(well, first the reason, why MB1 and Angel_SVCD take a big real avi as input for CCE (instead of TMpeg):
1. CCE (feeded with pseudo-avi by avisynth) is faster than Tmpeg (same method)
2. CCE feeded with real avi instead of avisynth's pseudo-avi is about 4 times faster !!! )



The point, why Leadtools Mjpeg filter is used for creating real avi by virtualdub is following:

Angel_SVCD had/(has still ?) on his site (German language) a comparison between a lot filters, eg. Leadtools Mjepg, Huffyuv and a lot others.
The result was clearly: The mjpeg filter in Virtualdub is really the Fastest for creating real avi (and later feeding CCE) from =>(vob->dvd2avi->vfapi (for creating *.d2v to *.avi, yes, a pseudo-avi as input for VirtualDub 1.4.10) -> Virtualdub => real.avi (very big))


I don't know, what makes LT filter so fast in combination with CCE, but has anyone tried creating real-avi by leadtools mjpeg, and later feeding divX5 ?
compared with vob -> divx5 and real-avi by huffyuv -> divx5 ?

well, in mpeg2, it made a huge difference, feeding CCE by LT's real.avi output, or feeding CCE by Huffyuvs real.avi..........