The Runtime Error 9 thread - reply with yours

[casonbang]

I figured it would be easier if we consolidate the few remaining bugs each into their own thread, especially since the forum doesn't allow you to search for "runtime error 9". Reply with your results so we can help jdobbs squash this bug.

DVD-RB: 0.44
Encoder: CCE 2.67 trial w/ EclCCE 1.8b
DVD: Step Into Liquid (disc 1) (region 1)
DVD comments: 44 VTS, lots of squirrely-looking authoring and commands. extras are 4:3 and look interlaced
Decrypt method: DVD Decrypter 3.2.1.0 file mode to hdd
DVD-RB Options: 1/2 D1 & 1/2 space

I get error 9 on rebuilding the first VTS (VTS10). That VTS is only one 5 min PGC, 2 cells, no stills. I tried copying without 1/2 D1 & 1/2 space and it worked flawlessly! So it seems that something about the 1/2 D1 space option was causing streams that messed with RB's head.

I'm running 0.45 on the same disc with half&half to see if anything is fixed. I'll update tomorrow when it's finished.

[samuraijack]

Okay, lets do this thing...

DVD-RB: 0.45
Encoder: CCE 2.50 ( AMD Proc ) ECCle 1.8
DVD: Kill Bill Vol 1(region 1)
DVD comments: Tested other process methods with Shrink and DVD2one. Seem to work fine
Decrypt method: DVD Decrypter 3.2.1.0 Select all files to HD
DVD-RB Options: 1/2 D1 & 1/2 space
Decomb.dll from AVISynth 2.5 plugins dir, mpeg2dec3dg.dll from specified file in Doom9 setup FAQ, left in same directory as DVD-RB. Not checked to add.

Anyone else?

[BeechNut]

I concur with casonbang's finding. I Was having runtime 9 errors with 1/2 D1 & 1/2 space option check on two different movies. Once I disabled that option both movies worked flawlessly. 1/2 D1 & 1/2 space is a nice option to have, but for now i gots to leave it unchecked.

DVD-RB: .45
Encoder: CCE 2.66 (AMD) ECCle 1.8
DVD's: Haunted Mansion R1 & Finding Nemo R1
Comments: The Nut just dropped you some acorns JDobbs great program
DVD Method: Decrypter 3.2.1.0 In file mode to HD
DVD-RB Options: 1/2 D1 & 1/2 space checked = Runtime 9
1/2 D1 & 1/2 space unchecked = Its Orville
Redenbacher's Time
Decomb.dll and Mpeg2dec3dg.dll in AVISynth 2.5 plugins dir.

[puddy]

Disc: Dikie Roberts 16x9 NTSC (7.27 GBs Originally)
Removed: English 2-CH AC3 and French AC3 using DVD-RB

DVD-RB failed upon rebuild at segment 8 VOBID:6 CELLID:1 with the Run-time error '9': Subscript out of range error.

My Stats:

HARDWARE
P4 2.8 GHz w/HT, 800 MHz Bus, 200 MHz FSB, 512 MBs DDR-SDRAM PC3200 (No Overclock)

SOFTWARE
DVD Decrypter v3.2.1.0: Rip in File Mode
DVD-RB v.45
- Dynamically Assign Cell Bitrates - ENABLED
- Half-D1 and Half Space for Extra - ENABLED
- ConvertToYUY2() - ENABLED
- AudioDub(BlankClip()) - ENABLED
- Add MPEG2DEC3DG to AVS File - ENABLED
- Run Encoder(s) Minimized - ENABLED
- CCE SP (v2.66+) Mode
- VBR_Bias=25
- Quality_prec=16
- VBR_Passes=6

eclcce v1.81
CCE SP v2.67.00.23
- Remove Cancel Button - ENABLED
- Priority set to IDLE

AviSynth v2.54 (all other versions uninstalled & registry cleaned)
MPEG2Dec3dg.dll v1.0.1.0 (put in AviSynth plugins dir)

puddy

[alanuk]

DVD Rebuilder v0.44 Beta
CCE Basic Ver.2.67.01.19
eclCCE: No

Bug: At the end of the "rebuilding segment" phase I'm getting an error 9 BUT only when I am in batch mode: that is have 2 or 3 films lined up. As a newbie I can't give any technical specifics except that the Run-time error '9': Subscript out of range error appears only in batch processing.

[puddy]

Stats for this run:
Disc: Italian Job NTSC (7.64 GBs originally)
Removed: English 2ch AC3 and French 6ch AC3 using DVD-RB
Phase I, PREPARATION started at 09:36:44
- Note: "Half-D1/Half Space for Extras" mode is enabled.
- VTS_02: 189,319 sectors.
-- Scanning and writing .D2V file
-- Processed 12,140 frames.
-- Building .AVS and .ECL files
- VTS_03: 371,554 sectors.
-- Scanning and writing .D2V file
-- Processed 31,248 frames.
-- Building .AVS and .ECL files
- VTS_04: 2,630,468 sectors.
-- Scanning and writing .D2V file
-- Processed 159,007 frames.
-- Building .AVS and .ECL files
- VTS_05: 691,869 sectors.
-- Scanning and writing .D2V file
-- Processed 67,644 frames.
-- Building .AVS and .ECL files
- VTS_06: 66,502 sectors.
-- Scanning and writing .D2V file
-- Processed 4,150 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 55.9%
- Overall Bitrate : 2,739Kbs
HALF-D1 Extras increased Main-Movie bitrate by 21.8%
- HIGH/LOW/AVERAGE Cell Bitrates: 4,824/131/2,739 Kbs
Phase I, PREPARATION completed in 11 minutes.
DVD-RB failed upon rebuild at segment 2 VOBID:3 CELLID:1 with the "Run-time error '9': Subscript out of range" error.

My setup for this run:

HARDWARE
P4 2.8 GHz w/HT, 800 MHz Bus, 200 MHz FSB, 512 MBs DDR-SDRAM PC3200
No overclocking

SOFTWARE
DVD Decrypter v3.2.1.0: Rip in File Mode
DVD-RB v.45
- Dynamically Assign Cell Bitrates - ENABLED
- Half-D1 and Half Space for Extra - ENABLED
- ConvertToYUY2() - ENABLED
- AudioDub(BlankClip()) - ENABLED
- Add MPEG2DEC3DG to AVS File - ENABLED
- Run Encoder(s) Minimized - ENABLED
- CCE SP (v2.66+) Mode
- VBR_Bias=25
- Quality_prec=16
- VBR_Passes=6

eclcce v1.81
CCE SP v2.67.00.23
- Remove Cancel Button - ENABLED
- Priority set to IDLE

AviSynth v2.54 (all other versions uninstalled & registry cleaned)
MPEG2Dec3dg.dll v1.0.1.0 (put in AviSynth plugins dir)

Source and destination were on different physical drives on machine.

puddy

[robw]

Originally posted by alanuk
DVD Rebuilder v0.44 Beta
CCE Basic Ver.2.67.01.19
eclCCE: No

Bug: At the end of the "rebuilding segment" phase I'm getting an error 9 BUT only when I am in batch mode: that is have 2 or 3 films lined up. As a newbie I can't give any technical specifics except that the Run-time error '9': Subscript out of range error appears only in batch processing.

Hi
I got the same error 9 in rebuild when I did it in either batch or one-click. I also tried to rebuild the failed avs in 3-click (rebuild phase only) and got the error.

[casonbang]

I tried the same dvd with 0.45 and got the same error.

DVD-RB: 0.45
Encoder: CCE 2.67 trial w/ EclCCE 1.8b
DVD: Step Into Liquid (disc 1) (region 1)
DVD comments: 44 VTS, lots of squirrely-looking authoring and commands. extras are 4:3 and look interlaced
Decrypt method: DVD Decrypter 3.2.1.0 file mode to hdd
DVD-RB Options: 1/2 D1 & 1/2 space

I get error 9 on rebuilding the first VTS (VTS10). That VTS is only one 5 min PGC, 2 cells, no stills.

[El Leon]

I got the error rebuilding Stuck on You

DVD-RB: 0.45
Encoder: CCE 2.67 - EclCCE 1.8b
DVD: Stuck on You
Decrypt method: DVD Decrypter 3.2.2.0 file mode to hdd
DVD-RB Options: 1/2 D1 & 1/2 space

[SAPSTAR]

Originally posted by casonbang
....

I get error 9 on rebuilding the first VTS (VTS10). That VTS is only one 5 min PGC, 2 cells, no stills. I tried copying without 1/2 D1 & 1/2 space and it worked flawlessly! So it seems that something about the 1/2 D1 space option was causing streams that messed with RB's head.

I'm running 0.45 on the same disc with half&half to see if anything is fixed. I'll update tomorrow when it's finished. ...


Well...I just had the error on Saving Private Ryan without using the 1/2 D1 & 1/2 space option...It may increase the risk but it's not so safe...

DVD-RB: 0.45
Encoder: CCE 2.67 - EclCCE 1.8b
DVD: Saving Private Ryan
Decrypt method: DVD Decrypter 3.2.2.0 file mode to hdd
DVD-RB Options: Only Dynamically assign bitrate

[Bluesilo]

DVD-RB: 0.45
Encoder: CCE 2.67 SP trial / ECL 1.81
DVD: American Beauty (Disc 1) (NTSC)
DVD comments: (VTS 1) 16:9 ; (VTS 2) 4:3 ; (VTS 3-5) 16:9
Decrypt method: DVD Decrypter 3.2.2.0 File Mode To HD
DVD-RB Options: 2 pass and 1 Audio Stream per Title Set

[jdobbs]

I'm starting to think this Half-D1 option may be more trouble than its worth.

[Joergen]

Originally posted by jdobbs
I'm starting to think this Half-D1 option may be more trouble than its worth.
I'll try it on something now to see if I get errors. :scared:
edit: doh, the disc I was trying it on is episodic and has an extra (VTS_5) that is bigger than the actual stuff :D Maybe I'll try basic half-d1 and RB-Opt for the extras bitrate.

[puddy]

Originally posted by jdobbs
I'm starting to think this Half-D1 option may be more trouble than its worth. Please don't give up. These reports are just so that you can have a base of knowledge to work from. These aren't complaints! :)

This is an option that makes DVD-RB very unique. I know I'd be disappointed if you were to remove it.

puddy

[jdobbs]

Originally posted by puddy
Please don't give up. These reports are just so that you can have a base of knowledge to work from. These aren't complaints! :)

This is an option that makes DVD-RB very unique. I know I'd be disappointed if you were to remove it.

puddy My real worry is that as I'm adding on user requests there are (as is always the case) follow-on work that comes with it. Then I spend a lot of time responding to those and some of the primary capabilities (like multi-angle and interleaving) keep slipping to the right on the schedule.

I'm also concerned about DVD-RB picking up a bad reputation for continuing errors if I keep "adding" rather than "stabilizing". It's more of a "time management" issue for me -- I like feedback so I'm not really reading these as complaints.

[elmokiddo]

DVD-RB: 0.45
Encoder: CCE 2.67 trial w/ EclCCE 1.8b

Runtime Error 9 on Rebuild phase of Runaway Jury and Kill Bill (both R1)

Kill Bill specifically at Rebulding segment 2 VOBID:3 CELLID:1

both 1/2 space Extras

Elmo

[robw]

Originally posted by jdobbs
I'm also concerned about DVD-RB picking up a bad reputation for continuing errors if I keep "adding" rather than "stabilizing". It's more of a "time management" issue for me -- I like feedback so I'm not really reading these as complaints.

jdobbs
I fully agree. In my opinion the number one priority should be to make the program stable and work with a wide range of DVDs including multi-angle. You have been more than generous, even over generous, in putting in user wish list items. That list is undoubtedly long and will likely get even longer. It sure is more interesting to add fabulous new features but without a stable platform is that really a wise choice?

Best regards and just want to say for the umteenth time how much I enjoy your product. Best regards and I truly hope you're having fun as you develop this ... because the rest of us are!

[Joergen]

Originally posted by jdobbs
Then I spend a lot of time responding to those and some of the primary capabilities (like multi-angle and interleaving) keep slipping to the right on the schedule.


I for one would rather have you disable the half-space option and continue with the root stuff like multi-angle.

With tools like RB-Opt and ECL Optimizer people can still reduce the bitrate of the extras if they so please.

[DDogg]

I'm bummed as I thought the 1/2-1/2 would be a quick and temporary solution to a fairly significant problem, thus actually creating extra time to do the multi-angle, etc.. Jdobbs, if it can't be fixed easily, I tend to agree you ought to pull the 1/2-1/2 as it seems it is causing the majority of the '9's on rebuild.

[Joergen]

Could CCE be bombing out with multipass (3 or more) and half-d1 like described somehwere, then the rebuild dies also?

[puddy]

Originally posted by Joergen
I for one would rather have you disable the half-space option and continue with the root stuff like multi-angle.

With tools like RB-Opt and ECL Optimizer people can still reduce the bitrate of the extras if they so please. Personally I think it would create confusion to pull it out now. Then you are going to have people who "really want it" still using old versions of DVD-RB. My opinion would be to continue work on it, but hold off on other things like issues with encoders/transcoders other than CCE.

If you want a transcoder:

Easy, reliable, slightly less quality: DVD Shrink
Dumb interface, unpredictable, but best quality: Instant Copy

To me trying to compete with these well established transcoding utilities is a waste of time. I'm not suggesting you (jdobbs) are wasting your time or am I trying to insult you in any way. I'm just saying from my standpoint, I don't need another transcoder.

CCE is well established as the best encoder available. Do you think anybody would be paying attention to DVD-RB if it wasn't for the fact that it is a one click re-encoding product using CCE?

The fact that DVD-RB is based around CCE encoding is the crux of the interest in this program. Maybe I'm wrong, and obviously I don't speak for others. That is just my opinion.

To the point: drop or push back work on QuEnc and ReJig before Half D1 and other options tied into CCE.

Please... pretty please, don't take anything I've said personally. I fully understand you are basically doing this for free. But if people don't tell you how they honestly feel, then what is the point? :)

Thanks again!
puddy

[Joergen]

I did a title so I used half-d1 in dvd-rb .45 3 pass CCE 2.66 and changed the bitrate to around half with ECL Optimizer and it compiled without error.

[jdobbs]

@puddy,

I'm not going to take it out... I'd never put out a version that has less capability than the previous. I do think, though, that I may have to slow down on the requests until I get a fully working version out.

[mpennel]

I'm getting the Runtime Error 9 on BLACK HAWK DOWN R1 on rebuild.

SOFTWARE
DVD Decrypter v3.2.2.0: Rip in ISO mode mounted with Daemon Tools
DVD-RB v.45
- Dynamically Assign Cell Bitrates - ENABLED
- Half-D1 and Half Space for Extras - ENABLED
- ConvertToYUY2() - ENABLED
- AudioDub(BlankClip()) - ENABLED
- Add MPEG2DEC3DG to AVS File - ENABLED
- Run Encoder(s) Minimized - DISABLED
- CCE SP (v2.50) Mode
- VBR_Bias=10
- Quality_prec=24
- VBR_Passes=3

I'm going to redo it tonight with "Half-D1 and Half Space for Extras" disabled, and see what happens this time. I'll report back then.

Mark

edit: I just finished Black Hawk Down with Half-D1 and Half Space for Extras disabled, and it worked just fine!

[DDogg]

I tried "ItalianJob" yesterday using rejig. It failed on rebuild with a '9', as well as with 1/2-1/2 when using CCE.

I am wondering if finding out why it is failing with rejig might show the way to the root cause?

Using CCE without the 1/2-1/2 the rebuild finishes ok, but there seems to be other problems like audio sync on the extras.

[insanescape]

Got mine with Matrix Revolutions, but as I eventually found (thanks for not letting me search for error 9, forum.. bleh), it has a 0byte VOB (straight off the disc) and after deleting it I tried again, so we shall see.

[jdobbs]

Originally posted by DDogg
I tried "ItalianJob" yesterday using rejig. It failed on rebuild with a '9', as well as with 1/2-1/2 when using CCE.

I am wondering if finding out why it is failing with rejig might show the way to the root cause?

Using CCE without the 1/2-1/2 the rebuild finishes ok, but there seems to be other problems like audio sync on the extras. We'll see -- I just went and bought the Italian Job just so I can see it bomb... and I'm not even sure I like Marky Mark! Hmmm... maybe this isn't a bug -- its a feature!

[jdobbs]

Originally posted by insanescape
Got mine with Matrix Revolutions, but as I eventually found (thanks for not letting me search for error 9, forum.. bleh), it has a 0byte VOB (straight off the disc) and after deleting it I tried again, so we shall see. That shouldn't make it bomb... except possibly if you try to burn with Nero.

[DDogg]

... and I'm not even sure I like Marky Mark! Hmmm... maybe this isn't a bug -- its a feature! Ah, yes, you mean the secret mediocre movie filter feature. :)

Good to hear you got the DVD, its a pretty decent flick. Oh course who watches this stuff anymore. Way to much testing to do. Hopefully you can put a stake in the heart of this '9' critter.

[jdobbs]

@all,

I just found and fixed this error. It will be posted with v0.46 -- it wasn't related to the bitrate... it was caused by a group of 4 or more reference frames (I or P) that somehow fit in a single output sector. That would be very unusual in typical DVD resolutions -- but more likely with Half-D1. It definitely wasn't CCE's fault.

[insanescape]

Might be fixed eh? That's wonderful news. If it works you've got some shiny, er, some um.. texty paypal coming your way.

So it wasn't the 0 byte file, and I didn't do half-d1 for extras, and the bitrate definitely was high enough, so I like your explanation as to what's causing it. :)

[robw]

Originally posted by jdobbs
@all,

I just found and fixed this error. It will be posted with v0.46 -- it wasn't related to the bitrate... it was caused by a group of 4 or more reference frames (I or P) that somehow fit in a single output sector. That would be very unusual in typical DVD resolutions -- but more likely with Half-D1. It definitely wasn't CCE's fault.

That's great!!!

[jdobbs]

So it wasn't the 0 byte file, and I didn't do half-d1 for extras, and the bitrate definitely was high enough, so I like your explanation as to what's causing it. No. As with a lot of these errors it was my stupidity... or more accurately the result of writing code in the middle of the night with your eyes only half open... I'd set a sanity check to ensure I didn't go past the end of an array I was using to record the last sector of reference frames (to populate a NAVPACK) -- unfortunately the sanity check was checking for a value that was really end+1 :rolleyes:

[Cidici]

DVD-Rebuilder: 0.45
Avisynth: 2.5x
CCE: 2.50
DVD: Code Swordfish (ripped months ago)

runtime 9 on "prepare" button pression

[jdobbs]

Originally posted by Cidici
DVD-Rebuilder: 0.45
Avisynth: 2.5x
CCE: 2.50
DVD: Code Swordfish (ripped months ago)

runtime 9 on "prepare" button pression That's a different error... but I have a fix for what is probably the cause of that one as well (v0.46). I've also found the cause of the #0006 error... but it appears to actually be flaw(s) in the original MPEG-2 stream(s) that has illegal temporal values -- I'm looking at a way to "get around" it. Yes I know it sounds weird (if you are one of the guys who understands MPEG)... what it looks like is some bad editing in which 1 or more B frames are being cut from the end of a GOP and the temporal offset of the preceding P or I frame then falls incorrectly after the end of the GOP!

[Cidici]

Originally posted by jdobbs
That's a different error... but I have a fix for what is probably the cause of that one as well (v0.46). I've also found the cause of the #0006 error... but it appears to actually a flaw in the original MPEG-2 stream(s) that has illegal temporal values -- I'm looking at a way to "get around" it.

it says something like "index out of bounds" (the error msg is in italian so im not sure about the english version) after writing
"----------------"

i suppose there's something wrong in my swordfish rip, cause im tryin another dvd and now the program is scanning and writing .d2v

[quantum]

Originally posted by jdobbs
That's a different error... but I have a fix for what is probably the cause of that one as well (v0.46). I've also found the cause of the Did you get a chance to include BOV in (v0.46) as well? :scared: :)

[Momotte]

When do you plan to make 0.46 available so that we can test it and see if the error went away? Up to now, I tried 3 different DVD and get the "subscript out of range" error in the rebuild phase.

continue your good work and try to prevent night coding!

[rkorkie]

Just from a software developer's perspective, I'm glad jdobbs was able to realize that he was incrementing an array past the size of its dimension, which will always result in that error of "subscript out of range". I suppose we could have suggested you to look for that code instead of pointing the finger at it possibly being the encoder's fault. Just my 2 cents...

[insanescape]

I'm sure he'd appreciate any positive remarks, especially because sometimes you might be going nuts over one particular issue and might be overlooking something simple.

[jdobbs]

Originally posted by Momotte
When do you plan to make 0.46 available so that we can test it and see if the error went away? Up to now, I tried 3 different DVD and get the "subscript out of range" error in the rebuild phase.

continue your good work and try to prevent night coding! Got it where? If you are getting errors often something else is wrong and you probably need to reinstall from scratch and setup... these errors are the exception not the rule -- I, for example, had to go out an buy another disc (The Italian Job) to make it happen!!!

[jdobbs]

Originally posted by insanescape
I'm sure he'd appreciate any positive remarks, especially because sometimes you might be going nuts over one particular issue and might be overlooking something simple. You must be a programmer...

[Joergen]

Yes its definetly the exception. Out of about 20 discs so far I've had only one with an error in compiling. :cool:

[Momotte]

Sorry, I hope you are not unhappy about what I wrote earlier I was just reporting what happened to me for the last three DVD I was trying to DVD-RB. These are: U2 Live from slane castle, Sting...All this time and David Gilmour. I had to revert to the Big3 because I had this error in the rebuild phase. My setup is correct since everything else is working with the big3 unless there is something I don't understand? By the way, it work flawlessly for 5 others I did last week...

Is there a way to get more infos or some sort of debug log with more informations so that we can do a better report when there is a problem? I would be glad to help...

[jdobbs]

I'm not unhappy. Sorry you read it that way. I'm just trying to tell you that it has to be somewhere in the range of 1000 to 1 that you would get 3 in a row that failed... That isn't impossible, but it also isn't probable.

Try 0.46 when I post it a little later. You may be the guy who broke the odds... ;)

[insanescape]

Not much of a straight programmer anymore, but I do have some work and hobbies that tend to get overanalyzed for the simplest of solutions. :)

I'm being quite a bad test case myself. I didn't get an error 9 with one dvd, of course, I didn't need to back it up (just testing a large space movie). The one I wanted to back up I got the 9, the other was a multiangle movie. :)

If 46 does the trick I'll be plenty content

[jdobbs]

Originally posted by insanescape
Not much of a straight programmer anymore, but I do have some work and hobbies that tend to get overanalyzed for the simplest of solutions. :)

I'm being quite a bad test case myself. I didn't get an error 9 with one dvd, of course, I didn't need to back it up (just testing a large space movie). The one I wanted to back up I got the 9, the other was a multiangle movie. :)

If 46 does the trick I'll be plenty content Well with any luck I might get multiangle into version 0.47 and probably no later than 0.48.

[quantum]

Originally posted by jdobbs
Well with any luck I might get multiangle into version 0.47 and probably no later than 0.48. Oooh, by my deductive reasoning, I must assume you have BOV ready on 0.46 since you didn't mention it for 0.47 or 0.48 :)

[jdobbs]

Originally posted by quantum
Oooh, by my deductive reasoning, I must assume you have BOV ready on 0.46 since you didn't mention it for 0.47 or 0.48 :) Yep.

[insanescape]

No error 9s with Matrix Revos now, awesome work. Nero still cries about an unreferenced VOB, but considering the files straight from the DVD say the same thing if you try to burn them, I'd say you did perfect work on eliminating that problem. $ your way my good man.

[SvensK]

Getting Run-time error '9': Subscript out of range,
when trying to 5pass CCE encode my Die Hard R2 (PAL).

Using DVDRB 0.47

Edit: It happens as soon as I press Prepare.

Second edit: Weird, this was fixed by using drive M: as source which has NTFS instead of drive E: which has FAT32.
You might wanna look into that.

[biggy7]

Originally posted by SvensK
Getting Run-time error '9': Subscript out of range,

Second edit: Weird, this was fixed by using drive M: as source which has NTFS instead of drive E: which has FAT32.
You might wanna look into that.

cheers mate!

was also getting runtime 9 when i was pressing the prepare button, and my source was indeed on a Fat32 hard drive, so i put the source on a ntfs hard drive and it started to prepare,

using 0.49 at the moment as it seems to work well on my pc, the rest just start to encode files very quickly, CCE just opens and closes very fast untill it says encoding complete.

[jcclow]

Titantic (it's for the wife)

I used DVD Remake Pro 2.2.1 to get rid of the junk I didn't want (FBI warnings).

Created .d2v and scripts fine. Encoded fine (225 min. 7,420mb).

Used idct=5 on all my scripts (thanks wmansir!)

Get runtime error 9 while trying to rebuild...
-Updating NAVPACKS for VOBID:3
-Rebuilding segment 3 VOBID:4 CELLID:1

3.0 P4 HT, 1gb Dual Channel DDR400, 3 HD's (total 180gb), ATI AIW 9600XT, Plex DVD-R, Lite-On CD-R, Plex SCSI CD-ROM, Adaptec 2940 SCSI Adapter, 600w Coolermaster PS, XP Pro

Used DVD-RB 0.55b.

jdobbs, this software is amazing! I will donate to your cause!

incidentally, all of my drives are NTFS.

[JadedMan]

I got runtime error 9 on 2 DVDs so far: Star Wars I & AI
Ripped with DVD Decrypter 3.2.3.0
Used DVD Shrink 3.2 to rip main movie
- I cannot use original rip because of multiple angles
Using CCE 2.67.00.09, EclCCE 1.81 & DVDRB 0.56
Each DVD originally had RCE Protection before being ripped.
I get error on rebuild when 99% complete

Using Athlon XP 3200, 1GB Dual Channel RAM, 2 - 120GB Hard Drives (NTFS).

I have successfully backed up other DVDs.

Just adding to the database :)

Otherwise, this software is wonderful - thank you jdobbs :)

I'll keep posting if I continue to have issues.

[kenkong]

I get it everytime I try and use rebuilder. Right when I start the rebuild phase.

[Rasta]

I've gotten Run-time Error 9 on two different backups. I rip the titles I want using DVD-Shrink w/no compression. I get this problem from The Sopranos Second Season Disc 1 and "28 Days Later." I am using DVDRB 0.56. This always happens in the rebuild phase. This happens over and over. If anyone could help I would really appreciate it.
*Rasta

[Rasta]

Bump. This is not just for me, I know there are some other people with this problem but have yet to find a solution. From what I have seen, the common denominator seems to be that people have get Runtime Error 9 with DVDRB are using DVD Shrink but I saw post somewhere else where some use DVD Decryptor so I don't know. I'm specifically using DVD Shrink 3.2 and for "28 Days Later;" I rip just the main title and the 5.1 audio stream with no compression. DVDRB seems to be the best for backup solution for very large movies or episodic discs and I have had a couple successful (Queer As Folk Season One Discs 1 and 2, also Vanilla Sky, and Helter Skelter have worked) but I'd like to figure out how to resolve the Error 9, maybe this would help others too. I should have mentioned that this only happens when it is rebuilding and doing the NAV Packs, specifically:

"-Rebuilding segment 34 VOBID:16 CELLID:1"

Well again, any help would be greatly appreciated

[Van the man]

getting the runtime 9 error when clicking on "prepare"
my source is on a ntfs drive.

Im using cce 2.50 with eclcce.
Dvd-RB 0.56

Im not using the half D1 and half space thing.

Do someone know whats wrong?

I had the dvd on my computer and then I made a img of it all,but when it was done I found out it had one .srm file in it.
Do ya'll think it has something to do with the error?
the dvd also was missing some .vob files but I replaced them with "dummy" files. Maybe it doesnt work then?

thanks for all the replys on this one

[jdobbs]

If you are going to rip... use a ripper -- DVD Decrypter. It's free and is the best ripper on the planet -- I don't understand why anyone want to use DVD Shrink as a ripper? It's like using a screwdriver to drive nails.

If you are using Shrink to strip the movie before running it through DVD-RB you are only asking for trouble. If you absolutely have to modify it (which I really don't recommend) -- use DVDRemake.

[Rasta]

Thanks Jdobbs. I'll try Decryptor, I use DVD Shrink to rip because it allows you to preview each title and I don't want menus or anything like extras, just the movie with the audio and english sub picture, and its easy to figure out what's what with Shrink. Anyway, DVDRB is great, I suppose Shrink is doing something to the IFO's or something, I don't know.
*Rasta

[DrChair]

I also have a dvd now, that gives a runtime 9 error, during the prepare stage, just after scanning the last vts.
After this, rebuilder.inf only contains some info about the sizes of the first 4 vtses, but nothing about the last vts.

This error happens every time with 0.56 and 0.55b. I tried it on a mounted ISO and on the files decrypted with dvddecrypter.

However DVD-RB 0.50b doesn't give the error, so it seems you might have reintroduced a bug...

Anyways as a workaround, I'll do the preparing for this disc with 0.50b and the encoding+rebuilding with 0.56

Greetz DrChair

[Rasta]

err ....

Ok, I just used DVD Decryptor to rip the main movie of The Truth about Charlie. I didn't do anything weird, just selected "Main movie + ifo" and ... Bam, Runtime Error 9 while doing the Rebuild, this happened at 99 or 100% .. I'm using DVDRB .56. Is there any way to know why this happens or what is going on? This is what it says:

"- Rebuilding segment 21 VOBID: 2 CELLID: 1"

That is the line it failed at: the previous line was:

"Updating NAVPACKS for VOBID_01"


Admittedly, I know very little about this but I checked the source directory I was using and it is like this and the only files I have are:

VTS_01_0.IFO
VTS_01_1.VOB - VTS_01_5.VOB (so I have 5 VOBs)

Is the rebuilding portion of DVDRB blowing up because it expects "VOBID: 2" to be there and I only have one VTS titleset? Or do I just have no clue and should wait til someone who knows what their doing offers some help? =)

Well again, any help would be really appreciated. But if that is the case, how do I prevent this, again all my runtime error 9's are in the Rebuild portion and usually are either finished or nearly finished. If this is the case does that mean DVDRB is using the IFO information from the original source, which maybe mentions other VOBIDs? ... well I don't know, hopefully fixing my issue will help other people too.
*Rasta

[Rasta]

Correction to last post, when using DVD Decryptor I did not select "Main Movie + IFOs," I selected "Main Movie" which gave me only one IFO file. I don't know why this would be necessary or if there is a workaround to get away from including those files or what ...
*Rasta

[robot1]

DVD-RB is a tool for a full backup, not for a movie only backup.
You can't rip main movie only. You have to rip all files (in file mode) or, even better, make an iso (mode->iso->read) and mount it with daemon-tools or another similar tool.

:readguid:

[Rasta]

I see, I was starting to see that, though with all due respect the After Dawn and the Doom9 guides do not explicitly say that, in fact the Doom9 guide refers to the DVD Decryptor guide which says to rip the main movie. Nevertheless, ok, when I use IfoEdit on the VIDEO_TS folders of the problematic DVD's (whether I choose the "ripped output" or the DVDRB output) and I open up an .ifo and click "get sectors" it does say something about correcting a problem in VMGI_MAT, what that means I don't know but the backups that work fine don't report this, so I'm suspecting the problem lies in the ifo or something ...

Anyway, ok if DVDRB is intended only to backup the full dvd, what does one do to backup the main movie, or just episodes in the case of an episodic DVD, and encode those with CCE to make them fit while retaining quality? It would seem that DVDRB would be great for this, and I guess mysteriously it does work fine on my Queer As Folk box set so far. To me it seems a lot of quality is lost in attempting to retain all those extras even if you "steal space," etc. Does anyone else only want to retain the main movie or in the case of an Episodic discs, the main episodes and make a simple menu for it? I guess I'm stubborn, I want to use DVDRB because it works so well at preserving quality, and it seems there should be some way to do this ... Oh well, if someone knows a workaround or a different way (not DVD2ONE or DVD Shrink) then please let me know, preferably using DVDRB.
*Rasta

[Faust2]

I succeeded with DVDShrink in Reauthor mode. In this case Shrink generates a new DVD-Structure, containing only the main movie, and this "DVD" you can use as source for RB. BUT keep the structure simple. No menus, just one plain titleset.
It works like this (with Shrink 3.1): Rip the source with Decrypter as described in the varios guides, use ISO-mode, and mount the image with daemontools; OR use file mode BUT be sure you get all files. Then start shrink, select "reauthor" (not backup), browse to your source, select the title(set) you're interested in, "add" it to the left part of the window by right-clicking it, mark it and then check "no compression" at "compression settings". Then hit "Backup!". After you're done, use shrink's output directory as source for RB.
I never had any problems, but this procedure isn't "officially" supported by DVD-RB, so if you get errors, it's propably not RB's fault.

[Rasta]

Faust, ya I do that, I use the latest version of Shrink but that's what I have done. Its worked on a couple and doesn't work on others but it seems to rarely work now. I don't use Decryptor then Shrink though, it seems redundant, but I will try it though I suspect the same problems will arise. There's got to be a way that works to accomplish what I'm trying to do, its really not that extravagant. I know, I could conceivably rip the DVD, like with Shrink, and use DVD Lab to re-author and make completely new IFO files, with no menu or anything, and then use DVDRB on that. I think, hypothetically, that should work with no issue but that is a LOT of what I think is needless work and very non-standard, if it wouldn't enter more problems into the mix.
*Rasta


- I must add that when I use VOBRator to analyze the VIDEO_TS folders, the last VOB on the DVDRB input always results in "failed to render graph" when you attempt to preview the VOBID that DVDRB fails on but if you preview the VOBID right before that one it is perfectly fine and it is actually the end of the credits. This happens on all the ones that fail, and if I preview the last VOBID of the DVDRB output it outputs fine, which contains the end of the movie (credits) just as the input. I played both DVD Decryptor output and the DVDRB output in WinDVD and it all plays fine except somehow the Chapters are screwed up in the DVDRB Output (there are 5 less chapters but the only difference appears to be where and how many chapter markers, the movie is still the same length), maybe this has to do with difference in frame positions. So I don't know what all this means, it just makes me think that this Error 9 can't be a huge problem and there must be some workaround or something. Btw, the DVDRB output *looked* great as always.

[Faust2]

like Jdobbs said:


If you are going to rip... use a ripper -- DVD Decrypter. It's free and is the best ripper on the planet -- I don't understand why anyone want to use DVD Shrink as a ripper? It's like using a screwdriver to drive nails.


maybe shrink 3.1 is better in keeping the standards? as far as i know the new version isn't so long out of beta yet. I used the above "movie-only-method" many times and didn't have a single problem. I can imagine, however, if you use shrink to strip just one extra and two warnings out, the possibility of srcewing up the structure is higher.

[Rasta]

Well since it seems like I've been documenting my problem I may as well post the last bit I've discovered ...

I used used DVD Decryptor to rip the entire DVD (The Truth About Charlie) and then used Doom9's guide for IfoEdit to remove the main movie only. I must admit I got a bit lucky in choosing the VOBID as I don't really have that technique down. After using the IfoEdit guide, I used DVD Rebuilder and it worked flawlessly. The chapters remained intact correctly, as well.

If nothing else it looks like I was right in that there was a problem in the the IFO file(s). Although this worked, if I had not gotten lucky choosing the VOBID this would have just been a wasted 5 hours. I still think there must be a workaround or something simpler to do to make this work, and I wouldn't even want to attempt for backing up any of my episodic DVDs. For some reason, I have this feeling that all the main movie VOBs for the movies I've done successfully with my DVD Shrink method had only one VOBID. It seems like Error 9 pops up when it attempts to use a VOBID other than 1, but this is just a neophyte's conjecture. Hopefully, this post is not all for naught.
*Rasta

[Trahald]

Originally posted by Rasta
...Anyway, ok if DVDRB is intended only to backup the full dvd, what does one do to backup the main movie, or just episodes in the case of an episodic DVD, and encode those with CCE to make them fit while retaining quality? It would seem that DVDRB would be great for this, and I guess mysteriously it does work fine on my Queer As Folk box set so far. To me it seems a lot of quality is lost in attempting to retain all those extras even if you "steal space," etc. Does anyone else only want to retain the main movie or in the case of an Episodic discs, the main episodes and make a simple menu for it? I guess I'm stubborn, I want to use DVDRB because it works so well at preserving quality, and it seems there should be some way to do this ... Oh well, if someone knows a workaround or a different way (not DVD2ONE or DVD Shrink) then please let me know, preferably using DVDRB.
*Rasta

There is nothing wrong with wanting to be able to only back up part of your dvd for qualities sake. Problem is trying to make a tool that the author intended for all video to be kept using it. I wish my car had a button to fly.. id get places alot faster. but i cant blame ford that thats not the case because they think cars are best on the ground. And i (note the 'I') cant demand/expect that they add it (suggest politely maybe) ;)

[Rasta]

Oh definitely. I'm not trying to demand anything, after all I haven't paid for it but I think its still great software. The problem is I think this can already be done with DVDRB but something weird is happening or whatver and just trying to get to bottom of it and maybe help other people as well. =)
*Rasta

[SVCDPhreek]

DVD-RB : .57a
AviSynth: 2.54
dvddecrypter: 2.3.0.1

i get this error during the prepare proccess the dvd i am trying to backup is Red Green :Suffed and Mounted 3 and 6 both give me the same error , when i look in the work directory the d2v files goto vts 10 ,but the dvd itself has 14 vts,
what i am trying to say is every time i have had dvd-rb try to backup any dvd with 11 or more vts's it gives me the Runtime error 9 subscript out of range.

am i doing something wrond? or is this a dvd-rb problem?

so far i read this whole thread and all who posted problems had older versions of dvd-rb , and the error happened in the rebuild proccess. mine happens in the prepare

Thanks to all who Help others
SvcdPhreek(dvdPhreekiest)

[jdobbs]

11 VTSs or 11 VOBs within a VTS? You should be able to have up to 99 VTSs (DVD standard) -- but can only have 10 VOBs (0 - 9) within each VTS.

[2COOL]

Originally posted by jdobbs
11 VTSs or 11 VOBs within a VTS? You should be able to have up to 99 VTSs (DVD standard) -- but can only have 10 VOBs (0 - 9) within each VTS. Definitely out of specs and here's what I wrote on this matter. About filenames (http://forum.doom9.org/showthread.php?threadid=71071&highlight=filename+8.3)

[jdobbs]

I just found and corrected one instance that could cause an Error '9' -- if anyone reports getting a '9' at the very start of an encode, and it doesn't seem consistent across DVDs; this one was likely your problem. It will be posted as a part of v0.58.

[JadedMan]

The error 9 problems that Rasta has documented in this thread are verbatim the problems I have been experiencing. I also have been ripping the main movie only using DVDShrink 3.2.0.15 with no compression in the interests of preserving as much quality as possible. The error comes up during the rebuild phase at 99% complete. The latest movie I tried is Master & Commander. When I play back the resulting output, I also experience shifted chapter points, the same as Rasta has already documented.

Thank you Rasta for documenting this problem so well and for sharing a workaround, albeit as you point out, it's a rather involved process. I agree that the issue is potentially simple and could be an problem with the DVDShrink output. Let's hope that this problem will be fixed :) I still think that DVDRB is the tool of choice to make DVD backups :)

[jptheripper]

Runtime 9 error since upgrading to v0.66
Winxp
File image loaded in FantomCD to virtual drive

Title - Taking lives Unrated R1 NTSC (no preprocessing)
dgdecode.dll
ccesp 2.67 5 pass
half d1 steal space on vob that errored

many successfull backups before

runtime error on rebuild


Title - Hidalgo R1 NTSC (remake preprocessing
dgdecode.dll
ccesp 2.67 5 pass
half d1 steal space on vob that errored



hope the issue is not back

[Methanoid]

Just got my first error of any type using DVDRb

0.64 beta

On VTS_49 on a backup of B Movies (Brain from Planet Arous / Teenagers / Tom Corbett). Tried several times with and without Half D1 Extras. Only ever sets up the FLG and AVS files, no encoding done.

Hope this is fixed in the next public one. Can supply screen dump if needed

[jptheripper]

3rd runtime 9 error, no preprocessing..

Dawn of the Dead r1 ntsc..

one of my settings must have gotten screwed up.

It is the last cell of the main movie vts that is crashing, 1 frame, yet cce 2.67 generates a 2560KB file. I remember this happening before, switching back to 2.50 helped i think.

I will try that again

grrr...

any ideas would be very appreciated

[jdobbs]

Where is is happening (PREPARE, ENCODE, REBUILD)? Any details would be helpful.

[jptheripper]

it is only happening in the rebuild. It is crashing on the single frame items. I had this problem a long time ago, switched to 2.5 on my other machine and it went away.

I am redoing the project with the same settings except switching to 2.5 and will let you know if there is any problems

[jptheripper]

the problem seems to be the generation on the single frame cells. Seems as if 2.67 makes a 2.6mb m2v file out of these, and on the rebuild something goes wrong. I am baffled as to how a single frame can generate a file that big regardless of bitrate, i actually think its a problem in cce but unfortunately i have no idea how to explain it.

[jdobbs]

Does the AVS file show only one frame?

[jptheripper]

yes

well it was a trim (276000,276000) for example (made up numbers)

im reprocessing atm with 2.67 to get exact avs that generate the m2v

[jdobbs]

Thanks.

[jptheripper]

#------------------
# AVS File Created by DVD Rebuilder
# VOBID:02, CELLID:01
#------------------
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\DGDecode.dll")
mpeg2source("L:\DOD_OLD\D2VAVS\V01.D2V")
trim(157136,157136)
ConvertToYUY2(interlaced=true)
AudioDub(BlankClip())



is the one that produce the error..

it just hit me that maybe avisynth 2.5 and dgdecode.dll are not playing well together? Im using the june 07, 20004 dgdecode.dll, and wondering if i upgraded versions and decoders at the same time? hope i havent wasted your time

[jptheripper]

Identical avs generated for cce 2.50, however, rebuilt with 0 errors. I fear this is a problem with a difference between how 2.5 and 2.67 deal with single frames.

I will check the ecl's now.

[jptheripper]

From ecl files.. first is working ecl for cce 2.50

[item]
title=V01002100002001
aud_out=0
vaf_file=L:\DAWN OF THE DEAD\D2VAVS\V01002100002001.vaf
aud_file=L:\DAWN OF THE DEAD\D2VAVS\V01002100002001.mpa
file_focused=0
packet_size=2048
width=720
height=480
frame_rate_idx=1
cbr_brate=6000
vbr_brate_avg=393
vbr_brate_min=0
vbr_brate_max=6688
seq_endcode=1
dvd=0
half_width=0
half_height=0
lum_level=0
aspect_ratio=3
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
all_closed_gop=0
fix_gop_length=0
samples_per_sec=44100
stereo=2
brate_idx=7
crc=1
progressive=0
alternate_scan=1
intra_dc_prec=2
encode_mode=0
vmode=1
fast_mode=0
quality_prec=37
timecode=0x0000000
vid_file0=L:\DAWN OF THE DEAD\D2VAVS\V01002100002001.m2v
vid_file1=L:\DAWN OF THE DEAD\D2VAVS\V01002100002001.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=6688
vbr_bias=10
vbr_pass=4
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=L:\DAWN OF THE DEAD\D2VAVS\V01002100002001.avs
frame_first=0
frame_last=1
encode_first=0
encode_last=1

[jptheripper]

And this is the one from cce 2.67 that causes the runtime 9 subscript error on rebuild

[item]
title=V01002100002001
aud_out=0
vaf_file=L:\DOD_OLD\D2VAVS\V01002100002001.vaf
aud_file=L:\DOD_OLD\D2VAVS\V01002100002001.mpa
file_focused=0
packet_size=2048
width=720
height=480
frame_rate_idx=1
cbr_brate=6000
vbr_brate_avg=393
vbr_brate_min=0
vbr_brate_max=6688
seq_endcode=1
dvd=0
half_width=0
half_height=0
lum_level=0
aspect_ratio=3
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
all_closed_gop=0
fix_gop_length=0
samples_per_sec=44100
stereo=2
brate_idx=7
crc=1
progressive=0
alternate_scan=1
intra_dc_prec=2
aud_mode=0
tc_ref_frm=0
drop_frame=0
fix_vbv_delay=0
letter_box=0
pulldown_detect=0
offset_line=0
create_new_vaf=1
credits_tweak=0
credits_start=0x00000
credits_brate=1000
h_filter=0
h_filter_idx=8
dither=0
dither_max=8
qmat_idx=0
quality_prec=24
timecode=0x0000000
video_type=1
vid_file0=L:\DOD_OLD\D2VAVS\V01002100002001.m2v
vid_file1=L:\DOD_OLD\D2VAVS\V01002100002001.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=6688
vbr_bias=10
vbr_pass=4
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=L:\DOD_OLD\D2VAVS\V01002100002001.avs
frame_first=0
frame_last=1
encode_first=0
encode_last=1

[Methanoid]

Originally posted by jdobbs
Where is is happening (PREPARE, ENCODE, REBUILD)? Any details would be helpful.

I was using One Click but tried separate to identify WHERE it goes wrong and its on the PREPARE stage. It gets to VTS_49 and then barfs with Runtime 9. The display shows:

VTS_49: 544,559 sectors.
--Scanning and writing .D2V file
--Processed 44,496 frames
--Building .AVS and .ECL files
-Reduction level for DVD-5: 60.0%
-Overall Bitrate: 2842Kbps
-Space for Video: 3,753,374KB

Are you sure its not overflowing on 49 VTS's!! :sly:

Its got me stumped.. I LOVE this s/w and use it regularly now.

[Toranaga]

I am getting a CCE crash at the last encode and then "Subscript out of range" when rebuilding. Movie is LOTR Return of the King EE. I have ripped to movie only and am using 0.68. Anything to be done?

[jkcheng122]

seems ppl are still runnin into this error, it is happening on every disc i've tried on now. even reinstalling didnt work.

[jkcheng122]

Originally posted by JadedMan
The error 9 problems that Rasta has documented in this thread are verbatim the problems I have been experiencing. I also have been ripping the main movie only using DVDShrink 3.2.0.15 with no compression in the interests of preserving as much quality as possible. The error comes up during the rebuild phase at 99% complete. The latest movie I tried is Master & Commander. When I play back the resulting output, I also experience shifted chapter points, the same as Rasta has already documented.

Thank you Rasta for documenting this problem so well and for sharing a workaround, albeit as you point out, it's a rather involved process. I agree that the issue is potentially simple and could be an problem with the DVDShrink output. Let's hope that this problem will be fixed :) I still think that DVDRB is the tool of choice to make DVD backups :)

shouldnt be a problem with dvdshrink, b/c i used clonedvd2 and recode2 to preprocess and the same error came up. i then tried no preprocessing and still the same problem occurs. by same problem i meant what u described (rebuild fail at 99% and chapter shifts). i'm using cce 2.67, that half and half thing is disabled. i'm gonna have to give 2.66 a try, if that dont work then try 2.50.

this error thing could very well be an issue to cce 2.67 being incompatible with dvd-rb since jptheripper had the same disc work with no error when he switched to 2.50.

[jptheripper]

yeah

likely you vts 49 is a low bitrate vbr (sub 400) but odd that it is crashing in the prepare phase.

[jdobbs]

Let's nail this down... because this thread seems to be all over the place...


1. When does this error occur?
2. Is it always related to single frames?
3. Does using 2.50 always fix it?
4. Is there an NTSC movie that ALWAYS causes it?

Please don't answer with "always" or "every disc" -- as that only convinces me you have some other problem and I won't respond. I can't come to your house to debug this.

Note: Contrary to conspiracy theories -- DVD-RB was not seen meandering around the grassy knoll just before the Kennedy assassination. DVD-RB was questioned and judged as "coincidentally present" by the Warren Commission.

[jkcheng122]

Originally posted by jdobbs
Let's nail this down... because this thread seems to be all over the place...


1. When does this error occur?
2. Is it always related to single frames?
3. Does using 2.50 always fix it?
4. Is there an NTSC movie that ALWAYS causes it?



1. most of the time at the end of the rebuild phase, sometimes at the very beginning right after copying unaltered files.

2. i dunno how to answer this one.

3. have not tried 2.50, will post here with results. i will likely attempt this overnight.

4. i have 3 movies that all came up with the same error repeatedly

[Trahald]

Originally posted by jkcheng122
4. i have 3 movies that all came up with the same error repeatedly I think he was looking for specific DVD titles.. and what region they are (hopefully R1 ntsc so he can try to duplicate).

[Toranaga]

LoL I just ran three different discs through without problems. I will try to find a specific NTSC film that gives me problems (the movies I had problems with was PAL).

[jkcheng122]

switching to cce 2.66 worked, so the issue is definitely (well, let's say 99% to stay away from that "always" word) between cce 2.67 and dvd-rb.

[Toranaga]

Originally posted by jkcheng122
switching to cce 2.66 worked, so the issue is definitely (well, let's say 99% to stay away from that "always" word) between cce 2.67 and dvd-rb.
Really! This is great if we can get this cleared up. I will keep running 2.67 until I run into an error and then try and older version of CCE.

[jdobbs]

Ok... Here's what I've found out about the Error 9 as it happens during rebuild. It seems that occasionally something can happen in CCE during the encoding phase that will make one of the output .M2V files be corrupt and incomplete. That fact then, during rebuild, creates either the Error #0004 (Buffer Overrun) or Runtime Error 9 depending upon where it happens.

A workaround follows: You have to reencode the one .M2V that is causing the problem. Look at the LOG, get the name of the file, then copy that files section of description out of the REBUILDER.ECL file into ITEM.ECL, load it into CCE and execute, and then run the rebuild phase again.

The problem is that CCE doesn't seem to give DVD-RB any indication that anything is amiss during the encode phase. I'm going to look at the code and see what I can do.

[Toranaga]

Originally posted by jdobbs
Ok... Here's what I've found out about the Error 9 as it happens during rebuild. It seems that occasionally something can happen in CCE during the encoding phase that will make one of the output .M2V files be corrupt and incomplete. That fact then, during rebuild, creates either the Error #0004 (Buffer Overrun) or Runtime Error 9 depending upon where it happens.

A workaround follows: You have to reencode the one .M2V that is causing the problem. Look at the LOG, get the name of the file, then copy that files section of description out of the REBUILDER.ECL file into ITEM.ECL, load it into CCE and execute, and then run the rebuild phase again.

The problem is that CCE doesn't seem to give DVD-RB any indication that anything is amiss during the encode phase. I'm going to look at the code and see what I can do.

The problem I am talking about is that CCE crashes during encode, and you cannot re-encode the file. If you just close the error message from the crash then RB continues with the next encode, but then you cannot rebuild the files because of the missing encode that crashed.

[NobbyNobbs]

@Toranaga

Have you read the post you quoted at all ?

[b1ackmai1er]

@jdobbs

Love your new tag line.

"Contrary to conspiracy theories -- DVD-RB was not seen meandering around the grassy knoll just before the Kennedy assassination. DVD-RB was questioned and judged as "coincidentally present" by the Warren Commission."

Regards b1m1

[jkcheng122]

i do wanna add that it was cce 2.67.0.9 that i'm having trouble with. since there are other builds of 2.67 i thought i give u the specific one i have.

[wrxblaze]

Hi I tried uninstalling and reinstalling everything to do with rebuilder. I had done quite a few backups before the runtime error 9 began happening, which made me very frustrated. So I always seemed to switch between 2.5 and 2.66 and one or the other might possibly work or it might not. But than none of them worked, I was doing Die Hard 3 (die with a vengeance) region 1 and was using 2.5 and it failed near the beginning of the rebuild stage (where it usually happens).

So I tried 2.66 and started the whole process over again. But this time I remembered that when I first installed rebuilder a long time ago I used Mpeg2dec3dg.dll and not dgdecode so I switched them since than I've done 3 movies and no problems well I did the Matrix and I got some buffer overflow or something but thats another matter. So whether this means anything I don't or maybe I'm lucking with 2.66 as the flav encoder of the month I don't know, but I'd be glad to help I think rebuilder is a great program, thanks.

[dannyv]

I also get run time error 9 as well as buffer overflow 3's and 4's and always in the rebuild stage and never at the same point in the rebuild process. I don't get these problems when I use cce 2.50se only with 2.67. My tag line has all my machine info. I've gotten this on Star Trek the original series season 2 and on Law and order 2004 season. I have not gotten a successful build yet and went back to 2.50. I am going to fool around with it a little more now that the holidays are over and I have some spare time. Any helpful hints would be welcome.

<<EDIT>> also wanted to mention that I do no pre-processing.

Intresting statement in the above post (I first installed rebuilder a long time ago I used Mpeg2dec3dg.dll ).

I'll try it with mpeg2dec3dg and report back.

[dannyv]

Well I'm at my whits end. I tried it with mpeg2dec3dg and it gave me an error 9 on the last m2v file during the rebuild process just like it does with dgdecode. I tried selecting the file section of the last m2v file to rebuild it as jdobbs suggested in an earler post and when I move the item.ecl file into cce I get a message that it can't read the ecl file. At this point I have ran out of things to try. If anyone can help I would sure appreciate it.

@jdobbs

I'm trying to re-encode the last m2v file.
Can you give me an example of what a single segment item.ecl file should look like maybe I just didn't cut and paste the correct information into it.

Here is the end of the log file

- Rebuilding segment 14 VOBID: 4 CELLID: 3
- Rebuilding segment 15 VOBID: 4 CELLID: 4
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 16 VOBID: 5 CELLID: 1

[dannyv]

Originally posted by jptheripper
the problem seems to be the generation on the single frame cells. Seems as if 2.67 makes a 2.6mb m2v file out of these, and on the rebuild something goes wrong. I am baffled as to how a single frame can generate a file that big regardless of bitrate, i actually think its a problem in cce but unfortunately i have no idea how to explain it.

I just confirmed the same thing the last m2v file is a single fraim and the file is 2.6 megs. This is on law and order special victoms unit 2004. This happens on any disk in the series.

[dannyv]

Originally posted by jdobbs
Ok... Here's what I've found out about the Error 9 as it happens during rebuild. It seems that occasionally something can happen in CCE during the encoding phase that will make one of the output .M2V files be corrupt and incomplete. That fact then, during rebuild, creates either the Error #0004 (Buffer Overrun) or Runtime Error 9 depending upon where it happens.


@jdobbs

Could the error 9's at the end of the rebuild as it starts the navpack be due to the single frame VOBID's as described by jdtheripper in a previous post?

Lets recap this error 9 problem

1. Seems to only happen at the end of the rebuild.
2. Seems to only happen with cce 2.67, cce 2.50 seems to work fine.
3. Seems to happen at a vobid that has a still frame (makes m2v file 2.6 megs) I've proved this on 3 seperate disks from the set.

4. Seems to happen just as it starts the navpack for the still frame.
5. If you play the processed dvd the nav pointers are all screwed up.

Jdobbs when you look into this and if you make any changes to the code. I will be happy to test it just PM me. I have several disks saved to my hard drive that I can test on. As of now I've tested this on 068 - 070 and I get the same results.


Hope my observations help.

[Sir Didymus]

Hi dannyv, :)

1. No point IMHO to test the older decoder release: DGdecode is supported from release 064, and I never heard about anybody reporting problems with it, just some guys making confusion with renaming and other crazy manipulations, trying to support some funny hypotheses that may just lead to troubles on their own...

2. As pointed out by Jdobbs, it seems, [even if I am still curious: maybe I missed something; has it been clearily and explicitely reported ? I mean is it a fact ?], that in some circumstances (what ? when ?) CCE may produce crappy m2v files (truncated ? corrupted ?)...

3. For manually reencoding a specific segment, you just need to use a text editor and extract a segment like this from the rebuilder.ecl file:


[item]
title=V01000000001001
aud_out=0
vaf_file=C:\TEMP\D2VAVS\V01000000001001.vaf
aud_file=C:\TEMP\D2VAVS\V01000000001001.mpa
file_focused=0
packet_size=2048
width=720
height=576
frame_rate_idx=3

...
skip
...

vid_file0=C:\TEMP\D2VAVS\V01000000001001.m2v
vid_file1=C:\TEMP\D2VAVS\V01000000001001.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=8552
vbr_bias=25
vbr_pass=2
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=C:\TEMP\D2VAVS\V01000000001001.avs
frame_first=0
frame_last=5275
encode_first=0
encode_last=5275


4. You should feed this segment to CCE, through ECLCCE, so manually start ECLCCE, and drag&drop the segment into the CCE window...

Regards,
SD

Edit: forgot to mention... You should paste the segment into the item.ecl, or in a new temp.ecl file, in order to drag&drop this file into the CCE window, started using ECLCCE... :rolleyes: OK. Impossible to provide a more obscure and complicated description of such a simple thing... Hope it is helpful anyway...

[dannyv]

Originally posted by Sir Didymus
Hi dannyv, :)

1. No point IMHO to test the older decoder release: DGdecode is supported from release 064, and I never heard about anybody reporting problems with it, just some guys making confusion with renaming and other crazy manipulations, trying to support some funny hypotheses that may just lead to troubles on their own...



I agree as stated in my previous post that the error 9 I get is produced with eather Mpeg2dec3dg.dll or dgdecode.dll so I have since ruled out the decoder as a problem.


[QUOTE]Originally posted by Sir Didymus
2. As pointed out by Jdobbs, it seems, [even if I am still curious: maybe I missed something; has it been clearily and explicitely reported ? I mean is it a fact ?], that in some circumstances (what ? when ?) CCE may produce crappy m2v files (truncated ? corrupted ?)...



I'm not so sure its corrupt m2v files as it may me segments with still frames. I was able to prove this from 3 seprate disks in this set.


[QUOTE]Originally posted by Sir Didymus
3. For manually reencoding a specific segment, you just need to use a text editor and extract a segment like this from the rebuilder.ecl file:

4. You should feed this segment to CCE, through ECLCCE, so manually start ECLCCE, and drag&drop the segment into the CCE window...



Thank you for the clearification I will try this tonight and report back.

[jdobbs]

The ones I have personally experienced were not single frames. They were standard segments. There was no indication that any error had occurred in the encode -- except the fact that the .M2V file was obviously way too small (I looked at it after the rebuild failure). I just reencoded that segment (using the data from the .ECL file5) and then did a rebuild and everything was ok.

In checking out the error I noticed that the DGDECODE.DLL was not the most current. I have not experienced the error since upgrading it.

[dannyv]

Originally posted by jdobbs
The ones I have personally experienced were not single frames. They were standard segments. There was no indication that any error had occurred in the encode -- except the fact that the .M2V file was obviously way too small (I looked at it after the rebuild failure). I just reencoded that segment (using the data from the .ECL file5) and then did a rebuild and everything was ok.

In checking out the error I noticed that the DGDECODE.DLL was not the most current. I have not experienced the error since upgrading it.

I created an item.ecl and manually re-encoded the m2v file.

CCE indicates its 1 frame with a duration of .01 sec.
The new m2v file created was 2.5 megs which seems large for 1 frame.

the entire segment consist of 1 cell - Rebuilding segment 16 VOBID: 5 CELLID: 1

I did a rebuild after re-encoding the above segment and again at the end of the rebuild at 99.99% when it went to do the navpack for segment 16 it came up with error 9.

Note: Segment 16 is the last segment in the rebuilder.ecl file consisting of 1 cell.

So where do I go from here?

[jptheripper]

exactly the problem i have

encode that one cell with 2.50 instead of 2.67.. it should work

[dannyv]

Originally posted by jptheripper
exactly the problem i have

encode that one cell with 2.50 instead of 2.67.. it should work

Tried 2.50 for that cell but 2.50 complains that the .ecl is not valid for that version. Is there somthing I need to change in the ecl for that cell?

[item]
title=V01001600005001
aud_out=0
vaf_file=E:\LO\4\D2VAVS\V01001600005001.vaf
aud_file=E:\LO\4\D2VAVS\V01001600005001.mpa
file_focused=0
packet_size=2048
width=720
height=480
frame_rate_idx=1
cbr_brate=6000
vbr_brate_avg=393
vbr_brate_min=0
vbr_brate_max=7046
seq_endcode=1
dvd=0
half_width=0
half_height=0
lum_level=0
aspect_ratio=2
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
all_closed_gop=0
fix_gop_length=0
samples_per_sec=44100
stereo=2
brate_idx=7
crc=1
progressive=0
alternate_scan=1
intra_dc_prec=2
aud_mode=0
tc_ref_frm=0
drop_frame=0
fix_vbv_delay=0
letter_box=0
pulldown_detect=0
offset_line=0
create_new_vaf=1
credits_tweak=0
credits_start=0x00000
credits_brate=1000
h_filter=0
h_filter_idx=8
dither=0
dither_max=8
qmat_idx=0
quality_prec=4
timecode=0x0000000
video_type=1
vid_file0=E:\LO\4\D2VAVS\V01001600005001.m2v
vid_file1=E:\LO\4\D2VAVS\V01001600005001.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=7046
vbr_bias=10
vbr_pass=1
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=E:\LO\4\D2VAVS\V01001600005001.avs
frame_first=0
frame_last=1
encode_first=0
encode_last=1

[Trahald]

i wonder if it could just be ripped in dvddecrypter via ifo-mode demux (split by cell) and dropped in any problem cells with the correct filename. (specifically this single frame stuff that wont have a size impact)

[dannyv]

Originally posted by Trahald
i wonder if it could just be ripped in dvddecrypter via ifo-mode demux (split by cell) and dropped in any problem cells with the correct filename. (specifically this single frame stuff that wont have a size impact)

That's an idea or I can prepare under 2.50 and build the cell info.ecl from that, encode it then try the rebuild again. These could be viable work arounds but it defeats the simplicity of rebuilder if you need all these work arounds. I hope jdobbs can work this problem out.

@djobbs

Note in my previouse post

[file]
name=E:\LO\4\D2VAVS\V01001600005001.avs
frame_first=0
frame_last=1
encode_first=0
encode_last=1


The first and last frames this indicates its a 1 frame file. If played in power dvd it gives and unknown file type error. The previous m2v file plays fine. Could this be some sort of protection?

[Sir Didymus]

Originally posted by dannyv
That's an idea or I can prepare under 2.50 and build the cell info.ecl from that, encode it then try the rebuild again. These could be viable work arounds but it defeats the simplicity of rebuilder if you need all these work arounds.

...

Could this be some sort of protection?

If I understand correctly, suggestion given by Trahal is more intended as a testing option in order to be totally sure the problem is in that specific 1 frame cell. If you extract the m2v from the original VOB file and the title rebuild correctly that would lead to a very bad conclusion (i.e. that in some circumstances also the CBR @ 6000 Kbit/s encoding of still frames is not killing all of the still frame issues...). On the other hand, if you are not able to rebuild the title, even using the original m2v file that indicates the problem is elsewhere...

As an alternative to the suggested way, I sometimes am using VobEdit, --> demux by cell id...

Cheers,
SD

P.S. Don't think it a sort of protection: if the cell is playable on a standalone, it should be possible to decrypt it, to re-encode, and to rebuild...

[dannyv]

Originally posted by Sir Didymus
If I understand correctly, suggestion given by Trahal is more intended as a testing option in order to be totally sure the problem is in that specific 1 frame cell.
As an alternative to the suggested way, I sometimes am using VobEdit, --> demux by cell id...


Ahh now I understand. I'll give it a try this evening and report back. I am not an expert on the inner workings of encoding so if I seem to be missing the point on something, leaving out any vital information or going about troubleshooting incorrectly please let me know. My only goal here is to assist in problem solving to make RB a great program.

[dannyv]

Originally posted by Sir Didymus

As an alternative to the suggested way, I sometimes am using VobEdit, --> demux by cell id...


@Sir Didymus

I took a look at VobEdit and have a few questions.

Please note: I'm at work and don't have access to the actual project that has the problem so I'm trying vobedit on any title I had available just so I can get fimilure with the vobedit program.

I demuxed the last vob in the set by cell id as you instructed above and noticed it saved each cell as a vob file. I played one of the cells in power dvd and noticed it has audio so I guess my question is what do I do with it from here? Do I rename the vob to m2v and drop it in place or do I need to strip the audio out? Sorry if this is an elementry question but I haven't worked with these tools before.

[Sir Didymus]

No, no...

Now you have the cells of the last VOB separated, but they are still muxed...

Please consider the very initial cell you get may be wrongly demuxed,
(since it may be across to a VOB boundary), but you need the last cell
of your VOB, if I understand well, so the method should be safe...

Well at the point you are, just open again the single last cell with VobEdit and this time:

Demux --> Mpeg Stream

You will produce an additional single file with the m2v extension, that should be exactely the one of the cell you want to work with...

Check with some Media Player, to be sure, and rename it to the proper m2v filename before rebuilding...

And keep us informed about the result...

:)

Cheers,
SD

[dannyv]

Originally posted by Sir Didymus
No, no...
Well, just open again the single last cell with VobEdit and this time
Demux --> Mpeg Stream. You will produce a file with the m2v extension...

Check with some Media Player, and rename it properly before rebuilding...

And keep us informed about the result...

:)

Cheers,
SD

Now I understand perfectly. I just tried it on my test file and it worked perfectly. Thank you for clearing that up for me. I will try it on the problem file when I get home and report back.

Just to recap what I'm doing.

1. I demux the last vob in the set via cellid
2. I then demux the problem cell from the above result via mpeg stream to produce the m2v file and play it to make sure its good.
3. rename it to the problem cell name.
4 drop it into the d2vavs directory and try the rebuild again.

[dannyv]

@Sir Didymus

I tried to reply to your PM but your mailbox is full. Just thought I'd let you know.

[dannyv]

I extracted the original source blank cell as outlined previously.
I inserted the original blank cell as V01001600005001.m2v into the d2vavs directory and it completed the build with no problem. Funny thing is the original blank frame is only 5.34kb where the one that RB produced is 2.5mb. How is this possible? And why is this happening.

<<EDIT>>
The m2v file that dvd-rb created which is 2.5 megabytes will not play in powerdvd it gives an error invalid file type which leads me to believe the file is being corrupted in someway during the encode process. I've done 3 disks in the set that all had this same problem with the same 1 frame file. I also reencoded disk 4 which this test was based on 3 seperate times with the same results. I've also manually re-encoded the cell and had the same results.

[Sir Didymus]

2.5 MB :confused:

I wonder how may CCE create such a monster...

It is two order of magnitude bigger than what is reasonable to expect for a single frame CBR encoded @ 6000 Kbit/s...

It's really a bad situation, since a very basic assumption for the proper working of Rebuilder is to thrust in the controlled applications (Avisynth, DGIndex, CCE, ...)...

Maybe something peculiar is present in the configuration of your PC ?
Maybe some seriuos bug is really present in these applications ?

Anyway troubles on the Jdobbs path...

All the best,
SD

[dannyv]

Originally posted by Sir Didymus

Maybe something peculiar is present in the configuration of your PC ?
Maybe some seriuos bug is really present in these applications ?

Anyway troubles on the Jdobbs path...

All the best,
SD

Trouble is not with the PC I was able to produce this on 2 seperate PC's. As we speak I'm backing up star trek original season 3 and star trek voyager season 7. Lets see what happens to those.

[dannyv]

Just did Star trek voyager season 7 and this came out fine. Did star Trek the original series season 3 and the error 9 happened on 3 of the disks I've done so far and all at the end of the rebuild. I will check tonight to see if its the blank cell problem again.

<<Edit>> I just want to add that this also happened on star trek the original series season 2 which I did about 2 weeks ago. It must have somthing to do with the way these disks are mastered. It seems the voyager series processes fine but the original series has problems and they both come from the same studio. Also the law and order svu season 5 series has the same problem. I've done all the law and order series that are availabe with cce 2.50 and they all were fine but this last one with 2.67 has the error 9 problem. I would expect that if I went back and re-did the law and order's that I did with cce 2.50, with 2.67 they would produce the same error but I am not in possession of the originals at this time so I can't test it.

<<EDIT 2>>

I was premature on star trek voyager season 7. It seems disk 7 error 9'ed. Read further down in this thread for my test results.

[jdobbs]

Which set of the STOS are you doing -- the original ones that came out on DVD, or the "Complete Season" discs?

[dannyv]

Originally posted by jdobbs
Which set of the STOS are you doing -- the original ones that came out on DVD, or the "Complete Season" discs?

The complete season sets that just started releasing in 2004, not the original ones released several years ago that were released by volumes.

[dannyv]

The error 9's were caused again by corrupt single frame m2v files. They were 2.5 megs just like the one I found in law and order. This time there were 4 corrupt m2v files. The disk has four episodes and a preview for each episode. The corrupt m2v file was found at the end of each preview. I got tired of doing the rebuild for each failure so I sorted the d2vavi directory by file size and tested all the m2v files I found that were 2.5megs and none would play in powerdvd. I then copied the same blank cell from the original rip to each of the corrupt files. It then rebuilt correctly with no errors.

It seems that the corrupt m2v file is always 2.5megs regardless of the lenth of the single cell whether its a 1 second cell or a .01 second cell.


<<EDIT>>
Checked the second disk in the set and the same 4 m2v files were corrupt. I imagine the rest of the disks in the set will produce the same 4 corrupt files.

<<EDIT 2>>

I just finished star trek voyager season 7 and disks 1 - 6 went fine with no errors.

Disk 7 finished with an error 9

I sorted the d2vavc directory and found 10 2.5meg m2v files. With the exception of 1 file 9 of them were corrupt. I fixed these files in the same manor as above and it did the rebuild with no errors. This disk has 10 special features on it and the corrupt blank cells were placed at the end of the first 9 features.

Note: this was done on a different computer then the star trek original series disks which rule out a problem with the computer or its configuration.

[dannyv]

Finished the rest of the disks and all the disks had the same 4 bad cells with the exception of disk 7 which has the extra features this had 12 bad cells.

@Jdobbs

Whats next as far as you addressing the problem and is there anything I can do to help?

[jdobbs]

What date is on the DGDECODE.DLL file you are using? This sounds familiar...

Also... try playing back the .AVS files with WMP... how do they look?

[wrxblaze]

.........I've done all the law and order series that are availabe with cce 2.50 and they all were fine but this last one with 2.67 has the error 9 problem. I would expect that if I went back and re-did the law and order's that I did with cce 2.50, with 2.67 they would produce the same error but I am not in possession of the originals at this time so I can't test it.

Dannyv which encoder through the 4 bad cells and the 12 bad cells?

[jdobbs]

Hmmm... I typically use v2.50 so maybe that's why I haven't seen these??? I'll start doing more encodes with v2.67 to see what happens.

[dannyv]

Originally posted by jdobbs
What date is on the DGDECODE.DLL file you are using? This sounds familiar...

Also... try playing back the .AVS files with WMP... how do they look?

My dgdecode is dated 06/07/04 its the newest version that I'm aware of. You can see my complete configuration at the bottem of the post.

When playing the AVS through mplayer it plays 10 seconds of blank (black) frames. This is a little weird since the original source cell is only .07 sec.

[dannyv]

Originally posted by wrxblaze
.........I've done all the law and order series that are availabe with cce 2.50 and they all were fine but this last one with 2.67 has the error 9 problem. I would expect that if I went back and re-did the law and order's that I did with cce 2.50, with 2.67 they would produce the same error but I am not in possession of the originals at this time so I can't test it.

Dannyv which encoder through the 4 bad cells and the 12 bad cells?

I did the entire Law and order with 2.67 and all the disks get the error 9 caused by a single cell corrupt m2v file at the end of each disk. I still have one of the disk's I'm saving for testing purposes.

The series that has 4 bad cells is disks 1-6 of star trek the original series year 3 the 7th disk has 12 bad cells.

The series star trek voyager year 7, disks 1-6 finish with no problems but disk 7 has 9 bad cells.

It seems these cells are put at the very end of eather an episode or special feature.

I will be saving one disk from each set for further testing as jdobbs works out the problem.

[dannyv]

Originally posted by jdobbs
Hmmm... I typically use v2.50 so maybe that's why I haven't seen these??? I'll start doing more encodes with v2.67 to see what happens.

CCE 2.50 works fine on these problematic disks. The problem is with 2.67. I only just switched from 2.50 to 2.67 in the last 2 weeks to take advantage of the superior quality of interlace materal that 2.67 gives and this is when the problems started. I have a feeling any episodic interlaced materal will produce this problem. I have not gotten a whole episodic set to work yet.

[Craz]

My experience on this runtime error:

http://forum.doom9.org/showthread.php?s=&threadid=89322

[Rockas]

Correct me if I'm wrong but it seems like this error only happens on NTSC sources?!?!?!

[Craz]

wrong, the DVD that gives me problems is R2 PAL DVD9 ;)

[Craz]

Originally posted by dannyv
CCE 2.50 works fine on these problematic disks. The problem is with 2.67. I only just switched from 2.50 to 2.67 in the last 2 weeks to take advantage of the superior quality of interlace materal that 2.67 gives and this is when the problems started. I have a feeling any episodic interlaced materal will produce this problem. I have not gotten a whole episodic set to work yet.

My problematic DVD is also an Episode DVD, the CCE i'm using is 2.66.

[Methanoid]

and I was using 2.50 with problem before I gave up :D

[dannyv]

Originally posted by Rockas
Correct me if I'm wrong but it seems like this error only happens on NTSC sources?!?!?!

In my case it only happens on eposodic ntsc sources.

[glassvial]

Happening here when trying to open the source, RB v0.75. Episodic, NTSC, R1.

[2nd_Gunman]

I received the dreaded "runtime error 9" during the rebuilding stage of "Equilibrium" using CCE 2.67 and DVD Rebuilder .71.

Rather than use the "Big 3" method as usual I set up Rebuilder to work with Procoder2 and EclPRO v0.25a beta and this encoded "Equilibrium" without incident

[EnDeR_PL]

S.W.A.T R1 PAL

[dannyv]

I haven't tested the last few releases of RB so I desided to test 076 with my 3 usual test titles and I'm still getting the error 9's during rebuild as described in this thread starting from page 6 on.

[2nd_Gunman]

Originally posted by 2nd_Gunman
I received the dreaded "runtime error 9" during the rebuilding stage of "Equilibrium" using CCE 2.67 and DVD Rebuilder .71.

Rather than use the "Big 3" method as usual I set up Rebuilder to work with Procoder2 and EclPRO v0.25a beta and this encoded "Equilibrium" without incident


Same problem and solution executed by me again, this time with "The Motorcycle Diaries".

[wmansir]

I just received a Error 9 at the end of a batch job. Luckily it had completely finished the jobs. The last thing in the status box was:


Done.
Batch Job #1 finished in 00194 minutes.
- HIGH/LOW/AVERAGE Cell Bitrates: 3,717/393/3,366 Kbs

Batch Job #2 finished in 00180 minutes.
- HIGH/LOW/AVERAGE Cell Bitrates: 3,449/393/3,315 Kbs

Batch Job #3 finished in 00201 minutes.
- HIGH/LOW/AVERAGE Cell Bitrates: 3,497/393/3,318 Kbs

Batch Job #4 finished in 00235 minutes.
- HIGH/LOW/AVERAGE Cell Bitrates: 3,559/393/3,343 Kbs



I don't know what it would be doing after that to cause this error, but it's the first error 9 I've seen in a long time. Although I don't use batch processing often.

I just thought of something, could it be because I deleted the source directories of the first couple of batch jobs after they finished, but before the batch process was complete? Also, I was reusing the working directory if that matters.

[jdobbs]

I'm in the middle of a batch job now. I'll see how mine turns out.

[wmansir]

I just finished a 2 job batch without any errors. Of course I didn't delete the source files before the batch finished this time.