I thought cinema craft encoder was meant to be fast???

[rcflyers]

I have been using dvd2svcd for a while with tmpeg as the encoder with good results but decided to try it with the cinema craft encoder SP version 2.50.01.00. When it got to the cce part, it did do its job in about 1 hour 30 mins, i thought great!! Then it started another process, which took a further 6 hours 30 mins. Also the first part of the CCE program appeared to crash and lurked around in the background. Then the second part (6 h 30 min part) crashed just before it finished.
My pc is an athlon XP1800+ with 256Mb DDR Ram, 2 x 20GB hdd's and runs windows 98SE.
Anyone know whats going on please?

[rcflyers]

p.s. screenshots here

http://www.lightningeng.fsnet.co.uk/cce.htm

[adam]

As for the speed...what you don't realize is that the encoding speed you are getting is much faster than what you were getting with TMPGenc.

The default number of passes in DVD2SVCD when encoding in CCE is 4, at least it is on mine. This is actually 5 passes because the first pass just creates the vaf file. This is what happened during the first part you mentioned. You didn't say how you had previously used TMPGenc but if you used CQ then you are now literally doing 5 times more processing in CCE, so of course its going to seem like its taking longer. Take however long it took to do it in TMPGenc and multiply it by 5 and you will see that CCE is actually encoding much faster. I recommend not using more than 3 passes in CCE, anymore is pretty much overkill. Next time you encode this same movie you will not have to create the vaf file again so you will just skip that step.

Now as for your crashing...make sure that the add resample audio tab is checked in the frameserver tab. Other than that post the log that DVD2SVCD created. Your screen capture shows absolutely nothing. CCE always shows up as not responding in the system resources tab and the program always lurks around in the background like that. CCE will push your CPU processing up to %100 so if you do not have proper cooling you will crash everytime. I recommend that next time you encode with CCE you run a system monitor to make sure that you aren't just overheating.

[LeeBear]

The reason CCE is taking so long is because you're using multi-pass encoding, from the sounds of it you're using a 5 pass encoding. This basically means the encoder will go through the video 5 times (actually 6) to collect information so it can best distribute the bits most effeciently. That's why you are noticing the long encode times Multi-pass encoding is arguably the best and most effecient method but does take longer then a CBR or CQ_VBR mode. If you want to speed up your encode time don't use mutli-pass use a CBR which will take about an 1.5 hours, or a CQ_VBR which will also take about 1.5 hours to encode, but with CQ_VBR you won't know the exact file size until the encode is done. Personally I use the multi-pass method because I'm a quality freak and like to maximize as much bits as possible, but 5 pass is a bit over kill as the manual states after about 3 passes the gains from the extra passes are minimal.

-LeeBear