developed a strange problem

[jamieg]

hi guys about a month ago i developed a wierd problem that happens when i get to the encoding stage of the process.basically what happens is this
i run dif4u all goes sweetly
set up reauthorist hit encode
run either docce or batchcce and cce starts
this is where i now have problems
cce starts doing wierd things
sometimes fails on first scan and says information is differant to previous scan!!!
or it encodes for about half the first scan at normal expected speed and then just accelerates.
or it fails on second scan.
everything was working nicely and i updated some of the software and it went like this.i was hoping that getting the latest versions of everything would sort it out but it hasnt.this is the software i am using
dvd decrypter 3.1.9.0
avisynth 2.5.4.0
docce 1.0.1.5
batchcce 0.9.1.3
reauthorist 1.0.0.0
cce 2.50.1.0
ecl 1.7b
dif4u 1.4.0.0
i thought i might have a dodgy hard drive but i got another to encode onto and the same thing is happening.
any ideas would be really appreciated.

[Kedirekin]

AviSynth errors can cause this behavior.

CCE will speed up if AviSynth experiences an error part way through an encode, because AviSynth is no longer frame serving.

The first and second scan message has the same root cause. The first scan is part video and part error message, but the second scan is all error message.

There is no one single cause for AviSynth failure, so there is no one single solution. However, the most likely cause is system instability. If you're overclocking, you might want to dial it down, and you should test your memory.

[OvERaCiD23]

I ran into the same problem a few weeks back. At that time I was using CCE 2.5, but had never had a problem before. All of a sudden I was getting CRC errors and other errors at random times during encoding. I applied the CRC patch, but that still did not solve the problem. I tried CCE 2.66 and haven't had a single problem since. Sure, I lose .2 off my encoding speed, but who cares?

If you know you have a stable system (I know I did, I could run CPUBurn or MemTest for 24+ hours with no problems at a 400mhz overclock), then don't question that as a problem in CCE. Try using the newer version and see how it works out.

[jamieg]

cheers for the input guys,i'll give a newer version of cce a go,i hope i can sort this out because its doing my head in!!!!by the way whats the crc patch?