CCE error , wierd and unexpected happening . . .

[ankurs]

well i was authoring a custom dvdr from a tv capture . . . ran the script as usual and left it , to my amazment this is what i got after some time . . .

http://i31.tinypic.com/10wikad.jpg

well the script which i am using is supposed to take way longer than this , i expect a 35 ~ hour encode for 4 passes , what i would like to ask is why did this happen and why did i get this error ? :eek: because if it was true then that would've been phenomenol lol , i enqueued the rip again and this is what i get now . . .

http://i32.tinypic.com/28gvwpt.jpg

i want to ask that will it happen again , because i dont want to lose precious time and also not be bothered to do it all again lol :p

a memory leak might be the culprit ?

pc specs : 2.0 core2duo with 2 GB ram and windows 2003 std . . .

P.S : Also around 326 GB is free out of the 500 GB so there surely is enough space , nothing related to space on the hdd it seems ...

[manono]

Hi-

I don't know if it will happen again. Did you try and open the script in VDub(Mod) to see if it gave out with an error? What's the script?

Also, if the encode is going to be that slow, you might consider making a lossless AVI first (I use Lagarith) in VDub(Mod), and then using that in an AVISource AviSynth script for CCE. That way the really slow script is run only once. The CCE passes will go much more quickly.

[ankurs]

Hi-

I don't know if it will happen again. Did you try and open the script in VDub(Mod) to see if it gave out with an error? What's the script?

Also, if the encode is going to be that slow, you might consider making a lossless AVI first (I use Lagarith) in VDub(Mod), and then using that in an AVISource AviSynth script for CCE. That way the really slow script is run only once. The CCE passes will go much more quickly.

nope script works all fine in vdub as well . . . and not at home atm , will post the script when i get home .

and i am using lagarith as the source lol :p its just what i'm doing will take time hehe :)

probably seems a memory leak , its going fine now , 11 more hours for the encode to complete :D