DVD-Video Mastering Errors

[jdobbs]

Sorry for taking so long to respond but I wanted to repeat my steps to be absolutely sure. The source files were ripped with dvddecryptor and not preprocessed with anything.

dvdrb 0.93.2 - One click, movie and menus, output to ISO. Anydvd doesn't complain.

Using the source files from 0.93.2 and doing the rebuild + ISO step with rc2, Anydvd doesn't complain.

dvdrb rc1 or 2. One click, movie and menus, output to ISO. Anydvd doesn't like it, and reports the dvd is not mastered correctly.

I have tried using Pgcedit v0.6 to compile an ISO from the rc2 DVDFILES folder and this has the same error with Anydvd.

For the sake of jdobbs' sanity the iso's reported as incorrect by Anydvd have been burned and play flawlessly on a standalone player.

At the end of the day it's not a huge problem and the reported error is likely to be attributable to Anydvd as previously guessed, but something changed recently in dvdrb to prompt the messages.

I hope some of this helps. On the next version I'll put a switch that will allow you to burn without padding.

[jdobbs]

You just can't win on these features. When I first added ISO output mode I had several posts that were concerned that that 32k padding wasn't inserted and a failed IFO might cause a disc failure. So I added the padding (even though the liklihood of failure was extremely low in my opinion). Now... AnyDVD doesn't know what to do with it... so DVD-RB is faulty.

sigh.

[mayhem2408]

Now... AnyDVD doesn't know what to do with it... so DVD-RB is faulty.

sigh.
I have now decided to try using DVD Region+CSS Free and it is working OK without any Mastering errors and is unlocking my Sony RPC2 DVD Drive. So at this stage I am happy with DVD RB and will continue to use the ISO creation with Padding and stop using AnyDVD until they fix this issues with it.

[jdobbs]

One thing to add to the Anydvd problem with dvdrb iso. If I use dvdremake pro to postprocess the DVDFILES folder (rmoving menu buttons etc), then the final output generated works fine with Anydvd.

Curiouser and curiouser... :) And how is the final output generated? More than likely it doesn't have the 32k padding -- and there's the dilemma. Without the padding there is a possibliity of the BUP not performing its function in the event of an IFO failure -- but it will work with AnyDVD.

[winny]

I should have chosen my wording better in the previous post, sorry.

After post processing the DVDFILES folder with Dvdremake Pro the amended output is saved to a new folder, not directly to an iso.

This can then be converted to an iso with imgtools classic or pgcedit\mkifos and Anydvd is happy with the result when mounted in Daemon or burned to disk. Even if the 32K padding option is enabled in pgcedit it still works.

This led me to think it wasn't the iso creation that was the cause, but there something else that the RC versions are doing to the rebuilt content that isn't present in 0.93.2.

I hope this makes more sense.

[jdobbs]

As I said earlier, except for the addition of the 32K padding the ISO creation code in v0.93.2 and RC1/2 is exactly the same. Frankly, DVD-RB does very little anyway -- it is MKISOFS.EXE that creates the ISO.

[winny]

I don't believe the problem is with dvdrb's code for iso creation, or any other tool used for iso creation. The problem already seems to exist in the dvdfiles output folder.

From a previous example, a dvdfiles folder created with 0.93.2 can be made into an iso with the tool of your choice, and Anydvd will not complain.

The same project using rc1 or 2 creates a dvdfiles folder that can not be made into an iso without complaint from Anydvd.

Is it possible a change was introduced in the rebuilding process between 0.93.2 and rc1 or 2, maybe as a byproduct of all the work gone into ILVU?

[jdobbs]

I don't think you understand how the 32k padding works. If you create a VIDEO_TS folder for output to ISO with 32k padding -- YOU HAVE TO BURN IT WITH 32K PADDING. If not, the sector pointers in the IFO files are wrong (they are off by whatever amount of padding was needed):

From the update log:
- Added ISO failsafe code so that padding is inserted
at any time it may be possible for an IFO and BUP to
overlap in the same ECC. This dramatically decreases
the possibility of a scratch ever damaging both an
IFO and it's corresponding backup (BUP) file (which
can render a disc unplayable). Note that this action
is only taken when DVD-RB has been instructed to
create an ISO image. Also note IFOEDIT will
incorrectly see the changes to the IFO for padding as
offset errors. Do NOT perform an IFOEDIT "Get VTS
Sectors" against a VIDEO_TS folder that has been built
for ISO unless you are planning to use some other
burning package to create the disc -- as IFOEDIT will
incorrectly change the values back to the non-failsafe
state.
Note the highlighted part... if you are planning to burn with ANY package other than using the ISO DVD-RB created, and there is a need for padding (again I stress, this is rare, except in movie-only discs) -- you can't have ISO creation option enabled. The VIDEO_TS folder will have been modified for padding.

But, as I said earlier, 32k padding can be turned off in the next release.

If you want to create a VIDEO_TS that has not been modified for 32k padding from a source that has already been encoded, you can just switch to 3 step mode, turn off the ISO creation option, and REBUILD.

I stress, though... the ISO created by DVD Rebuilder is DVD compliant. The problem is in AnyDVD.

[sneaker_ger]

I did a short test and I believe that winny is right!

I backed up Matrix Reloaded with DVD-RB (1.00 RC2, movie only)and let it make an iso and burned that iso with Nero - then I installed AnyDVD and it complains about the DVD.
Then I tested a DVD I backed up with Nero Recode (again movie only) and of which I created an iso with PgcEdit with the 32k padding and burned that one with Nero and it works just fine with AnyDVD.

There must be something wrong in DVD-RB that has nothing to do with the iso creating and its 32k padding. Also see my posts about Star Wars Episode II above.

[winny]

Thank you so much for the explanation and patience, it's greatly appreciated :D

I promise never to mention it again!

[winny]

@sneaker_ger. I was fairly sure I'd duplicated my steps with 0.93.2 and rc2, but this doesn't fit in with the explanation above. So i concede it must have been me, and Anydvd still has bugs :)

[jdobbs]

I did a short test and I believe that winny is right!

I backed up Matrix Reloaded with DVD-RB (1.00 RC2, movie only)and let it make an iso and burned that iso with Nero - then I installed AnyDVD and it complains about the DVD.
Then I tested a DVD I backed up with Nero Recode (again movie only) and of which I created an iso with PgcEdit with the 32k padding and burned that one with Nero and it works just fine with AnyDVD.

There must be something wrong in DVD-RB that has nothing to do with the iso creating and its 32k padding. Also see my posts about Star Wars Episode II above.Sigh.

[k2002rahmani]

I would contact Slysoft to make sure that its product does not give meaningless errors in future releases. :D

[k2002rahmani]

Also, I would like someone experiencing this error to try using ImgTool Classic on the DVDFILES folder.

[Carpo]

what i cant understand is why someone would want/need to use anydvd on a dvd that has had all protections removed when it was ripd with dvddecrypter or some other ripping tool

[winny]

Up to now it's just something that sat quietly in the background until it was needed. It's useful for the odd region 1 disk that comes my way as my dvd drive ran out of region changes a while ago.

It's now turned off by default to stop the nagging error messages.

[sneaker_ger]

Also, I would like someone experiencing this error to try using ImgTool Classic on the DVDFILES folder.

I've tried it with Matrix Reloaded. The iso created by DVD-RB, the iso by PgcEdit with 32k padding and the iso by PgcEdit without the 32k padding make AnyDVD return an error message when inserting the DVD.

[jdobbs]

Ok. Now turn off the ISO creation option in DVD Rebuilder and do a REBUILD. As I said above, if you build the VIDEO_TS folder for ISO -- you will get that problem no matter what package you use to burn. The pointers have been modified for 32k padding.

I've explained this as well as I can and I am confident that the problem is in AnyDVD. If anyone wants to keep debating it you'll have to do it with someone else from here on in.