Log in

View Full Version : error 9 during rebuild - one solution


krbo
4th April 2005, 08:57
As I had several times error 9 during rebuild phase here
are some findigs from my case.

It allways occurs on a last segment of a VTS.

Looking in AVS in question shows it instructs CCE to
produce mpeg of only ONE frame (Trim(183765,183765))

Every CCE version I tested produces junk file if asked
to encode only one frame.

As TMPGEnc was handy nearby - imported AVS made perfect
one frame mpeg and rebuild was OK.

(Never tried QuEnc or ReJig )

maybe this will help someone else

dannyv
5th April 2005, 19:04
Originally posted by krbo


Looking in AVS in question shows it instructs CCE to
produce mpeg of only ONE frame (Trim(183765,183765))


I also had the same problem with blank frames causing error 9's. This was caused by the encoder trying to encode the single frame then choking on the frame and corrupting it. Since then jbobbs has rb coping over the single frame and not encoding it.

You are obviously not using the latest version of RB. So I suggest you download the latest version.

Originally posted by krbo


Every CCE version I tested produces junk file if asked
to encode only one frame.


Every version from 2.6x and up

jptheripper
5th April 2005, 19:11
new rebuilder (.81pr) does not reencode single frames, it simply copies them.

dannyv
5th April 2005, 20:22
Originally posted by jptheripper
new rebuilder (.81pr) does not reencode single frames, it simply copies them.

You are correct it was fixed and only available in the pro version 081

- Updated STILLFRAME code so frames are no longer reencoded but instead are kept intact and are reintegrated into the output stream.

@krbo

You would need to donate to the project to get the PRO version.

krbo
6th April 2005, 07:16
Originally posted by dannyv

@krbo

You would need to donate to the project to get the PRO version.


willing to do that for a long time but jdobbs is stucked with PayPal
and many of us can't use that xenophobic service - see my other post
here

Stealth915
7th April 2005, 05:25
krbo,

what settings did you use to rebuild the one frame? I loaded the avs file into TMPGENC and it encoded, but i get an "Error 0006: DVD-RB has found an inconsistency in source data between the PREPARE and REBUILD phases. Aborting."

jdobbs
7th April 2005, 11:40
v0.81 should have also fixed this problem in the freeware version. While it doesn't extract the frame as PRO does, it has changed the processing. The cause of this issue is the bitrate imposed sometimes makes it impossible for CCE to come up with a solution. In v0.81, the bitrate for a single frame is raised, but VBR is still used. When it gets released, let me know if you still have this problem and I'll come up with something else.

krbo
7th April 2005, 13:49
Originally posted by Stealth915
krbo,

what settings did you use to rebuild the one frame? I loaded the avs file into TMPGENC and it encoded, but i get an "Error 0006: DVD-RB has found an inconsistency in source data between the PREPARE and REBUILD phases. Aborting."

It was 5.3Mbit CBR ,HighQ, 16:9, GOP 1/4/2/1/15 closed , video ES
(avs is rebuilder's one)

(on a single frame :)) )

and yes, I remember that exact error in similar case earlier while
experimenting with exported 1 frame from other videos

krbo
7th April 2005, 14:13
Originally posted by jdobbs
In v0.81, the bitrate for a single frame is raised, but VBR is still used. When it gets released, let me know if you still have this problem and I'll come up with something else.

here is what 0.77 proposed for one frame:

frame_rate_idx=3
cbr_brate=6000
vbr_brate_avg=9000
vbr_brate_min=0
vbr_brate_max=9000

jdobbs
7th April 2005, 17:38
I already fixed this (even in the freeware version) -- you'll have to wait until v0.81 Freeware is released.

Stealth915
7th April 2005, 18:44
jdobbs

any ETA on when freeware .81 will be released? i have quite a few movies with that runtime error waiting to be rebuilt.

jdobbs
7th April 2005, 19:11
Try just adding this line to the AVS after the trim() statement

BlankClip(last,length=1)

Not sure if it will fix it, but it might.

If you're using CCE SP you can definitely fix it by changing the segment containing the single frame to OPV.

Even better -- get the Pro version. ;)

jdobbs
7th April 2005, 19:15
Just a point to remember. If you're getting runtime error 9's (or 0006) frequently there is probably something else wrong. I haven't seen one of these since way back...

Joe_smish
7th April 2005, 23:06
Originally posted by Stealth915
jdobbs

any ETA on when freeware .81 will be released? i have quite a few movies with that runtime error waiting to be rebuilt.

I had the same problem related to this thread. Is there an ETA jdobbs? I dont have paypal or a credit card so I need to wait for the freeware version. Also, I'm really not skilled with this kind of technical stuff. I do have TMPGEnc and was wondering if someone could more clearly and in more detail explain the process of going about solving this problem if you dont have the version .81. I have freeware version .80. I'm trying to back up the movie "Fight Club". I used shrink and did it already but it was highly compressed (60%). I heard that DVD-RB works better for this level compression so I wanted to compare. I'm using CEE Trial Version 2.67. I ran into many errors along the way but was able to solve them all. Now I'm at the rebuild stage with this runtime error 9. I didnt change any of the settings of anything. I used Vobblanker to blank the extras, if that makes a difference. Hope this is enough information for you guys. Thanks alot.

jdobbs
8th April 2005, 17:07
Originally posted by jdobbs
I already fixed this (even in the freeware version) -- you'll have to wait until v0.81 Freeware is released. Well, at least I thought so. There has been some apparent changes to CCE SP 2.70.2.0. I just ran a job that works fine (exact same ECL) on v2.70.1.5, but on v2.70.2.0 I got the infamous "MPVA VBF ovf frame#" error... it just never stops. I'll have to work out a way to get around it.

Joe_smish
8th April 2005, 17:59
Do you think that this could happen, for me at least, because I used VOBblanker? I seem to run into the one frame error every time it reached a segment that I had blanked using Vobblanker.

jdobbs
8th April 2005, 18:19
Read this post (http://forum.doom9.org/showthread.php?s=&threadid=92741) -- it may help you.