Build does not work right when trying to replicate 99-title DVD

[Johnny Shanley Productions]

Ugh, Here I am again. For some reason, whenever I try to make a 16.3GB VIDEO_TS into a 8.5GB ISO, it doesn't work right. If I have "Preserve Full Path Names" checked, it can save the contents space but it sets the contents type to "Data" instead of "DVD-Video", but if I don't, it doesn't save space and gives me a warning and sets it to Blu-Ray type instead of "DVD-Video". This is very weird, because I have an ISO of Baby Neptune 2009, and it is bigger than 8.5GB in total, and it does play as a DVD-Video ISO. However, the ISO I am making does not play right for some reason when tested in VLC. I do have the "Optimise Duplicate Files" option checked, but it doesn't work for DVD-Video. Also the layer-break pop up does not show for some reason.

BTW, yes I am trying to replicate the 99-title protection seen on Disney DVDs from late-2008 until mid-2012 on my ISO.

Would it be possible to make a version of ImgBurn that can build a DVD-ISO with duplicate/fake titles from an HDD/SDD/that has 99-titles?

[dbminter]

What do you mean by a 16.3 GB VIDEO_TS?  That's definitely way too much for a DVD Video on a DVD-9.  If you've got a 16 GB VIDEO_TS after decrypting one of those ARCOSS discs, then compressing it down to 8.5 GB will almost always never work.

 

Then, you mention HDD and SDD with 99 titles.  An HDD is a Hard Disk Drive, which is a PC storage device.  And I don't know what an SDD is.

[Johnny Shanley Productions]

Here's a little update: I actually fixed it: All I had to do is use PowerISO to fix the directory. Also I mean HDD because I was editing a DVD I ripped to there and then I make edits to it

Edited 11 hours ago by Johnny Shanley Productions

[Johnny Shanley Productions]

BTW This is what i mean 16.3GB Video TS

[dbminter]

Well, that VIDEO_TS may be 16 GB, but it's not a DVD Video compliant VIDEO_TS.

 

My bigger concern is why ImgBurn thinks that fits on a DVD+R DL?  16 GB is like twice that size!  I am only guessing this is an error in the software and it's incorrectly assuming by finding a VIDEO_TS folder that it should fit on a DVD+R DL.

 

Wait, none that screenshot makes sense!  How can 17 billion bytes fit into an image size of 7 billion?  Are you simply just copying the VIDEO_TS from the Disney DVD physical disc itself into ImgBurn?  If so, that definitely won't be a playable DVD Video ISO.

[Johnny Shanley Productions]

Actually, it's a Fanmade DVD I made myself LMAO

[Johnny Shanley Productions]

And I did test the ISO after editing with PowerISO, it works fine, at least on VLC, I can also mount it too

Edited 7 hours ago by Johnny Shanley Productions

[dbminter]

Well, it's definitely not DVD Video compliant at 17 GB.

[Johnny Shanley Productions]

Actually, someone did manage to copy a DVD that has 99-titles (their ISO, as well as the one I have are from a Private Google Drive) and their copy works fine, the ISO even does say it has 6.41GB, when it's actually 13GB. So it's definitely possible to detect the fake/duplicate files and still be able to burn them onto a blank disc; here's proof BTW (this is a burned disc): 

 

[Johnny Shanley Productions]

And yes, this DVD does have the 99-title protection

[Johnny Shanley Productions]

The ISO i am making also has a layer-break as well. I wonder if It's possible to edit the layer-break in ImgBurn

[dbminter]

99 Titles is the maximum # for DVD Video compliance.   So, it's not that the DVD has 99 Titles that is the problem.  It's the 17 GB VIDEO_TS.  And whatever home made protection you're trying to add to it.  While that ISO may work in VLC, I would highly doubt burning it to a DVD+R DL will produce a disc playable on DVD player hardware connected to a TV.  This disc you burned may play on a PC, but I've no idea from the screenshot if that's a PC playing it or not.

[Johnny Shanley Productions]

it is

[LIGHTNING UK!]

So it needs ‘optimise duplicate files’ enabled to make it smaller but when it’s detected as a dvd video structure, it turns that off due to ifo and bup files intentionally being duplicates. 
 

There’s no way around that as the program is working as per design. The design just doesn’t work for structures like that.

[Johnny Shanley Productions]

Ah ok