cce- massive file size

[tonymac]

Using cce to process a file frameserved by vfapi from a dvd rip. Set 3 pass vbr with average bitrate as 4500 to reduce original file in size by about 10% (was 5000 average bits). Cce did the passes in 5 hours then proceeded to write the file. After 3 hours, 20% had been done, but the file size was over 2 gigs! Would have been 11 gig at the end, twice the size of original. What have I misunderstood here?
Do I need 3 pass anyway? If I use one pass vbr I cannot set the bitrate as I do not understand the relationship of q value to final file size.
I must say I was suprised also at the time factor. When using rempeg, it takes about 12 to 14 hours and encodes fine. Cce would have taken 10 hours in total if left running.

[SLK001]

You are miss-understanding what exactly CCE is telling you. For a 3 pass VBR encode, CCE will make the first pass and create a .VAF file (which it will use in future passes). Then, during the second pass, CCE will encode the file as if it were only doing a 2-pass run. The size of the file will build up to about the final size at 50%, THEN that file will drop to zero length and everything will start again. What is important during all of the passes (except the last one) is the refining of the .VAF file (which it does on every pass). For the instance that you describe, I imagine that your final file size would have been around 5GB (2GB / .4). If the final file is still too big, you can always make another pass, changing NOTHING BUT THE BITRATES, and only have to do one pass (a 1 pass VBR).

I only do 3-pass VBR (unless I have to do an extra pass to reduce file sizes), so I can't comment on how the file size versus the percentage counter acts for more than that.

Your machine ssounds like it may be a little slow to encode. It would probably be best for you to start the encoding before bed, and just walk away until it is completed.

If you still have your original .VAF file, then you can just pick up where you gave up earlier.

[tonymac]

Thanks for that. My point re encoding time was not related to cpu (900 Athlon, 512 ram) but compairing to rempeg, which is much simpler and seems to do a one pass vbr. I also know the exact size the file will be, and I can access other programs as it is not so cpu intensive. I suppose my point is I am a bit disappointed with cce as a first time user. I have a good source file from dvd rip and am just looking for a fast reencoder which is configurable.
Does the method by which I frameserve make a difference to the overall speed?

[SLK001]

I can get about a 1.0-1.3X encode frameserving with AVISYNTH into CCE with a 1.8GHz P4 (that means that a 2 hour movie will encode in about 6 hours with 3-pass VBR). I have never used VFAPI, so I can't give you any speed comparisons. The filters in your frameserving script can chew up a lot of CPU time, which has to be done BEFORE CCE even gets a look at the file.

It sounds like you need experiment with CCE to get a better feel as to its capability and the settings you should use. Rip out a 1 minute or so segmant out of your DVD, create the appropriate script, and vary the settings in CCE until you are satisfied with the results. This is the way I set CCE up each time I use it. CCE really is a very good encoder, so I'm guessing that you just aren't setting it up correctly.