weird thing: possible miscalculation with DVDShrink?

[Daether]

First off, thanks so much to DVDShrink for giving us the best DVD shrinking software there is. I've been using it since 2.0 and I think all the features you've added are great.

I read before that after you have used deep analysis DVDShrink is supposed to create perfectly sized output. I just used version 3.1.7.6 for the first time and with deep analysis the reauthored output came out too big for a disc. Is there a new bug?

Weird thing is Windows reports the files to be 4.40 GB (fits).
Nero says the output files are too big though and when I open them in DVDShrink DVDShrink says they are 4.507 GB (too big). I'm no data expert but maybe thats just a matter of file format (NTFS/DVD-ROM)?

Also I noticed DVDShrink made a separate VOB ~500MB for each of 8 titles in the reauthored DVD. I don't remember it being like that before. And with the new ISO capabilities I thought that perhaps DVDShrink is using a new algorithm for its output that has introduced a file size calculation bug.

Or maybe I'm just overanalyzing a fluke?

:confused:

[Kedirekin]

I think it's a fluke. It sounds like the very first disk you tried with version 3.1.7 was one that can't be compress far enough without removing something.

The file size confusion is pretty common. The actual maximum size you can burn to a DVDR is slightly over 4,700,000,000 bytes. Windows Explorer reports this as approximately 4.37 GB. So a windows 4.4 GB file is 4,505 MB, or 4,613,734 KB, or 4,724,464,025 bytes.

The separate VOB (titleset) for each re-authored title is correct. It's worked this way since 3.0b5 IIRC. I don't know how it worked in 2.3. It doesn't matter anyway - the titles would be separate even if they were all tucked into the same titleset.

[DK64_MASTER]

Did you try using DVD Decrypter to burn? Try making the output ISO (or did you use that to burn in Nero?)

[Daether]

Yeah it was a fluke.

I just looked at it again and DVDShrink doesn't realize that that particular DVD can't be compressed to fit until after analysis.

Guess I'll do analysis seperatly from the encoding process from now on to avoid encoding something thats not going to fit.