CCE Crash/Freeze

[Payasa]

my cce (2.5) keeps freezing/crashing read all the forums about it but nothing helps mpeg2dec.dll/mpegdec2.dll/mpeg2dec3.dll nothing worked.

my system:

cpu: 1.1ghz PIII
mb: MSI VIA 694x Pro
ram: 512 + 256mb
hdd: 60gb Maxtor 7200rpm
video: Geforce MX440 (64mb)
audio: Soundblaster Live Value!

DVD2SVCD 1.1.2 Build 1
CCE 2.5 (cracked) + crc patch

first pass goes succesfully at 1.280 speed
second pass freezes or crashes.

[smeghead]

I'm having a similar problem, though CCE crashes without doing any encoding. I haven't have a sucessful encode with CCE yet. I've spent countless hours looking through the forums and haven't yet found any solutions to my exact problem. I've tried TMPG and its worked but took 60hrs +. I'm glad you are having what seems to be a similar problem. Hopefully we work this out or someone can help us.

[iGorland]

Try to break your project (if this is a Premiere project) into several 10-minute parts, and encode each of them separately. This helped for me.

[atreides93]

I've never had CCE 2.5 or 2.62 or 2.64 or 2.66 crash on my computer, after countless passes etc. I used to have a lot of crashes (before i used CCE) when I had a SB Live card...after I got rid of that stupid card, my system became rock solid stable.

Just a suggestion ;)

[smeghead]

Thanks for your advice iGorland but i found the problem after the 7th week of searching - I have a 500Mhz celeron. I found a thread a couple of days ago saying that "CCE simply won't work in the celeron architecture.... unless its a celeron 500a or above". I know this isn't the same solution for you Payasa but keep trying. This thing about the celeron should be put in the CCE FAQ's, it would've saved me a massive amount of time!

[smeghead]

While we're on the topic, can anyone answer these questions about the logo that appears on the CCE encoded outputs:

Exactly where is it? Does it appear in the black areas or on part of the picture?
and
How big is it?

Thanks.

[Tabriz]

I recently had a freeze using cce 2.66 with mpegdecoder and avisynth 2.5.
At a certain point the coding froze and I had to terminate the program.
Windows task manager advised that CCE was waiting for input.
I did a test run of the same file at a higher bitrate and the coding went through although of course the file was too big !
As a VAF file had been created I was able to open the "advanced" section for bitrate change and tracking through the file I located a point where quantization was excessive. Using the local adjustment for that point I increased the bitrate at that point as far as possible. I then restarted the encode with successful conclusion.

Could it be that too much compression is being used ? In this case the problem was caused by a defective source file and only showed up because I was trying to compress it too much.

Best regards
Tabriz