DL Image With Imgburn Too Big

[Master Yoda]

I am trying to make a DL image, all the files come to 6.34GB but when i create a image with imgburn i get a iso which is 7.47GB. If i mount the new image and browse the disc the file's show up how they should but in my computer->details it shows the disc as the same as the image 7.47GB.

I have followed the guide in imgburns forum. I had "Don't update IFO/BUP files" ticked(due to the ifo's containing layerbreak info) and unticked but still to no effect.

Any ideas??

[r0lZ]

To place the layer break at the right position, it is often necessary to add a large padding area at the beginning of the DVD (usually between VIDEO_TS.IFO and VIDEO_TS.VOB or VIDEO_TS.BUP.)

Try to select another position for the LB, later in the DVD. Ideally, the LB should be in the middle of the DVD. And examine the output size in ImgBurn before creating the ISO, or use PgcEdit to select the LB position. It will display the number of sectors required in the padding area.

[Master Yoda]

I was using a position that imgburn said was excellent 50/50% but the padding was 592543, this time i tried another position that was excellent 60/40% but padding was only 13. Used that one and the iso is 6.34GB.

I ticked 'Don't update IFO/BUP files' as there are is already layerbreak information in the ifo's.

Thanks

[jinjin_jp]

I suppose image size become small if split cell at the half size of all files. (It is possibe by VobBlanker.)

Perhaps its last cell boundary is at about 2.61 GB from first of all files.
If so, L1=6.34-2.61=3.73GB and L0=2.61GB+padding.
It is need that L0>=L1, so L0=2.61+1.13(padding)=3.74GB.
So image size would be L0+L1=3.74+3.73=7.47GB.

If cell boundary is newly created at about 3.17GB, L0=3.17GB and L1=3.17GB, so image size would be about L0+L1=3.17+3.17=6.34GB.

Regard.

*I had much time to post, and it was too late. Sorry.

[r0lZ]

I ticked 'Don't update IFO/BUP files' as there are is already layerbreak information in the ifo's.IMO, if you specify the LB with ImgBurn, especially if it is different than the original position, you should let ImgBurn modify the IFO files.

[LIGHTNING UK!]

The whole purpose of 'padding' (beyond the normal 0 - 15 sectors to align on ECC boundary) is so that the cell you want as the LB one is valid whereby L0 >= L1 in size.

So if you pick an early cell that's before the midway point (of the file data - size wise), it has to pad it out some more (i.e. insert empty sectors somewhere in the file system between the files or whatever).

A disc with a 50/50 split is said to be the most compatible in readers.

As you have the whole disc to use for the files in question, I don't really get why you thought it was 'Too Big' ?! So long as the data you want on the disc is on the disc, it's really of no importance how the rest of the space is/isn't used.

If you don't fully understand what all the stuff on the LB dialog means and what it will do to the final image, you only have to ask and I'm sure someone in the know will explain it all to you :)

[Master Yoda]

I myself did'nt think it was too big, imgburn said it was but i don't believe that was the problem, had a duff disc. Put a new disc in and the image(6GB one) burnt fine

[LIGHTNING UK!]

Hmm well something's not right if build mode offered you a LB with so much padding applied to it that it meant the image was too big for the disc.

I'd be interested in the exact figures for the size of the image Vs the size of the disc if you're still able to get them.

But of course if it was just a dodgy disc that didn't report the correct size, that could mess things up.

[Master Yoda]

Well the first image i made was 7.47GB which should have fit a dl disc fine but i found it out to be a dodgy disc as i tried to burn a 360 backup on it which is 7.05GB and imgburn said the image was too big, popped in another disc and it burnt fine.

Anyways its sorted now and using the 60/40% layer break point that said 13 for padding work fine.

[blutach]

Remember, 50/50 will, in most cases, if the authoring is such that large padding is not required, leave room on the outside of the disk, which is still the most vulnerable place for errors.

Regards