Using Big3 Method Creating ISOs That Are Too Big Still

[stanjr]

Has anyone had the problem of using the Big3, but still getting ISOs that are too big, by anywhere between 8 and 12 MB?

The method I use is pretty much a "one-click" method: DoItFast4U v1.4.6 with ScenAid v0.9.0.5 (BatchCCEWS is launched and executes CCE automatically). I then use ScenAid to create a script and import that into Scenarist, have Scenarist create the video files, get the appropriate ones together with appropriate ones from the DoItFast4U VIDEO_TS folder, IFOUpdate the appropriate IFOs, then create an image with IMGTool. I use DVD Decrypter to burn the DVD from that ISO.

The last two times I've done this (backing up Absolutely Fabulous disc 1 and 2), DVD Decrypter states that there is not enough free space on the media (the media itself has 4,706,074,624 bytes available; however, for disc 1 my ISO size is 4,719,929,344 bytes, and for disc 2 my ISO size is 4,714,840,064 bytes). I know I can re-encode my material, but I wanted to share this phenomenon with others, to see if I maybe missed something in my process that cause the too-big ISOs.

I have tried DVD Shrink v3.1.7 to shrink down the too-big ISOs, but the program tells me that my ISO has an invalid navigational structure. Have I maybe not run IFOUpdate correctly? I use all the settings as described in all the guides and update only the IFOs that need updating.

Any insight would be appreciated.

[P3gasus]

I use abitually the big 3 method with doitfast4u - reauthorist - docce4u and sometimes (expecially when I have to use scenarist manually), this method produces too big isos.
I don't know why :confused: .

BYE

[n1ck0s]

The one time I ended up w/ too large iso, I was using ReAuthorist to calculate the compression bitrate (instead of DIF4U).

The other time was because I had to manually import an audio stream, which was left out by the Big3 process.

I can't tell you why your project ended up that big, but for the DVDShrink issue you should check this (http://forum.doom9.org/showthread.php?s=&threadid=68769&highlight=dvd+shrink)

[stanjr]

I've noticed upon re-opening the too-big ISOs with DoItFast4U (which reminded me that it was the same way with the original ISOs) that in the "Audio Streams" box there is a "0x0-not used" greyed out checkbox that can neither be checked or unchecked (it isn't checked to begin with). Could this be the culprit for incorrect size calculations? If so, how would I get around it?

[OvERaCiD23]

The only times I've had over-sized projects was from too many CCE passes (lower bitrates, I would run 4-5 passes). If I reduced to 3 passes in CCE, the project would be sized perfectly. I know there are many other factors involved, but in my experience everything else is always right (mainly indicating bitrates that are calculated by ReAuthorist).

[downloada]

hi,

i also have the same problem, big3 generates too big isos. but for me, it started when i first used numenu4u. both of the discs that came out too big were around 10mb oversized. since then, i always lower the bitrate of the main movie just a little so that the output is around 0.01-0.02GB smaller than with the original bitrate (the calc feature of docce/batchcce is really great for this).

now the content always fits on one dvd and noone can tell me that they would spot differences between a video with, let's say 3970 and 4000kbps ;) (also, the reencoded menu raises the mainmovie bitrate a lot more than i have to lower it...)

cu

[Angelus]

Well I think that if you look at the Doom9 guide and more specifically the ReAuthorist part of it, it recommends the settings for the dvd size to be 4680000000 bytes..my guess is that you guys have tried the maximum 4704317440 bytes to do this. When I use the recommended value in ReAuthorist, after all the encoding and putting everything back into one ISO file, I usually get around 4.35 or 4.36 GB for my movies...the other 300 or so I think is made for the lead-in and lead-out...So I don't know where you guys ever get the 4,719,929,344 bytes after making the ISO

[downloada]

hi,

i can only speak for myself, but i never touched that setting. it was always set to 4680000000bytes, which worked fine until i started using numenu, but it's no big deal changing the bitrate a little before encoding, so it doesn't really bother me...

cu