PDA

View Full Version : cinema craft sp stop encoding with an error message


squard64
26th January 2002, 12:46
hi!
it's the first time i'm trying to encode a full length movie. 'cinema craft encoder sp' stops encoding with an error message which says that the checksum does not match the one from a previous pass.

what can i do to make it work? is it my fault?
thanks!

squard64

markrb
26th January 2002, 16:04
Read the Newbie Faq and the Q + A there is a checksum patch. The link is in there.


Mark

squard64
26th January 2002, 17:41
thanks! i hope it's working now.
squard64

squard64
27th January 2002, 00:46
the patch says it will disable ALL CRC-checking from cinema craft sp-encoder. will that cause in artefacts when a CRC-checksum is not correct? (i'm sorry, but i don't know anything about CRCs...)

Slick
27th January 2002, 01:30
depends on what you call artefacts.
if you see an error or freezing using CCE after the patch is applied it normally means you have a memory problem, or Page file fault.
however you must be running DVD2svcd ver 1.06 build 1 or later to verify this. ( I think):) someone will correct me if I'm wrong.

squard64
27th January 2002, 02:57
i mean MPEG artefacts. i hope it is the right word. ...A BETTER DISCRIPTION OF MY PROBLEM IS... will i see the checksum error later in the movie?

pacohaas
27th January 2002, 07:12
I've had this error on some movies, and when I use crash recovery and start the video encoding over, sometimes it will give me the error again, but sometimes it makes it all the way through, on the same exact movie(hence crash recovery). So i'm guessing it could just be a problem with other things going on while encoding is happening and some math doesn't get done exactly the same in CCE for whatever reason and the second time it comes out slightly different than the first(the 2 values always seem to be similar) I don't know what i'm trying to say, i guess i'm just saying it happens to me too, but using crash recovery a few times, will usually get you past it.

it's kind of annoying, yes, but good to know that eventually CCE agrees with itself.

squard64
27th January 2002, 10:27
hey! please read all the postings... there is a patch available to disable CRC checking. my question was: the patch will make CCE not giving you any error messages. but the checksum error might still be there. will i see those error in the encoded movie later in form of artefacts or whatever you call it...'skrewed up pictures' for example...

Slick
27th January 2002, 10:39
O.K. I'm with you now.
no the artefacts you refer to will not show in the movie, because there arnt any!
the crc patcher simply corrects the spurious crcs by not reporting them.
like I said in my earlier post,

"if you see an error or freezing using CCE after the patch is applied it normally means you have a memory problem, or Page file fault."

squard64
27th January 2002, 13:04
that's all i wanted to know. my computer does not freeze at all. i'm quite happy. thanks again to all of you.

Val3r10
5th January 2003, 11:41
Q27: I get this strange Checksum error from CCE when it runs...
A: Please download this (http://www.bath.ac.uk/~susajb/Cinema_Craft_Encoder_2_50_SP_CRC_Patch.zip) patch 15KB (Thank's ALI! for hosting)


Unfortunately, that link is down and I receive Multipass CRC errors
very often.
And all my system is set-up for max compatibility.

Does anyone have another working link ?

Thanks

ux-3
5th January 2003, 13:03
Cure the disease, don't hide the symptoms. If someone shouts fire, cutting his tongue doesn't really solve the issue...

Check this, it is really usefull...
http://www.memtest86.com

scottchicken
17th January 2003, 07:55
I used to receive the CCE checksum error, with an AMD XP 1700, using Windows 98SE, and 3 x 256mb DDR RAM.

Opps! Windows 98SE can't handle more than 512mb for certain things. Took out one module so I'm down to 512mb, no more errors.

To confirm this, I used the Prime95 torture test which gave errors for the full 768mb RAM. With 512mb, it runs indefinately with no errors.

SO, in conclusion, I agree with the previous post. Do some investigating, find the problem!