Log in

View Full Version : F1 2003 review: Error in UpdateIFO - shouldn't happen (contact developer)


raddygast
24th March 2005, 19:12
I've been trying to back up F1 2003 -- the season in review disc. It's sort of episodic -- like 18 different events, and each event has an INTRO, On Pole!, Race, and Final Results. And you can naturally click on Play All for each race too. So the structure is a bit complicated but not too complicated -- I don't think there's multi-angles or seamless branching or anything. And the audio and subtitles complexity is nil -- one language, one type of audio, no subtitles.

But I'm getting this mysterious Error in UpdateIFO in the rebuild stage that causes DVD-RB to crash.

The source is completely unpreprocessed. Ripped by DVDD in ISO mode (every "remove" box checked except Remove IFO Structure Protection). Then mounted using d-tools and the virtual drive is used as RB's source. I even didn't do any tweaking with RBOpt the second time around. Everything is stock, 3-click mode.

I have searched through the archives and have seen a bunch of messages regarding this error. jdobbs said it occurs when there's a mismatch between the source disc and what CCE ended up encoding.

As far as I can tell, CCE had no errors during the encode. At least the rebuilder.log seems totally clean. (I could post it but it would say nothing). The only evidence of error is that the log trails off while rebuilding VTS_02, VOBID 1.... it says: Updating NAVPACKS for VOBID_01...
and that's the last entry, because at that point an error dialog pops up saying "Error in UpdateIFO - shouldn't happen - contact developer!" Then when you dismiss it another one "Stop statement encountered" and when you dismiss that DVD-RB crashes.

Is there a place to look to see if CCE had errors? Is there some kind of CCE log or do I have to enable that manually?

Some suggestions were to rip the disc in ISO mode and then mount that image using daemon tools and use the virtual drive as the RB Source. This time around that's what I did. (Last time it screwed up I had used File Mode to rip it). But the error occurs in the same place.

Please note, it seems like the output of DVD-RB is playing fine... I tried to view it and it seemed ok, but I didn't sit through the whole thing. It's very long.

The disc itself caused DVD Decrypter to say:

"<snip>
W 18:57:33 Possible Structure Protection Found!
W 18:57:33 1 area has been marked as 'suspect'.
W 18:57:33 Dummy sectors will be inserted where necessary.
I 18:58:35 Operation Started!
I 18:58:35 Source Device: [0:0:0] LITE-ON DVDRW SOHW-1633S BS0K (F:) (ATA)
I 18:58:35 Source Media Type: DVD-ROM
I 18:58:35 Source Media Region Code: 1
I 18:58:35 Source Media Copyright Protection System Type: None
I 18:58:35 Source Media Implementation Identifier: Spruce Technologies
I 18:58:35 Destination File: M:\DVD\Full-ISOs\F1_2003.ISO
I 18:58:35 File Splitting: Auto
I 18:58:35 Remove Structure Protection: No
I 18:58:35 Bad Sector Removal Method: Normal
I 18:58:35 Detect Mastering Errors: No
I 18:58:35 Remove Macrovision Protection: Yes
I 18:58:35 Extracting Sectors... (LBA: 0 - 3972360)"


Are there any fancy DVDD settings I'm supposed to use to rip this disc? I have everything enabled I believe, except for "Remove IFO structure protection." Will that setting help?

Would appreciate any help.

jptheripper
24th March 2005, 19:25
i would try reripping with structure protection removal on, its an option for a reason in my book. Is this a really new disk?

raddygast
24th March 2005, 19:37
It's quite old --- well, I mean, at least it wasn't released till 2004.

Will tell you what happens with that option checked. However, when I last ripped in File mode, I think that option *was* checked (in the File tab in Settings), but I'm not certain so I'm giving it a shot in ISO mode.

Am I supposed to see any indication of "Dummy Sectors" being inserted, in the log? All I ever see in the log is Possible Struct Protect found, 1 area has been marked suspect, dummy sectors will be inserted -- then after that, everything seems fine.

jdobbs
24th March 2005, 20:34
If dummy sectors are inserted you will see a message in DVD-RB's log saying "Null sectors" were found.

raddygast
24th March 2005, 22:15
I checked the rebuilder.log for all three of my attempts. First time I had used DVDD in File mode, remove struct protection. Second time DVDD in ISO, unchecked remove struct protection. Third time DVDD, checked remove struct protection (have not yet done the encode on this one yet).

None of the rebuilder.logs say anything about Null sectors being found.

Is there any more detailed info I can post to get to the bottom of this? It seems mysterious because the output of RB "seems" ok, but I haven't thoroughly checked it by watching it and trying every possible menu option in every combination.

wmansir
25th March 2005, 00:01
To check for a CCE error, the first thing I would do is take a look at the .m2v file for the last segment listed in the log before DVD-RB popped the error. Compare it to the .avs file (which can be opened in a media player) and make sure the video content is the same.

b1ackmai1er
25th March 2005, 13:24
The first time I resolved it by doing Update VTS sectors using ifoedit. This was a preprocessed movie only rip.

The second time I had it I could only resolve it by using rebuilders new no compression mode to rebuild the movie and then use that to process.
This was also a preprocessed movie only rip.

Hope one of those helps.

regards b1m1

jdobbs
25th March 2005, 13:58
Here's what that error means: DVD-RB is going through the cell tables in the IFO file, and has found a VOBID/CELLID combination that doesn't exist in the VOB files. This happens during REBUILD after the VOBs have been written.

That should never happen. If it does it means someone or something has removed the CELL but left the pointer to the cell in the IFO.


[ADDED] I assume this might be able to happen if an M2V was missing, and it was the ONLY source for that CELL...

I'm going to add the VOBID/CELLID to that error message in future releases so it can help with debugging.

b1ackmai1er
25th March 2005, 15:32
@raddygast

If you open the movie up in vobblanker, select the VTS and then view the cells, you will be able to see which cell is causing the problem.

regards b1m1

raddygast
28th March 2005, 10:52
Hmm... vobblanker. I'll try it, but I'm not really sure I understand what I'm looking for. You want me to view the cells in vobblanker? Does that just spit out DVD programming info or can you actually view video segments that way?

I'll try the "RB with no compression" option to "process" the original source, and then use that "processed" source to encode. Maybe that'll work. Anyway, very weird.

raddygast
29th March 2005, 01:45
Originally posted by raddygast
To check for a CCE error, the first thing I would do is take a look at the .m2v file for the last segment listed in the log before DVD-RB popped the error. Compare it to the .avs file (which can be opened in a media player) and make sure the video content is the same.


Ok, the error occurred again. Even though I did a first preprocess phase using DVD-RB in no compression mode. It didn't fix anything.

I checked the AVS and m2v files for the last segment right before the rebuild crash, and they were the same video segment (visually, at least) with the same length etc.

So I'm at a loss.

But I just noticed in rebuilder.ecl, pretty much every segment has a

[file]

section followed by an

[item]

section. But the last segment (31).... only has a [file] section. No [item] section. Maybe CCE is crashing just on the last thing?

jdobbs
29th March 2005, 02:34
Actually they should have an [item] section followed by a [file] section.