Layer Break Problem in ImgBurn [Archive]

View Full Version : Layer Break Problem in ImgBurn

jinjin_jp

15th January 2006, 13:04

Some DVD have the problem like below, please help me.

Procedure
(1)Decrypting by DVDDecrypter file mode.
(2)Create ISO by PgcEdit0.6.3beta5 and ImgToolClassic0.91.7. then selected Layer.Br cell is same as original DVD.
___shown in Log "Layer break is at absolute sector 1992992. (Offset in L0 is 5.)"
(3)Burn by ImgBurn1.1.0.0, then setting of layer break is "Calculate Optimal".

Problem_1 : Layer.Br sector is incorrect.
__Layer 0 Sectors: 1,981,200 (50.08%).
__I think it must be 1,992,992.
__I examined 1,981,200 is among the cell(76) and boundary of VOBU(between 9219 and 9220).
__In Log of ImgBurn shown "Optimal L0 Data Zone Method: ECC Block Boundary, VOBU Boundary". It seems to be not CELL Boundary.
__When setting is "User Specified and 1992992", Layer.Br sector is correct.

Problem_2 : Can't display IFO Layer break information in ImgBurn.
__Message is "Failed to get layer break information from IFO data."
__I confirmed the same problem with 3 example (involve above).
__I think common characteristics of these 3 is that main movie is "multi-angle"&"multi-title"
____Example of only"multi-angle", only"multi-title", and "interleaved"&"multi-title" have no problem.
__I think it is related with Problem_1.

LIGHTNING UK!

16th January 2006, 12:35

Yeah, for some reason, ImgBurn was unable to locate the layer break within the IFO files.

Without some work on your part, I will be unable to fix that.
There must be something 'ever-so-slightly, not quite what I'm expecting' about that image.

I'm hoping to release 1.2.0.0 very soon and would like to get this fixed before I do so.

Basically, what I need from you is the first 5mb of the image file so I can see the filesystem, then I need the IFO that covers the sectors surrounding LBA 1,981,200 - 1,992,992.

I have a little tool for helping with the 5mb part.

You can get it from here:
http://forum.imgburn.com/index.php?s=&showtopic=485&view=findpost&p=6404

You just need to email those bits to me at the address in ImgBurn's 'About' box.

Thanks :)

jinjin_jp

16th January 2006, 16:04

Thanks very much for the help.
I would send the file that is part of ISO file.
But I can't use "grab5m", because I've never used "dos/command
prompt", so I cut out the file by other, but minimum size was 10MB.
If the file is useless, please tell me so, I will try to use "grab5m".

By the way, when setting "Calculate Optimal", error was occured at first, sand the second yme was suceeded.
Log is below... Anything releted?

I 00:29:16 ImgBurn Version 1.1.0.0 started!
I 00:29:17 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 1)
I 00:29:17 Initialising SPTI...
I 00:29:17 Searching for SCSI / ATAPI devices...
I 00:29:17 Found 1 DVD-ROM, 1 DVDｱRW and 1 DVD-RAM/RW!
I 00:33:15 Operation Started!
I 00:33:15 Source File: H:\DVD_Collection\ISO\********.lst
I 00:33:15 Source File Sectors: 3,956,366 (MODE1/2048)
I 00:33:15 Source File Size: 8,102,637,568 bytes
I 00:33:15 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 00:33:15 Source File Implementation Identifier: mkisofs
I 00:33:16 Destination Device: [0:0:0] PLEXTOR DVDR PX-716A 1.09 (K:) (1394)
I 00:33:16 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x)
I 00:33:16 Destination Media Sectors: 4,173,824
I 00:33:16 Write Mode: DVD
I 00:33:16 Write Type: DAO
I 00:33:16 Write Speed: MAX
I 00:33:16 Link Size: Auto
I 00:33:16 Test Mode: No
I 00:33:16 BURN-Proof: Enabled
I 00:33:16 Optimal L0 Data Zone Capacity: 1,981,200
I 00:33:16 Optimal L0 Data Zone Method: ECC Block Boundary, VOBU Boundary
I 00:33:16 Filling Buffer...
I 00:33:18 Writing LeadIn...
W 00:33:44 Failed to Write Sectors 32 - 63 - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (1 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (2 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (3 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (4 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (5 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (6 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (7 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (8 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (9 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (10 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (11 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (12 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (13 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (14 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (15 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (16 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (17 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (18 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (19 of 20)...
W 00:33:44 Retry Failed - Logical Unit is in process of becoming ready
W 00:33:44 Retrying (20 of 20)...
W 00:33:44 Retry Failed! - Logical Unit is in process of becoming ready
E 00:34:31 Failed to Write Sectors 32 - 63 - Logical Unit is in process of becoming ready
I 00:34:31 Synchronising Cache...
I 00:34:31 Closing Track...
I 00:34:31 Finalising Disc...
E 00:34:31 Failed to Write Image!
E 00:34:31 Operation Failed! - Duration: 00:01:15
I 00:34:31 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 25 KB/s (0.0x)
I 00:37:04 Operation Started!
I 00:37:04 Source File: H:\DVD_Collection\ISO\********.MDS
I 00:37:04 Source File Sectors: 3,956,366 (MODE1/2048)
I 00:37:04 Source File Size: 8,102,637,568 bytes
I 00:37:04 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 00:37:04 Source File Implementation Identifier: mkisofs
I 00:37:04 Destination Device: [0:0:0] PLEXTOR DVDR PX-716A 1.09 (K:) (1394)
I 00:37:04 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x)
I 00:37:04 Destination Media Sectors: 4,173,824
I 00:37:04 Write Mode: DVD
I 00:37:04 Write Type: DAO
I 00:37:04 Write Speed: MAX
I 00:37:04 Link Size: Auto
I 00:37:04 Test Mode: No
I 00:37:04 BURN-Proof: Enabled
I 00:37:04 Optimal L0 Data Zone Capacity: 1,981,200
I 00:37:04 Optimal L0 Data Zone Method: ECC Block Boundary, VOBU Boundary
I 00:37:04 Filling Buffer...
I 00:37:05 Writing LeadIn...
I 00:37:51 Writing Image...
I 00:37:51 Writing Layer 0... (LBA: 0 - 1981199)
I 00:45:59 Writing Layer 1... (LBA: 1981200 - 3956365)
I 00:54:10 Synchronising Cache...
I 00:54:14 Closing Track...
I 00:54:16 Finalising Disc...
I 00:54:51 Operation Successfully Completed! - Duration: 00:17:45
I 00:54:51 Average Write Rate: 8,090 KB/s (5.8x) - Maximum Write Rate: 8,380 KB/s (6.1x)
------------------------------------------------------------------------

LIGHTNING UK!

16th January 2006, 18:31

Ah thanks for the chunk of ISO.

I've found the problem and have now fixed it.

Basically, it was only reading upto VTS_09_1.VOB (file 39) from within the UDF filesystem - the files after that were not seen to exist and so program logic was preventing it from finding layer break positions in those files.

That initial problem you have of 'logical until in process of becoming ready' is probably from a bus reset or a drive reset. It should be nothing to do with the layer break. That's the status returned by the drive when it's busy initialising the disc.

Had you have given it a bit of time after that final (number 20) automatic retry, and then hit 'Retry' yourself (rather than cancel), it probably would have worked. Never mind though, it obviously worked the second time around.

jinjin_jp

16th January 2006, 22:59

Thanks very much. I wait for the fixed version in the looking forward to.

About 'logical until in process of becoming ready' , is it related the function of the drive?
Plextor drive has the function of AutoStrategy.
It seems to be write in the OPC area and evalulete at first step of writing.

LIGHTNING UK!

16th January 2006, 23:36

This is something it's doing in error.

I've never known a drive to become 'not ready' (unless you've removed the disc!) except for when there is some form of reset - either internally within the drive due to some error, or a bus reset where the OS/driver has decided it's needed in order to clear some sort of error.

Either way, it shouldn't happen and it's certainly not a good sign that it is!

Am I to assume there is no way for you to make your drive an internal one? You'd probably find IDE more reliable than firewire.

jinjin_jp

17th January 2006, 11:40

Thanks very much.
It seems to be no good.
I will continue to check with attention when burning.

r0lZ

17th January 2006, 13:54

Basically, it was only reading upto VTS_09_1.VOB (file 39) from within the UDF filesystem - the files after that were not seen to exist and so program logic was preventing it from finding layer break positions in those files.LUK!, could you describe this problem? Is it something related to the numbering of the IFOs?
Is it possible that the problem reported by Tobi here (http://forum.doom9.org/showthread.php?p=769157#post769157) has the same origin?

LIGHTNING UK!

17th January 2006, 14:15

No, it's unrelated to his problem. The above problem is just for when my program parses the filesystem / IFO's (which it's not doing when you pass the LB via CLI).

Your program is passing that LB value and it would appear it's wrong - as it should always match the 'fixed' L0 data zone capacity.

r0lZ

17th January 2006, 16:36

OK. Thanks. My bug is fixed, too. Will release PgcEdit 0.6.3 soon.

jinjin_jp

22nd February 2006, 22:51

LIGHTNING UK!

22nd February 2006, 23:09

Blimey, that was some quick testing on your part!

Glad the problem has been solved :)