MTR 2.6 and Padded vs NON-Paded VOBs

[Albe Sure]

Hey-

First off...let me just say, GREAT JOB with MTR version 2.6. I have Mac G4 w/ Dual 1.25 gHz processors...had been experiencing significant problems with crashes when using MTR 2.x. In addition to the many quality new features the new version 2.6, it's stability has been excellent for me thus far, and finally I have an answer as to why I was experiencing so many problems with the previous versions of 2.x.

Now for my question. Among other things, with MTR version 2.6 Geezerbuttz has:
• Added the ability to extract DVDs with ARccOS copy protection, along with new Full Disc and Main Feature modes for those discs
• Added the ability to handle VOBs with bad sectors, which get padded with dummy data, and notify the user at the end of extraction that read errors were encountered
• Added bad cell detection in Title Only and Title – Chapter modes, so they automatically get skipped; useful for ARccOS DVDs

These new features are SUPER AWESOME, and are invaluable in making it possible to backup next generation DVDs that now seem to be appearing in greater abundance. So, when MTR detects "VOBs with bad sectors" that it determines are "padded with dummy data" is the error message that is then generated at that point in the RIP only generated when such a specially engeneered DVD is encountered? Or would such a message also be generated if there is physical damage to the DVD that has caused MTR 2.6 to experience a read error?

Also, regarding the two options presented when MTR 2.6 detects "VOBs with bad sectors", namely to either pad or delete the VOB in question, what would basically be the difference regarding the final output? Like, basically, what does MTR's action of padding an offending VOB do in terms of the operation of the resulting DVD RIP? And, how would choosing either option affect standalone operation (if the file is small enough to be burned without size reduction), and also in size-reduced operation using DVD2One, Popcorn, and/or DVDRemaster?

Sorry for the length of the post. Geezerbuttz and WiseWeasel, you guys are SO TERRIFIC for all your efforts in producing and continuing development of an application of as HIGH QUALITY as MTR. THANKS SO MUCH FOR ALL YOUR HARD WORK, and a very **HAPPY HOLIDAYS** to you both!!!

-A.S.

[geezerbuttz]

Its very early , and im a liitle unwell ,so I will be quick.

If a DVD has deliberate bad sectors on it , the structure of the disk must be created so the StandAlone DVDplayer never encounters those sectors , after all , a bad sector is a bad sector , and a setTop DVD player is just another laser..

If the settop player hit the bad sector , it would cause the movie to stutter / corrupt etc etc.

Now , nobody is gonna pay for movie that is deleberatly corrupted , so the sectors that are bad are useualy unreferenced or jumped over by the IFO cell commands etc etc...

if we pad the corrupted vob to maintain its correct size , all the offsetts in the IFO will match , and the dummy data will never be read , so the movie will play.


In ARccOS mode , some of te VOBS are nothing but bad data spread with random bad blocks....These VOBS cant be referenced as they would never play and lock up your DVD player.

The ARccOS mode checks the IFO to see what VOBS it 'realy' needs and rips those only...

thats it .

GB