PDA

View Full Version : Encountering a New Rebuilding Error


mnfesq
8th September 2006, 20:43
I am making a back-up of Basic Instinct 2, which is a Sony Video. I successfully ripped it using DVDFabDecrypter, having had no success using PGCEdit/DVDDecrypter. This was my first time using DVDFab - It seemed to work great.

Preparation and encoding phases went well and it appears that all of the m2v files were encoded. But in the rebuilding phase, I get the following error:

Error in UpdateIFO:VTS_01 VOBID: 01/CELLID 02 was not found in the VOB

I did not use FixVTS, figuring that it was not necessary with DVDFab, but now I'm beginning to wonder. Any ideas?

Fishman0919
8th September 2006, 20:52
Try RipIt4Me (http://forum.doom9.org/showthread.php?p=846315#post846315)

jdobbs
8th September 2006, 21:28
Definitely a bad rip. I had a similar report a couple of weeks ago.

You might want to try cleaning the disc and ripping again with DVD Fab... I think it sometimes mistakenly believes all read errors are some type of protection (instead of only certain types).

It will work ok with AnyDVD or RipIt4Me.

mnfesq
9th September 2006, 07:22
I ran FixVTS and did a clean up of the entire DVD (which I had already ripped to my hard drive with DVDFabDecrypter. Then I ran it again with DVDRebuilder and it seems to have come out just fine. I did not get the error I had before.

I guess I'll switch over to RipIt4Me next time I encounter a Sony DVD since that automatically runs FixVTS in the ripping process.

Thanks guys for your responses. I just love DVDRebuilder.

jdobbs
18th September 2006, 23:28
@mnfesq

Just so you know... I never stop looking when I see the possibility of an error.

I found what was causing this and it wasn't a bad rip. This happens where there is a specific sequence of starting/stopping/resuming a job during the ENCODE phase. As a result one or more M2V files may not be created following the RESUME. When you rebuild -- the IFO couldn't be updated because the cell was never encoded.

It would happen very, very rarely and only under very specific circumstances. I've fixed it for the next release.