any one ever seen CCE do this?

[therick]

any one ever seen CCE 2.5 SP do this?



It zooms through making the first pass (.vaf) and then gives me a checksum error when it begins the transcoding...

[SLK001]

Are you talking about the COLORS, which, although strange to me is completely configurable in Windows? Or, are you talking about the speed, which seems very fast, IF there isn't a problem with the video file. However, it looks like it really is about 1X (a 1GB VOB is about 20 minutes or so long) and you have already run for 22 minutes.
Maybe if you could tell us more about what you are refering to.

[Nelson37]

There is a posted fix for the checksum error on Doom9. Also, CCE is well known to crash is there is no audio component to the file, or if asked to code audio on an AMD Athlon.

[adam]

The checksum error is extremely common. It just happens on some hardware setups, I believe it is caused because some temp file is not cleared fast enough in between passes. As stated before, just get the patch. The checksum checks are pretty pointless.

If this is a full length encode and the speed is just too good to be true than it is. Are you frameserving through avisynth? This has happened to me before when the source had some garbage in it. Avisynth basically could not read past that point in the file so it simply fed an error msg to the encoder to encode. So when the encoding finally finished my mpg was just a black screen with an error code in it. Check the resulting mpg, either after its done encoding or just stop it now if you haven't already. I seriously doubt the mpg will be of any use.

[therick]

Thanks all -
I ran the checksum patch from doom9's site and still no dice. I am still shooting up the 3-4 time real time level.

I am frameserving through AVISynth, adam...running tests now to try and see what the problem is

[therick]

alright, I have never had a problem with CCE until this point...I have the encoder running at normal speed but it took a little fiddling. Adam, you were right about the error message from AVISynth, big red letters right on the top of the .mpg.

I have fixed it, but it is kind of ramshakel and I am sure that there is a better way. The fix is - add a trim. If I add a trim, it runs perfectly, no trim, no go.

script file:

LoadPlugin("mpeg2dec.dll")
MPEG2Source("bod.d2v")

trim(0,139909)
#Crop(0,6,720,474)
#CropBottom(10)
BilinearResize(352,360)
Sharpen(0.8 )
AddBorders(0,60,0,60)
ResampleAudio(44100)

if I comment out the trim, we get a 4x realtime encode with AVISynth's red letters at the top...is there something else wrong with my script causing this...I have used this script dozens of times with no problem. Any ideas?