"This isn't supposed to happen" error

[SpazzHH]

While trying to backup the R1 version of "The English Patient Bonus Disc", I ran into this jewel with RB Pro 1.04. It happens during encode at nearest I can figure, V01004000000000. It's a very small blank video segment that RB is identifying as ILVU for some reason when no other tool states any ILVU exists on the disc.
I have to leave for work now, but will be back this evening with more info if needed. There really isn't much info in the log due to the stop statement encountered. Just for the Prepare phase.

Spazz

[SpazzHH]

I'm back from work now and have been doing some further looking. The segment in question is supposedly only 3 frames in length. A 3 frame ILVU segment in the middle of nowhere? Something is amiss. Does this make any sense to anyone from the rebuilder.inf:
[V0100000]
Last_Sector=3218919
[V01004000000000]
SCR=4306239183.780
PTS=1335852670.000
Frame_Rate_Code=1
Pulldown=0
Structure=3
Frames=3
Playback=3
First_Sector=3218607
Last_Sector=3218919
Reduction=67.7
Aspect_Ratio=2
HalfD1=0
Convert16=0
EndPTM=-802930484.000
Audio_Sub_Sectors=24
ILVU=1
Video_Sectors=8

[Guest]

Please edit your thread title to comply to rule 9. Thank you.

[SpazzHH]

Please let me know what additional info might be helpfull. I've never run into this one before.

TIA, Spazz

[SpazzHH]

FWIW...If I'm reading things correctly, according to Vobblanker, the segment of source in question is a 0 byte segment containing just 1 pre-command and 1 post-command. Well, back to work again. :confused:

[Guest]

Unless you actually had an error message that says "this isn't supposed to happen", your thread title is still violating rule 9. Please fix it.

[Sir Didymus]

Unless you actually had an error message that says "this isn't supposed to happen", your thread title is still violating rule 9. Please fix it.

Hi neuron2. Just want to clarify about the communication problem I think you are facing... IMHO your quoted sentence is exactely what is happening to SpazzHH: a message box popped out from the application with a text message saying "this isn't supposed to happen"...

I am almost sure about this, since it is not the first person reporting the stated trouble...

Maybe the message from the application is not very descriptive, maybe the poster gave no much additional information in order to understand the process leading to the issue, but surely the forum rule nr. 9 is not infringed here...

All the best,
SD

[Guest]

If SpazzHH had told me that after my first posting, then I wouldn't have issued the strike. Now he'll have to contest it to get it removed, because I can't remove a strike.

[Rockas]

If SpazzHH had told me that after my first posting, then I wouldn't have issued the strike. Now he'll have to contest it to get it removed, because I can't remove a strike.
@Neuron2
Just a silly question... is there any place in the forum where people can see the strikes? is it possible to know if we have one? or had? :D

[Guest]

Only mods can see the strike status. If you get one, an email is sent to you.

SpazzHH, sorry about the misunderstanding. I'll PM Doom9 about it.

[wmansir]

Yes this is an actual error message and here's my post about it (http://forum.doom9.org/showthread.php?p=682543). Unfortunately, I forgot to follow up on it. In fact, I still have the Clerk X disc on my HD for testing.

EDIT: reading further in the thread it seems I did follow up, but when I couldn't re-rip my disc I just discounted it as a possible disc read error. At least now I know why I haven't deleted those files yet. :)

[Guest]

The erroneous strike has been removed. Thank you for your understanding, SpazzHH.

[blutach]

The problem of course is that the segment is too short to be valid (<0.4 seconds = 12 frames in NTSC).

If I were you SpazzHH, I'd use PgcEdit to Kill Playback of the segment. Better still is to blank the segment with VobBlanker, which will intorduce a proper MPEG-2 compliant blank.

Good luck.

Regards

[SpazzHH]

@blutach
Thanks for the info in your reply!! I will cetainly give it a try. Thanks again.

Spazz

[jdobbs]

It's the result of ripping... it usually happens when using DVD Decrypter and AnyDVD at the same time. It just started happening on some recent titles. There is a fix in the new soon-to-be-released version of Rebuilder.

[SpazzHH]

It's the result of ripping... it usually happens when using DVD Decrypter and AnyDVD at the same time. It just started happening on some recent titles. There is a fix in the new soon-to-be-released version of Rebuilder.

Perhaps thats the case with the others, but I think something else strange is going on here. I've tried ripping the disc with three different tools, no combinations, there is no special protections on this disc it is so old. I get exactly the same result every time. A three frame ILVU segment that crashes RB before it ever passes it to the encoder. There aren't even any navpacks or anything in the original. It's 0 bytes on the DVD, but a segment is attempted to be encoded from it? Perhaps somehow RB is being confused by the reuse of cells in this very oddly structured disc? Things just aren't adding up for some reason even though the ripped disc plays fine with IFO Edit's player(Yeah I know, doesn't mean much). I'm lost with this, but I know 2+2 doesn't equal 5.

You can't even blank the darn segment. Not with RB, because it says it's ILVU, and not with any other tool because it has no navpacks to update.

If I had any brains in the subject matter, my money would be on a poorly authored disc. Just about every single one of the 41 segments has the same reused 1 mb cell.

[jdobbs]

v1.05 should be hitting mailboxes soon. Try that one whe you get it.

[SpazzHH]

Will do. Tnx.

P.S. Boy times like this, I wish my e-mail addy started with an "A". :D

[jdobbs]

It doesn't go by name... it goes by date registered (with a couple exceptions for developers, etc). First in, first out.

One of these days I'll need to find a new connection. The current one has a limit as to how many mail messages can be forwarded per minute... so I have to throttle the process down to keep from being blocked.

[SpazzHH]

Unfortunately, the new version doesn't seem to have as much luck as the old version. Right after the status window says that RB has processed a 963,503.7MB ILVU section, I get an error message saying "DVD Rebuilder experienced an error opening AVS. [06:20:25] 00053 00006". And it aborts. This is so strange, because no other tool even reports there being any ILVU on the disc. Even stranger yet that whatever RB is reading from this disc, the new version is trying to process the entire VTS as ILVU, not just the one funky cell like the older version.

B.T.W. I don't even get the "ILVU and/or Interleaving detected" message when I load the source.

[jdobbs]

I'll go pick up the English Patient so I can test it.

Thanks.

[SpazzHH]

I'll go pick up the English Patient so I can test it.

Thanks.

@jdobbs

I know you've been more than busy with the new versions and other fixes, but just didn't want you to forget about this one, so I thought I might give you a small reminder. :)

[SpazzHH]

I am sure this is a structure error, as no other tool will fix or alter the file. FixVTS doesn't work, Vobblanker gives the "unsychronized" error and aborts, yet the disc plays fine in IFO Edit, and Shrink will convert the disc with no errors.
With VixVTS, I do get this:

Replacing blank pack at LBA 73323 with stuffing pack
Adjusting Fwd pointer at LBA 72669
Found VCID 40/1 at LBA 86751 (86751 out)
Done with VOB files. 1 navpack pointers adjusted, 0 packs removed, 0 navpack remapped

But it doesn't solve anything.

[jdobbs]

I had to order that disc -- all I could find locally was the older version that didn't have the bonus disc, it should be here in a day or two. I'll look at it when it gets here.

[SpazzHH]

Thanks a bunch. Would it help any to have a look at the IFO's without the vobs?

[SpazzHH]

@jdobbs

Anything new on this one?

[jdobbs]

It just got delivered yesterday. I'll try it out.

[SpazzHH]

@jdobbs

Anything new yet? Please don't forget about me.:o

[jdobbs]

Yeah, I fixed it for v1.06. The original disc has a fairly large number of "garbage" sectors in that segment that confused DVD-RB. Interestingly they all fall after the last sector that is referenced in the IFO, so I have to assume they were put there on purpose.... which is really lame.

I've added code to filter them out.

[SpazzHH]

@ jdobbs

I just finished backing up my disc with 1.06. It had no trouble at all. :D "Thank you sooooo much for your hard work." says Spazz as he jumps up and down for joy.