2.50 Is POS encodes same speed as Tmpeg 2.53

[Octagon]

Dang you guys. Keep braggin about CCE this...CCE that. I finally get the full ver of 2.50. Run Vdub with warp sharp and 2d Cleaner optimized filters and BAM. Same time to encode. I mean what is a .vaf file any ways? My 100 min anime (720*480) takes 12 hours or so in TMPEg 2.53. CCE is saying 6-7 hrs for VAF and then god knows how long it takes to transcode. AM I doing something wrong? and thereby making CCE slower than it should be? ALso the quality look just about the same between the two to me. Im running an avs script in Vdub, adding fileters, framserving it to CCE 2.50. Any help is apprecated.

[Faceman101]

CCE does have a much better speed for encoding than TMPGEnc, but that doesn't mean in all cases. Frameserving with VD has always slowed down my encoding times to the point where I don't even want to wait. CCE also depends on the speed of your comp, RAM, PIII or PIV.

[jdobbs]

CCE is much faster than TMPEGEnc. When feeding a VOB to CCE on my computer it does better than real time encoding. TMPEGEnc is about half as fast. In your case I think most of your encoding time is spent in VDub doing warp shape and 2d cleaner... It may also be converting from YUV to RGB and back. CCE is good, but can't make VDUB and its filters go any faster.

[baskarans]

hi jdobbs,

how do you feed VOB to CCE. Can you explain the method you follow. if you can send it to my email baskarans@yahoo.com

Thanks in advance
Baskarans

[Uli]

If you are frameserving with avisynth *AND* VirtualDub to CCE you need at least half a ton ( 512 MByte ), better 1 GByte of ram to get things at full speed. VirtualDub takes lots of ram when frameserving, just take a look in task manager. In the CCE manual ( ! ) you can read, that it needs at *least* 256 MByte and that 512 MByte are 'recommended', read required.
Youre encoding is obviously slowed down by swapping on harddrive.

greetz, Uli

[jdobbs]

baskarans,

I don't like to respond by private EMail as it doesn't share the message with the rest of the Forum. I use the standard AVISynth frameserving and Robshot encoding methods. It is well documented by Doom9 but below is a snapshot:

1. Install Smartripper, AVISynth, MPEG2DEC plugin, VFAPI, DVD2AVI, and CCE.

2. Run SmartRipper to get the VOBs onto your hard drive.

3. Run DVD2AVI to create a .D2V file and also break out the original .AC3. This takes about 3 minutes.

3. Create an AVISynth .AVS file containing the following (substitute your own paths):

LoadPlugin("C:\PROGRAM FILES\DVD-RIP\AVISYNTH\MPEG2DEC.DLL")
mpeg2source("d:\image\movie.d2v")
ResampleAudio(44100)

[You could also feed directly from VFAPI, but I find AVISynth with MPEG2DEC to be about 10-25% faster]

4. Open the .AVS file with CCE, set the parameters, and encode. If you have plenty of space (e.g. an entire DVD-R) you can set the Q to about 30-40, min bitrate to 0, and max bitrate to 9000 and you'll have good clean output in one pass (a two hour movie takes about 1.6 hours on my 1.3GHz Athlon TB). I prefer to optimize using Robshot's method so I can fit more than one movie on a DVD-R -- that requires a second pass. Two passes takes about 3.2 hours for a 2 hour movie, but also makes it possible to fit 2-3 movies on a single DVD-R.

I usually author with SpruceUp for simplicity, but I sometimes use Maestro. SpruceUp requires an IFOEdit modification for 16:9 movies.

jdobbs