FixVTS Version 1.25 (New version)

[jsoto]

Originally Posted by jeanl

They mean nothing as far as I know, and I have NO IDEA why FixVTS modifies them!!!!! But I'll know tonight (I'll do some tests using the IFOs that davemorell sent me).

It's difficult to believe that these values make CloneDVD to fail... But may be FixVTS is done anything more wrong in this situation....
jsoto

[jeanl]

Well, you read the message from CloneDVD2:
"DVDManager 0 invalid AdaptedDisc Type"
somehow it reads these values as part of the disc type, the volume number and the side ID are not very far, actually...
I sent davemorell a modified IFO with these bits set to 0, and he replaced the one from FixVTS with the new one, and everything opened fine. Then replaced the old one again and everything failed. I checked that the difference between the two was ONLY these 4 bytes. So I'm pretty confident that that's the problem.
I'll tell you guys tonight what the stupid bug was!
jeanl

[Drinken]

I've create a small stupid program that you might find interesting: it creates a VOB file according to an IFO: you start from an existing vob from any DVD you have and it removes or add navpacks, renumbering them as needed, according to the IFO. Of course, the resulting DVD is completely broken from the video/audio point of view, but it does have the VOBU structure of the original, and oftentimes it's enough to test simple bugs.

I'd be very interested in checking out this piece of code, mind sharing it?

Dr.

[jeanl]

OK guys, it was indeed a STUPID bug (aren't all bug stupid? most for sure!).
I've posted version beta 1.16 here:
http://www.videohelp.com/~FixVTS/Downloads/

FixVTS -- Beta 1.16
- Fixed a bug in the IFO class that cause data to be written in the wrong place, which caused CloneDVD2 to refuse to open the DVD (but otherwise had no other side-effect)...
- FixVTS now updates the last navpack pointers in the menu domain as well, if they're incorrect.

This should fix the CloneDVD2 bug. Davemorell can you check that indeed, this does the trick?
Thanks!
jeanl

[jeanl]

Originally Posted by Drinken

I'd be very interested in checking out this piece of code, mind sharing it?
Dr.

Oh I don't mind one bit. I have to clean it a bit before I do that! As it stands some of the stuff is hard-coded. What would you use a tool like that for?
jeanl

[Drinken]

Not sure what to do with it, consider it educational... I'm guessing that it might be helpful for fixing some old butchered rips I got. VB refuses to process them, but with the "proper" vobs present I think it will. Easier than creating dummy vobs and go through PGCedit/VB mock strip ++ steps.

Did that make any sense? (Disclaimer: I'm NOT talking about downloaded material here, but old backups made with very old software and a stupid guy behind the keyboard (namely me). Sorry that I can't go into more detail, I also got teflon inside my head.).

Dr.

[jeanl]

Drinken, I think my little app wouldn't help you with that: it creates vobs that are completely useless because it totally messes up the video (sometimes replacing video and audio packs by navpacks) and completely messes the original GOP structure (replacing original navpacks with video packs if the IFO does not want them there!).
But you can still try to run FixVTS on your messed up DVDs, and see if that helps. No need to remove unreferenced material.
Why does vobblanker refuse to process your DVDs? What's the error message?
jeanl

[Drinken]

Well IIRC it's mostly vobs for non existant extras that it chokes on, but I might be wrong. There's also some with unsynchronised vob errors (which this surely wouldn't do much for). Haven't looked at it in ages. I was about to post that FixVTS might accomplish the same thing but you beat me to it.

So I guess it's not a big deal.

Dr.

[jeanl]

Well, who knows, give it a shot. The one thing that vobblanker does NOT like (and which FixVTS does not fix) is pgc cells that point to vob cells that don't exist. VB complains and won't open the DVD saying something like "cell not found"....
jeanl

[jsoto]

These cells can be easily removed with PgcEdit, but
VobBlanker also does not like :
A) Wrong references in C_ADT tables (FixVTS fix them )
B) Unsynchronized VOBs:
B.1---> Null packs, produced by DVDdecrypter while reading errored sectors. Fixed by FixVTS
B.2.---> Really unsynchronized, i.e. an offset of some bytes. Very rare, and I think FixVTS is not able to fix it. Is it?
jsoto

[davemorell]

Originally Posted by jeanl

FixVTS -- Beta 1.16
- Fixed a bug in the IFO class that cause data to be written in the wrong place, which caused CloneDVD2 to refuse to open the DVD (but otherwise had no other side-effect)...
- FixVTS now updates the last navpack pointers in the menu domain as well, if they're incorrect.

This should fix the CloneDVD2 bug. Davemorell can you check that indeed, this does the trick?
Thanks!
jeanl

I have just tried your newest release, and it is working like a charm. I tried two ways: video_ts alone and the fulldvd too, and CloneDVD2 had no problem with them.

Thanks for the great work

[Drinken]

Originally Posted by jeanl

Well, who knows, give it a shot. The one thing that vobblanker does NOT like (and which FixVTS does not fix) is pgc cells that point to vob cells that don't exist. VB complains and won't open the DVD saying something like "cell not found"....
jeanl

I think that's the error I got on several discs actually. I think I solved it on a couple by copying a small dummy vob to the missing ones (IIRC I just deleted the unwanted material, as I said, butchered). PGCEdit kill playback and some mucking about usually fixed it so VB was able to process it afterwards.

It's a wonder most of those discs actually works. Well if you don't click on anything outside of "Play" that is... that's probably the only thing that works.

I've learned alot since then though.

[r0lZ]

Yes, if you have accidentally deleted a VOB by hand, or if you can't rip it from a damaged DVD, you can use PgcEdit's Blank Out All PGCs in Domain function to recreate a valid dummy VOB file. In a menu domain, you can even use the option to remove the VOB file completely. In both cases, it fixes the IFO tables.

[weaver4]

Originally Posted by weaver4

I'll try it and get back with you.

I tried it both ways and the audio is still out of sync. Any other ideas?

[bourtzovlakas]

From my experience...
If you use the "remove crap" operation of the psl plugin and then you use FixVTS, you won 't have a/v desync, when you encode to Mpeg4...

[jeanl]

FixVTS Version Beta 1.17
Here's the latest beta for FixVTS.

• FixVTS now renumbers the VIDs as well as the CIDs.
• FixVTS now checks for empty output vobs and renames the others accordingly.
• Restore backups now works better (won't forget files)
• Fixed a bug that occured when the last cell of the last vob was removed.
• Fixed a couple bugs when the vob file was empty to begin with, or the IFO didn't exist.
• Fixed a bug in the IFO class that cause data to be written in the wrong place, which caused CloneDVD2 to refuse to open the DVD (but otherwise had no other side-effect)...
• FixVTS now updates the last navpack pointers in the menu domain as well, if they're incorrect.
• The log is now in the default directory pointed to by the %TEMP% environment variable. To open the log, right-click on FixVTS title's bar, and chose "Open Log".

Enjoy!
jeanl

[r0lZ]

Thanks, Jean!

[dirio49]

thanks Jean

[jeanl]

Originally Posted by weaver4

I tried it both ways and the audio is still out of sync. Any other ideas?

I'm not sure... You're saying that you tried running FixVTS without removing the unreferenced material, and you still got a large a/v missync? I'm not sure what that could come from, but I'm not familiar with the tools you're using...
sorry...
Jeanl
r0lZ, dirio49, you're welcome!

[jsoto]

You're the fastest. Thanks.