@jdobbs: Error in UpdateIFO: Shouldn't happen - Contact developper.

[Craz]

Hi,

I've ran into another problem (another DVD this time). I have a DVD9 disc which was being a pain in the ass to get ripped to HD. I tried several times with several methods (iso ifo file) on different drives.
After the 4th try and a lot of rubbing on the disc with my sweather I finally managed to get the disc on my HD using IFO mode in DVDdecrypter.
Then I started processing the disc in DVDRB v0.75 & CCE 2.67. Everything went smooth (transcoding phase succesfully finisched, CCE started succesfully) untill I woke up this morning. On my screen I had an error message saying "Error in UpdateIFO: Shouldn't happen - Contact developper.". So here I am :p
At the moment I'm trying the same with DVDRB v0.72 to see if it gives any difference.
I kept my working folder from DVDRB v0.75 so if you want to see any of the generated files I can provide them.

Let's hope we can track down this problem too :)

[Khauron]

Rip the DVD with DVDDecrypters File-mode and use no pre-processing. Should do the trick. Also use latest DVDDecrypter.

[pg55555]

Try doing a "fake" stripping with Ifoedit, and then processing with RB.

Khauron suggestion is a good one, but if I understood you, probably it would be difficult to obtain a clean rip.

[Craz]

Originally posted by pg55555
Try doing a "fake" stripping with Ifoedit, and then processing with RB.

Khauron suggestion is a good one, but if I understood you, probably it would be difficult to obtain a clean rip.

Yes, you're right. The disc gives quite some problems to get a clean rip. I tried to rip it in file mode and it didn't work when I tried it yesterday.

How does the "fake" stripping work in ifoedit? :)

[Craz]

Ok dvdrb v0.72 has the same error (see below).
It happens at the end of the "Updating NAVPACKS for VOBID_03" phase. When that phase reaches 100% it gives me the error.

http://members.lycos.co.uk/speerman/images/dvdrb.gif

[Craz]

Noticed one of the files created in IFO ripping was corrupt, so problem (or should i say cause) solved.

[lamster]

I just got an "Error in UpdateIFO" message, rebuilding Mulan 2 (which I already did a few times previously using the same source directory, so I know the files are good.)

The last thing shown is, "Updating NAVPACKS for VOBID_01".

Possibly related - Rebuilder had previously ended in error during phase 3 when I ran out of disk space. I freed up some space and tried a second Rebuild, which is when I got the error. (Actually, it's definitely related - I compared the D2VAVS directory with one saved from a previous attempt, and saw that there were a number of 0-byte M2V files which should have been substantially larger. I had initially thought phase 2 was successful because the target VIDEO_TS directory was not empty; bad assumption on my part.)

[jdobbs]

There was some work done in that area related to the new copy protections... I probably introduced something. I'll check it out.

[lamster]

Originally posted by lamster
I just got an "Error in UpdateIFO" message, rebuilding Mulan 2 (which I already did a few times previously using the same source directory, so I know the files are good.)

The last thing shown is, "Updating NAVPACKS for VOBID_01".

Possibly related - Rebuilder had previously ended in error during phase 3 when I ran out of disk space. I freed up some space and tried a second Rebuild, which is when I got the error. (Actually, it's definitely related - I compared the D2VAVS directory with one saved from a previous attempt, and saw that there were a number of 0-byte M2V files which should have been substantially larger. I had initially thought phase 2 was successful because the target VIDEO_TS directory was not empty; bad assumption on my part.)
I just got the same thing after starting from scratch. This time there's still almost 3 gig free, so the 0-byte M2V files were definitely not caused by running out of disk space.

Another problem is that there was no sign of the Rebuilder window - just the pop-up saying "Error in UpdateIFO". I tried minimizing all my other windows, but I couldn't find the main Rebuilder window. After clearing the pop-up, there was a second one saying "Stop statement encountered", then Rebuilder was gone. If I didn't have logging turned on, I wouldn't have known what the last thing in the status windows was.

(Interestingly, this was with QuEnc 0.54, and the size of the Rebuilt\VIDEO_TS directory is 3,425,677,312 bytes, which is roughly what I was getting for the successful rebuilds using 0.57 and 0.59b2 as described here (http://forum.doom9.org/showthread.php?s=&threadid=89965). I don't know if this is a clue to the other problem or just a coincidence.)

[Vanderlow]

I got the same error as craz did in post 1. Beautiful Mind .74 beta with Procoder. Any idea what this is?

[jdobbs]

The most recent version has a check that warns you if no .M2V was created by the encoder.

[Vanderlow]

Ok I reripped it the same way and rencoded it and no error at the end. So thanks! Must of been a corrupt file or a fluke.