L0 Data Zone Capacity Miscompare

[Clavius]

Hi,

 

I did a search on this, but the only two topics which came up had something to do with build-mode and 32k-padding.

But I got this warnings with an image which was created by "an other tool" from LUK.

 

W 11:39:21 L0 Data Zone Capacity Miscompare!

W 11:39:21 Wanted: 1605369, Got: 1605376

 

I burned dozens of images before, and a few after this one, without this warning.

This image, I burned twice to see if it was a reproducible warning (it was!).

Verify went ok, and I even did a file by file compare with the image contents and the burned disc.

 

So I wonder if I have something to worry about?

 

 

 

I 11:38:23 ImgBurn Version 2.1.0.0 started!

I 11:38:23 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

W 11:38:23 Drive D:\ (FAT32) does not support single files > 4 GB

W 11:38:23 Drive E:\ (FAT32) does not support single files > 4 GB

I 11:38:23 Initialising SPTI...

I 11:38:23 Searching for SCSI / ATAPI devices...

I 11:38:23 Found 1 CD-RW, 2 DVD-ROMs and 1 DVD?RW!

W 11:38:57 Program 'Debug Mode' has been Enabled!

I 11:39:21 Operation Started!

I 11:39:21 Source File: G:\TEST.MDS

I 11:39:21 Source File Sectors: 2.719.811 (MODE1/2048)

I 11:39:21 Source File Size: 5.570.172.928 bytes

I 11:39:21 Source File Volume Identifier: TEST

I 11:39:21 Source File Implementation Identifier: UDF Toshiba DVD Video

I 11:39:21 Source File File System(s): ISO9660; UDF (1,02)

I 11:39:21 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

I 11:39:21 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

I 11:39:21 Destination Media Sectors: 4.173.824

I 11:39:21 Write Mode: DVD

I 11:39:21 Write Type: DAO

I 11:39:21 Write Speed: 2,4x

I 11:39:21 Link Size: Auto

I 11:39:21 Test Mode: No

I 11:39:21 BURN-Proof: Enabled

I 11:39:21 Optimal L0 Data Zone Capacity: 1.605.369

I 11:39:21 Optimal L0 Data Zone Method: Copied From Original Disc

W 11:39:21 L0 Data Zone Capacity Miscompare!

W 11:39:21 Wanted: 1605369, Got: 1605376

D 11:39:35 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

D 11:39:35 Device Buffer Size: 6.291.456 bytes.

D 11:39:35 Device Buffer Available: 6.291.456 bytes.

I 11:39:35 Filling Buffer...

I 11:39:45 Writing LeadIn...

I 11:40:26 Writing Image...

I 11:40:26 Writing Layer 0... (LBA: 0 - 1605368)

I 11:56:51 Writing Layer 1... (LBA: 1605369 - 2719810)

I 12:08:18 Synchronising Cache...

I 12:08:22 Closing Track...

I 12:08:23 Finalising Disc...

I 12:14:17 Image MD5: 9616e32cb4bedcfc9c8e91b57bec4725

I 12:14:20 Exporting Graph Data...

I 12:14:20 Graph Data File: G:\TEST_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

I 12:14:20 Export Successfully Completed!

I 12:14:20 Operation Successfully Completed! - Duration: 00:34:56

I 12:14:20 Average Write Rate: 3.255 KB/s (2.4x) - Maximum Write Rate: 3.360 KB/s (2.4x)

I 12:14:20 Cycling Tray before Verify...

I 12:14:56 Device Ready!

I 12:14:59 Operation Started!

I 12:14:59 Source Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

I 12:14:59 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

I 12:14:59 Image File: G:\TEST.MDS

I 12:14:59 Image File Sectors: 2.719.811 (MODE1/2048)

I 12:14:59 Image File Size: 5.570.172.928 bytes

I 12:14:59 Image File Volume Identifier: TEST

I 12:14:59 Image File Implementation Identifier: UDF Toshiba DVD Video

I 12:14:59 Image File File System(s): ISO9660; UDF (1,02)

D 12:14:59 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

I 12:15:00 Verifying Sectors...

I 12:26:58 Device MD5: 9616e32cb4bedcfc9c8e91b57bec4725

I 12:26:58 Device (Padded) MD5: 6710682da3585f76b07e08b2517c95b2

I 12:26:58 Image MD5: 9616e32cb4bedcfc9c8e91b57bec4725

I 12:26:59 Exporting Graph Data...

I 12:26:59 Graph Data File: G:\TEST_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

I 12:26:59 Export Successfully Completed!

I 12:26:59 Operation Successfully Completed! - Duration: 00:11:59

I 12:26:59 Average Verify Rate: 7.576 KB/s (5.5x) - Maximum Verify Rate: 10.134 KB/s (7.3x)

I 12:43:05 Close Request Acknowledged

I 12:43:05 Closing Down...

I 12:43:05 Shutting down SPTI...

I 12:43:05 ImgBurn closed!

[LIGHTNING UK!]

1.605.369 is not a valid LB address. It must be a multiple of 16.

 

All that's happened there is that I've told the drive to use 1.605.369 (as taken from the MDS) and it's rounded it up to the nearest 16.

 

So the layerbreak point *could* be wrong if you IFO files etc were aligned with 1.605.369.

[Clavius]

The disc seems to play fine in both WinDVD and my standalone.

 

But is there nothing I can do to fix this, and not having this warning when burning this image?

 

And,

 

is there a way to check if the layerbreak point is wrong? I have both IfoEdit and PgcEdit installed, but I don't know where to look.

[LIGHTNING UK!]

You'd need to go back to the original source disc and try to figure out why the layerbreak position was read as being what's stated there - i.e. 1.605.369, in the first place!

 

To see what the IFO layerbreak position is, just click tools -> iso -> display ifo layer break.

[Clavius]

You meant the original source _image_, right?

 

 

???

[LIGHTNING UK!]

Nope, I meant 'disc', not 'image'.

 

I find it weird that the MDS file contains an invalid LB address. So you need to load the original disc again and see exactly where it thinks the physical media layer break is. It's the last couple of lines in the info panel on the right within ImgBurn.

 

The LB addresses from the IFO are nothing like the MDS one so something is very messed up!

[blutach]

In theory, the LB should be at an ECC boundary - that's where the multiple of 16 comes in. However, who knows how studios master their DVDs these days! I have seen some shockers recently that are obviously out of spec but released on an unsuspecting public.

 

If you have a direct ISO copy of what's on the source, then there's nothing you can do (if you want a direct ISO to burn methodology) - except be happy that ImgBurn has adjusted the L0 zone for you. In the future, I'd start off by having files, not an ISO.

 

Regards

[Clavius]

Nope, I meant 'disc', not 'image'.

I was just confused, because "tools -> iso -> display ifo layer break" only works for images, correct?

 

It's the last couple of lines in the info panel on the right within ImgBurn.

Here it is:

----------Original Disc:

Current Profile: DVD-ROM

Sectors: 2.719.811

Size: 5.570.172.928 bytes

Track Path: Parallel Track Path (PTP)

First Physical Sector of Data Area: 196.608

Last Physical Sector of Data Area: 1.801.976

Last Physical Sector in Layer 0: 0

Layer 0 Sectors: 1.605.369 (59,03%)

Layer 1 Sectors: 1.114.442 (40,97%)

----------Burned Disc:

Current Profile: DVD+R DL

Sectors: 2.719.824

Size: 5.570.199.552 bytes

Track Path: Opposite Track Path (OTP)

First Physical Sector of Data Area: 196.608

Last Physical Sector of Data Area: 16.089.679

Last Physical Sector in Layer 0: 1.801.983

Layer 0 Sectors: 1.605.376 (59,02%)

Layer 1 Sectors: 1.114.448 (40,98%)

 

Maybe this is something: The original disc is the second disc from a 5-year-old 4-DVD-set.

The 3 other discs all have

Track Path: Opposite Track Path (OTP)

but this one has

Track Path: Parallel Track Path (PTP)!

I think I read somewhere that OTP is mandatory for video-DVDs?

 

 

However, who knows how studios master their DVDs these days!

It's about 5 years old.

 

except be happy that ImgBurn has adjusted the L0 zone for you.

Of course I am!

 

In the future, I'd start off by having files, not an ISO.

In the past I did so, using PgcEdit to make the image and ImgBurn to burn.

But I hated it to make decisions about the layerbreak position. Especially one time, when I had a DVD with multiple angles, and I did not know which one to chose.

Also, I'm some sort of a neurotic perfectionist and like to have everything as close as possible to the original.

And until now this was the only occurrence of this error ever since I practise the "direct ISO to burn methodology".

Are there any other disadvantages?

 

Clavius

[blutach]

Well, in file mode, you can edit the heck out of a DVD (if you want to).

 

Up to you, of course.

 

Regards

[LIGHTNING UK!]

lol well as far as that disc goes, you'd actually get a better image if you rebuilt it using 'Build' mode.

 

At least then the IFO and Physical layer breaks could/would match!

[Clavius]

So was I right then with the track path stuff?

 

I mean, that video-DVDs must be OTP, and that they did a mastering error on that one by mastering it PTP?

 

Thanks a lot

Clavius

[LIGHTNING UK!]

No, it just depends on the type of disc it's mastered onto.

 

All DVD+R DL / DVD-R DL discs we can buy are OTP.

 

That's not really the problem here though.

 

Sometimes, PTP discs can have L0

 

The problem here is that the layerbreak position isn't on an LBA divisible by 16. That's not possible/acceptable according to the specs so I don't really know how they did it!

 

Even with rounding up, it still doesn't match any IFO LB position, hence why you'd be better off redoing the image.

[Clavius]

OK, I guess I should really consider rebuilding this one.

 

At the latest when I experience problems with it in a player.

 

Thank You very much, once again!

 

Clavius

[blutach]

This non multiple of 16 is, by the way, one of Ner0's greatest flaws. It just packs the files in there, as closely as possible. It's a wonder how any DL disks turn out OK using Ner0. Beats me why people actually pay for it.

 

Regards