Adds padding of 1.55GB to a DVD9?

[setarip_old]

I recently made a DVD9 backup of the R1 version of "I Am Legend".

Explorer indicated disc size 7.66Gb

Sum total of ALL files/contents 6.11GB

What would necessitate padding of 1.55GB?

[jinjin_jp]

Similar examples are reported in Japan from before.
Here is a certain example.
http://yaki2fan.hp.infoseek.co.jp/sub/br_fuguai.shtml
It is written is Japanese, but you will be able to know size and secters.
*disc size is 6.57GB.
*files size is 5.34GB.
The reason is ;
*start sector of VIDEO_TS.IFO is 646865. ---It is very big.

Regards.

[blutach]

It is simply a gap on the DVD. They don't have to be continguous and start exactly where the FS ends.

Regards

[setarip_old]

The question is "Why?":
What would necessitate padding of 1.55GB?

[r0lZ]

Because L0 and L1 must have the same size. I've explained that in another thread with much details. I think it is in the IFO/VOB Editors section. Use search.

[setarip_old]

@r0lZ

If I remember correctly, the requirement is "L0 >= L1".

So, if the actual DVD content is 6.11GB, can't burning programs simply burn 3.06Gb to L0 and 3.05Gb to L1?

Or is there an ADDITIONAL requirement that L0 must be FULL?

[blutach]

No, L0 must not be full (except on a DVD-R DL). They may wanna put the LB somewhere for aesthetic reasons, which mandates placement on the DVD that way.

Either you pick an LB at or near 50/50 or L1 is padded out so the disc is 50/50.

Regards

[setarip_old]

@r0lZ

Is LIGHTNING UK! saying something different than you, in the following post":

http://forum.doom9.org/showpost.php?p=892452&postcount=4

Initially, the program was basically saying that it couldn't move anything around (i.e. via padding) so that a cell lined up on an ECC block where L0 was still >= L1.

[jinjin_jp]

What size L0 and L1 each?
Layer-break is among of title, not in mid of title?
If it is about 2.4GB from first of all 6.11GB, L0=3.95(1.55+2.4)GB and L1=3.71(6.11-2.4)GB.
It can avoid pause during replaying the title, even if some players pause at Layer-break.
This is my guess, and might be wrong.

Regards.

Sorry, I mistook. First post was L0<L1. Now I corrected.

[r0lZ]

Exactly the same amount of data must be written on both layers. BUT, if L1 < L0, the drive is responsible of filling the remaining part of L1 with zeroes. That means that the burner program doesn't have to take care of that part of the process, and also that this part can be omitted from an ISO image.
And the method used by PgcEdit and ImgBurn allows to burn LESS data on L0, by offsetting them. However, in this case, the gap must explicitly be written by the burner program.
So, if we are speaking ONLY of the real data, contained in the IFO/BUP/VOB files, L0 > L1 is a myth. If you include the gaps and the padding zeroes, then L0 must be equal to L1.
Search the forum, There is a very long and technical thread about DL burning and the gaps, full of details! :search:

[setarip_old]

And 6.11GB/2=3.055GB for L0 - plus padding to bring it up to 4.37Gb.

I see...