View Full Version : im getting a CCE checksum error. please help...
YaoMing11
12th April 2004, 10:37
cce encoding failed: Error: Video check-sum is different from that of previous pass.
Source video data or time code may be different
Please check video tape or the information file
--- information ----
Current: check sum = 0134fc55
previous: check sum = 0134fe8d
Can somebody help me fix this? It seems I might need a patch. I can't seem to find it though.
ux-3
12th April 2004, 11:29
Before you patch up a problem, do this:
Go to bios, note the settings and slow down your machine to specs and standard settings. Your errors will hapen if the system is running too fast.
It will also be a good idea to google for memtest86, and run it. If you get any errors there, they are likely the cause of your problem.
YaoMing11
12th April 2004, 18:55
My pc is at stock speeds. I'll try running the memtest.
Joergen
12th April 2004, 19:18
Didnt cce 2.5 require a "CRC Patch" .. at least I had to use it way back when. CCE 2.66 doesnt need it nor does the 2.67 basic
ux-3
12th April 2004, 19:24
It doesn't _require_ a patch. I've been using it for some time, but when you try to pick up speed, it was the first thing to break. The patch does not remove the problem, only the notification.
If you can, lower ram speeds to slowest settings and try from there.
YaoMing11
12th April 2004, 19:25
I just googled and found the cce 2.50 crc patch. I'll try encoding again later on.
Joergen
12th April 2004, 19:25
If the patch indeed doesnt fix anything, could this be a problem for DVD-RB aswell?
YaoMing11
12th April 2004, 19:49
I checked BIOS and had my memory timings set to aggressive. I lowered them to Optimal as well as applied the CCE Patch. I'll try another encode later tonight and let yall know how it goes.
ux-3
12th April 2004, 20:22
Originally posted by YaoMing11
I checked BIOS and had my memory timings set to aggressive. I lowered them to Optimal as well as applied the CCE Patch. I'll try another encode later tonight and let yall know how it goes.
You just administered morphine to the patient. No use to ask him, if he is still having pain. He isn't cured though.
CCE will now ignore errors. It will still make them. If I were you, I'd reinstall and try with conservative timings first. What did memtest86 say?
Joergen
12th April 2004, 20:25
Actually as I remember, all of my friends had to use the CRC patch for CCE 2.5.. it wasnt related to how stabile the system is, and no memtest could find any problems. It's not to say that a true mem problem wont increase the frequency of the errors.
ux-3
12th April 2004, 20:31
I am runnning and have been running CCE on rounabout 10 machines in the past. Using Athlons, Durons, Pentium3s. I only got CCE to blow the whiste when I OCLed the memory or when I had faulty memory. In fact, to find out if a FSB-setting is still working, I set a 5 pass on the machine. Perhaps there are exceptions, but not hitting one in ten tries does seem to make them rare exceptions.
Joergen
12th April 2004, 20:34
Well is it not a "well known" fact that CCE 2.5 has memory leaks? And maybe you were using an updated version.
Secondly, why does CCE 2.66 and 2.67 never give checksum errors on the same system(s)?
ux-3
12th April 2004, 20:40
Frankly I can't tell you. I never gotten any checksum errors from them. I got them from CCE 2.50, and when I slowed down, they went away.
There is also a rumor, that some of the "trial enhancement software packs" don't do a good job in enhancing, so I don't know if that could have to do with it.
I just recommend to slow the machine before overriding an error message. Only if that fails, I'd tell CCE to shut up!
Joergen
12th April 2004, 20:45
Originally posted by ux-3
that some of the "trial enhancement software packs" don't do a good job in enhancing
Yep that might be it, but with that in mind, considering a software like dvd-rb for the average user.. whenever CCE 2.5 is used, it's most certainly the "enhanced" version. ;)
Methanoid
13th April 2005, 08:28
Well I have 2 machines which ran fine with Rb-080 and with latest 0.82free they are BOTH producing the same error.
Using the Decode DLL provided, CCE 2.50 without CRC patch which I have never had to use in all versions of Rb/CCE. Also no BIOSn tweaks or aggressive timings.
So.... guess I have to apply patch?
jdobbs
13th April 2005, 19:29
I know I had to apply the patch a long time ago -- but I can't remember the circumstances under which the CRC would pop up (it's been a long time)...
ChickenMan
16th April 2005, 01:32
CCE ver 2.50.01.00 Retail standalone version does NOT require the CRC patch, while an earlier "enhanced" trial version (cant remember the actual version) did. The CRC problem shows up more on an AMD based pc than on Intel pc's as well.
jdobbs
16th April 2005, 04:42
It had to be used on mine, and it's the retail version 2.50.01.00. I do have an AMD Processor and always have had. Can't remember the cirucumstances -- I think it had something to do with the VAF file...
Just can't walk away from 2.50 -- it's still a good 30% faster than the newer versions on my AMD.
Methanoid
16th April 2005, 10:12
Well I'm on Intel P4 but I needed it. As soon as I applied it the problem stopped.
Bacardi_AVT
20th April 2005, 10:24
I to have this problem since I went up to DVD-RB 0.83...CCE have worked perfectly on my machine since I installed it two years ago...
BUT...when I cheked the .AVS files that correspond to the faild videosegments I found that they all where just one frame (or 0 frames depending how you interpret the avs file)
Example (all paths edited out):
LoadPlugin("DGDecode.dll")
mpeg2source("V01.D2V")
trim(126759,126759)
ConvertToYUY2(interlaced=true)
AudioDub(BlankClip())
Could this have something to do with the error??
By the way all other segments works perfectly and there is no problem rebuilding the DVD even when I miss these segments...
jdobbs
20th April 2005, 11:52
Nothing changed related to single frames in v0.83. But a change was made in v0.81 in which segments smaller than 60 frames were no longer being encoded using CBR... they were changed to VBR.
Bacardi_AVT
20th April 2005, 12:36
Maybe thats somehow related to this issue since this is the first time I have used the 0.8x versions of the software...I just uppdate my rebuilder version today and The one i used befor was 0.78 (I think)..
richarddd
20th April 2005, 19:35
Me too.
I never had CRC errors before the most recent public builds and now get them frequently. I'm not overclocking or anything like that, my computer passes all memory, etc. tests and I haven't made any major changes.
jdobbs
20th April 2005, 21:19
I think it would be a real stretch to come to the conclusion that a new build of DVD-RB could somehow make CCE have CRC errors.
Bacardi_AVT
20th April 2005, 22:29
I agree that it would be a far strech...but still the evidece points in that direction at the moment...I am going to go back to an older version and test if it will give the same error as the new one using the same source...I will try to post my result tomorrow....
richarddd
20th April 2005, 22:44
I'm running a test as we speak. 0.83 resulted in CCE CRC errors on the first two segments (as well as the last segment). Using 0.80, no CCE errors on the first two segments. The only change I made between encodes was to download and unzip the DVD-RB exe.
By the way, I also ran 0.83 without compression. Worked fine and did not result in any errors.
SpazzHH
20th April 2005, 23:40
@jdobbs
I'm sure this might be a bit of a stretch here, but do you think these CCE errors(Not DVD-RB) could be a bug in there code that is more apt to pop up with AQMS now disabled by default? Is it possible that without it, CCE freaks sometimes on these small segments?
jdobbs
20th April 2005, 23:40
If possible let me know what happens if you use 0.81 and 0.82. If somehow DVD-RB is causing this, I'd like to find our why... I'm never to proud to eat my words... but the likihood of DVD-RB causing this just seems to be slim.
jdobbs
20th April 2005, 23:44
Originally posted by SpazzHH
@jdobbs
I'm sure this might be a bit of a stretch here, but do you think these CCE errors(Not DVD-RB) could be a bug in there code that is more apt to pop up with AQMS now disabled by default? Is it possible that without it, CCE freaks sometimes on these small segments? That's possible. But it has no affect on v2.50 -- didn't someone say they had problems with it also? I can't remember. If it only happens on small segments it also might be tied to the fact that in 0.81 I started using VBR rather than CBR for them.
In my experience to date I've had no problems other than v2.70 on high demand areas... and the problem went away when I went stepped back out of that version.
Is anyone having any issues with the Pro version? It does a demux and reuse for single frames... I may need to do that in the freeware version also just to save myself some headaches.
Bacardi_AVT
21st April 2005, 00:26
Okay..my tests aren't done yet but I only get the problem when CCE is supposed to encode a very small segment (e.g. 1 frame) everything else works fine.
I actually just canceled the segment in one of the encodes I did, since it was the last frame of the movie, and went on just rebuilding it and the finnished product works like it should.
By the way this is what I am using:
DVD-RB 0.83 Free
CCE SP 2.50.01.00
Before this problem I was using:
DVD-RB 0.15 up to 0.79 free
CCE SP 2.50.01.00
jdobbs
21st April 2005, 00:37
Yeah, I'm going to have to do something about VBR and small segments. I changed it to CBR in v0.73 -- but it made the files way to large. Then I thought that it was the min bitrate that was causing it and backed that out in v0.81 -- so it's not like this is a new problem with CCE (unlike the one I mentioned about maximum bitrate sensitivity). Are all of the offending segments a single frame?
richarddd
21st April 2005, 00:56
Originally posted by jdobbs
If possible let me know what happens if you use 0.81 and 0.82. If somehow DVD-RB is causing this, I'd like to find our why... I'm never to proud to eat my words... but the likihood of DVD-RB causing this just seems to be slim. Same problem with 0.82 as with 0.83.
richarddd
21st April 2005, 01:00
Originally posted by jdobbs
Are all of the offending segments a single frame? Seems to be the case.
Bacardi_AVT
21st April 2005, 09:01
I have now tested it on the same video material using different versions of DVD-RB. What I found was the following:
0.83 Free - CRC error
0.81.1 Free - CRC Error
0.80 Free - Works!
I went and checked the REBUILDER.ECL files in the D2VAVS directory and found that they did not match each other, even when the where run on the same source material.
here are the differences:
0.80 Free
vbr_brate_avg=1229
vbr_brate_max=8808
(not there)
vmode=1
opv_brate_max=8088
0.83 Free
vbr_brate_avg=6000
vbr_brate_max=9000
adjust_q_matrix=0
vmode=2
opv_brate_max=9000
could it be the addition of the adjust_q_matrix param that cause this?? I have no clue what that does soo...
SpazzHH
21st April 2005, 11:48
On the surface, these numbers(very little info) just show the difference between CBR and VBR encoding. What is the size in frames of the segment in question? And you're using OPV or Multi-pass?
jdobbs
21st April 2005, 11:51
Just so we keep the record straight... this is very clearly not an error with DVD-RB. It is an error within CCE. The reason you see the error change between versions is because DVD-RB changed from one pass CBR in version 0.80 to two pass VBR in version 0.81 -- a CRC check isn't done in CBR because there is no second pass...
I'll put together a workaround -- but I'll be honest with you, I'm spending way too much time writing workarounds for Cinemacraft's errors. Right now I think their encoder is still the best in the world, and that's why I continue to support it. But QuEnc and HC Encoder both are getting very close in quality and speed -- and neither of them have any of these kinds of problems.
By the way -- posting the VBR numbers is meaningless in v0.80... it's doing a CBR encode if the segment is less than 60 frames.
richarddd
21st April 2005, 12:09
Originally posted by SpazzHH
What is the size in frames of the segment in question? And you're using OPV or Multi-pass? 1) See a few posts back
2) multi-pass
richarddd
21st April 2005, 12:18
Originally posted by jdobbs
Just so we keep the record straight... this is very clearly not an error with DVD-RB. It is an error within CCE. No question it's a CCE error. The only question is what to do to DVD-RB so that CCE doesn't generate an error.
As you suggest, if the problem is single frame segments, maybe that could be tweaked without other ill effects?
jdobbs
21st April 2005, 12:24
You can get around the error by using OPV mode on that segment. But not all CCE encoders (e.g. CCE Basic) have an OPV mode...
Rockas
21st April 2005, 12:59
I'm lost here :confused:
What's the CCE version that is causing those errors?
I've been using CCE 2.50 SP for a long time and never got that!?!?!?
But QuEnc and HC Encoder both are getting very close in quality and speed -- and neither of them have any of these kinds of problems
That (speed) doesn't apply to CCE 2.50 on an Athlon, does it? :D
The last time I tested QuEnc it was about 100% slower - I usually make my backups in about 180 minutes (2 passes CCE 2.50) and QuEnc took me about 6 hours :( (I think it was v0.57).
Methanoid
21st April 2005, 14:00
I'm confused too.. I've been using same 2.50 SP CCE for aeons and only changed DVD-Rb as it changes versions. I only got this error recently.
Granted I solved it (on my P4) with the CRC patch. However it must be the change is CCE versions that has exposed this error. If so, was it a problem on earlier DVD-Rb versions that CCE behaved as it does?
Also, if QuEnc is free and approaching CCE for speed/quality why not just drop CCE and put QuEnc in the package and then we could have a nice all in one single installer that installs the whole caboodle in one go. Its a bind (not a big one) to have to install CCE, Rb, AViSynth etc every time I install my OS!
Bacardi_AVT
21st April 2005, 14:02
Just to test if it is the 1 or less frame thing that causes this problem I edited the .ecl and .avs files in one of the segments that caused the CRC error. I set it to 2 frames instead.
No more error!!
To me as an amature it seems that CCE 2.50 Sp do not like vbr when it comes to only one frame to encode. Would it not be possible to make DVD-RB skip the encoding for 1 frame segments and just use a blank (black) frame instead when rebuilding the DVD?
Carpo
21st April 2005, 14:48
Originally posted by jdobbs
I'll put together a workaround -- but I'll be honest with you, I'm spending way too much time writing workarounds for Cinemacraft's errors. Right now I think their encoder is still the best in the world, and that's why I continue to support it. But QuEnc and HC Encoder both are getting very close in quality and speed -- and neither of them have any of these kinds of problems.
which version of cce would you suggest jdobbs ?
atm i am testing HC and am liking the results - but if i were to use cce which would you suggest ?
also seeing as i wasnt working before when i donated only sent $5 (poor i know - about £3) so i dontated again $10 this time :)
jdobbs
21st April 2005, 15:05
The two most reliable versions I've seen are CCE Basic v2.69 and CCE SP Version 2.50. If you do a lot of interlaced encoding you may want to use CCE SP v2.67 instead of 2.50
Carpo
21st April 2005, 15:13
Originally posted by Carpo
also seeing as i wasnt working before when i donated only sent $5 (poor i know - about £3) so i dontated again $10 this time :)
Just in case u missed it as i edited after you had posted :)
ok i will see if i have enough out of my wages to buy a legit version of cce basic :)
Rockas
21st April 2005, 18:57
@Methanoid
Also, if QuEnc is free and approaching CCE for speed/quality why not just drop CCE and put QuEnc in the package and then we could have a nice all in one single installer that installs the whole caboodle in one go. Its a bind (not a big one) to have to install CCE, Rb, AViSynth etc every time I install my OS!
That package already exists... look at my signature :D
Methanoid
21st April 2005, 21:12
Originally posted by Rockas
@Methanoid
That package already exists... look at my signature :D
U surely dont expect me to READ a sig do you??? ;-)
Thanks.. I'll try it... from first scan of the webpage it seems it doesnt install/include AviSynth in the package and I wonder (before I install) if it puts them all in one neat location on my HD (eg c:\program files\DVD-rb) ??? Anyway will PM some feedback later
Rockas
21st April 2005, 22:03
doesnt install/include AviSynth in the package and I wonder (before I install) if it puts them all in one neat location on my HD (eg c:\program files\DVD-rb) ??? Anyway will PM some feedback later
It doesn't but will ;)
At this point the installer doesn't include Avisynth 'cause it would be too big (5GB)... when Rebuilder v1.0 is out... the installer will include it.
edit: The size of the Installer will be 5Mb not 5Gb... lol... if it was 5Gb you would need Rebuilder to make it fit on a DVD-5 lol... another story like "Who was born first... the chicken or the egg?" :D
ChickenMan
22nd April 2005, 11:06
Originally posted by Rockas
"Who was born first... the chicken or the egg?" :D
I hope this doesnt start a flood of Chicken jokes. :D :D But the answer to that question is simply - BOTH !
richarddd
22nd April 2005, 11:21
Originally posted by ChickenMan
I hope this doesnt start a flood of Chicken jokes. :D :D But the answer to that question is simply - BOTH ! More seriously, the answer is the egg. There were eggs long before there were chickens or even chicken eggs. "Which came first, the chicken or the chicken egg" is a much harder question. :D :D
vBulletin® v3.8.2, Copyright ©2000-2009, Jelsoft Enterprises Ltd.