Jump to content

DVD+R DL won't play second layer


morgabo

Recommended Posts

Hi everyone-

 

Having a bear of a time getting a DVD+R DL to play its second layer in either my PS3 or my Mac. I'm using Verbatim disks, and have followed the instructions from the "burn avchd disks with Imgburn" guide at afterdawn.

 

I've also hunted around for other guides, and methods, to no avail. Spent about 8 hours yesterday and three disks trying to get it to work. My files are about 8.45 gb, set up in BDMV and Certificate folders. When I press the calculate function in Imgburn, everything sets up to UDF 2.5, etc, and going through the steps avails me a burn that takes about 45 minutes at 2.4x, with no errors. The log shows both layers (0 and 1) being written, "All Ok", and the disk ejects. This is the same for two different movie projects I tried to do yesterday, so I know the error is not particular to one project's setup.

 

When I put the disc in my PS3, the first half plays beautifully. I can seek back and forth until I reach the halfway point, where it should be switching layers. At that point, it locks up/goes black and the PS3 says "invalid disk". Putting the disk back into my MacBook pro, I tried playing it with VLC media player. In this case too, scrubbing past the halfway point gets me a blank screen.

 

In all my attempts, I've never been able to get the layer break screen to pop up in Imgburn, to manually select where the break is happening, so I wonder if it even is happening at all. Other guides say it will come up twice during the burn setup, but it never has for me.

 

I've also tried creating an iso from my folders and burning that. Same thing happens- all OK according to Imgburn, but nothing doing for the second layer.

 

Any help is greatly appreciated! Thanks.

Link to comment
Share on other sites

The layer break stuff is for DVD Video. You won't see it at any other time.

 

If you aren't already doing so (and I guess you're not), make sure ImgBurn is set to Verify after it burns.

 

Once you've done that, burn another disc (and verify it) and then post a log so we can see what's going on. (as per the pink box up the top :chair: )

Link to comment
Share on other sites

Here is the log... I'm on an iPhone, so forgive the formatting.

 

 

I 22:28:12 ImgBurn Version 2.5.5.0 started!

I 22:28:12 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)

I 22:28:12 Total Physical Memory: 2,858,764 KB  -  Available: 2,468,636 KB

I 22:28:12 Initialising SPTI...

I 22:28:12 Searching for SCSI / ATAPI devices...

I 22:28:12 -> Drive 1 - Info: DTSOFT BDROM 1.05 (E:) (Virtual)

I 22:28:12 -> Drive 2 - Info: MATSHITA DVD-R   UJ-868 KB19 (D:) (ATA)

I 22:28:12 Found 1 DVD±RW and 1 BD-ROM!

I 22:28:27 Operation Started!

I 22:28:27 Building Image Tree...

I 22:28:27 Calculating Totals...

I 22:28:27 Preparing Image...

I 22:28:27 Contents: 10 Files, 14 Folders

I 22:28:27 Content Type: BD Video

I 22:28:27 Data Type: MODE1/2048

I 22:28:27 File System(s): UDF (2.50)

I 22:28:27 Volume Label: [Not Configured]

I 22:28:27 Size: 8,464,023,416 bytes

I 22:28:27 Sectors: 4,132,831

I 22:28:27 Image Size: 8,464,891,904 bytes

I 22:28:27 Image Sectors: 4,133,248

I 22:28:27 Operation Successfully Completed! - Duration: 00:00:00

I 22:29:26 Operation Started!

I 22:29:26 Building Image Tree...

I 22:33:12 Calculating Totals...

I 22:33:12 Preparing Image...

I 22:33:12 Contents: 10 Files, 14 Folders

I 22:33:12 Content Type: BD Video

I 22:33:12 Data Type: MODE1/2048

I 22:33:12 File System(s): UDF (2.50)

I 22:33:12 Volume Label: ESB Despecialized Edition

I 22:33:12 Size: 8,464,023,416 bytes

I 22:33:12 Sectors: 4,132,831

I 22:33:12 Image Size: 8,464,891,904 bytes

I 22:33:12 Image Sectors: 4,133,248

I 22:33:18 Operation Successfully Completed! - Duration: 00:03:51

I 22:33:18 Operation Started!

I 22:33:18 Source File: -==/\/[bUILD IMAGE]\/\==-

I 22:33:18 Source File Sectors: 4,133,248 (MODE1/2048)

I 22:33:18 Source File Size: 8,464,891,904 bytes

I 22:33:18 Source File Volume Identifier: ESB Despecialized Edition

I 22:33:18 Source File Volume Set Identifier: 3F35B3AD003F112F

I 22:33:18 Source File Application Identifier: ImgBurn v2.5.5.0

I 22:33:18 Source File Implementation Identifier: ImgBurn

I 22:33:18 Source File File System(s): UDF (2.50)

I 22:33:18 Destination Device: [1:0:0] MATSHITA DVD-R   UJ-868 KB19 (D:) (ATA)

I 22:33:18 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2.4x, 4x)

I 22:33:18 Destination Media Sectors: 4,173,824

I 22:33:18 Write Mode: DVD

I 22:33:18 Write Type: DAO

I 22:33:18 Write Speed: 2.4x

I 22:33:18 Link Size: Auto

I 22:33:18 Lock Volume: Yes

I 22:33:18 Test Mode: No

I 22:33:18 OPC: No

I 22:33:18 BURN-Proof: Enabled

I 22:33:18 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x)

I 22:33:18 Optimal L0 Data Zone Capacity: 2,066,624

I 22:33:18 Optimal L0 Data Zone Method: ECC Block Boundary

I 22:33:47 Set L0 Data Zone Capacity Succeeded!

I 22:33:48 Filling Buffer... (40 MB)

I 22:33:49 Writing LeadIn...

I 22:33:51 Writing Session 1 of 1... (1 Track, LBA: 0 - 4133247)

I 22:33:51 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4133247)

I 22:33:51 Writing Layer 0... (LBA: 0 - 2066623)

I 22:55:31 Writing Layer 1... (LBA: 2066624 - 4133247)

I 23:17:09 Synchronising Cache...

I 23:17:14 Closing Track...

I 23:17:15 Finalising Disc...

I 23:18:26 Exporting Graph Data...

I 23:18:26 Graph Data File: C:\Documents and Settings\Case\Application Data\ImgBurn\Graph Data Files\MATSHITA_DVD-R_UJ-868_KB19_WEDNESDAY-SEPTEMBER-21-2011_10-33_PM_MKM-003-00_2.4x.ibg

I 23:18:26 Export Successfully Completed!

I 23:18:26 Operation Successfully Completed! - Duration: 00:45:07

I 23:18:26 Average Write Rate: 3,181 KB/s (2.3x) - Maximum Write Rate: 3,570 KB/s (2.6x)

I 23:18:26 Cycling Tray before Verify...

W 23:18:53 Waiting for device to become ready...

I 23:19:18 Device Ready!

I 23:19:21 Operation Started!

I 23:19:21 Source Device: [1:0:0] MATSHITA DVD-R   UJ-868 KB19 (D:) (ATA)

I 23:19:21 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-003-00) (Speeds: 2.4x, 4x)

I 23:19:21 Image File: -==/\/[bUILD IMAGE]\/\==-

I 23:19:21 Image File Sectors: 4,133,248 (MODE1/2048)

I 23:19:21 Image File Size: 8,464,891,904 bytes

I 23:19:21 Image File Volume Identifier: ESB Despecialized Edition

I 23:19:21 Image File Volume Set Identifier: 3F35B3AD003F112F

I 23:19:21 Image File Application Identifier: ImgBurn v2.5.5.0

I 23:19:21 Image File Implementation Identifier: ImgBurn

I 23:19:21 Image File File System(s): UDF (2.50)

I 23:19:21 Read Speed (Data/Audio): MAX / MAX

I 23:19:21 Verifying Session 1 of 1... (1 Track, LBA: 0 - 4133247)

I 23:19:21 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 4133247)

I 23:19:21 Verifying Layer 0... (LBA: 0 - 2066623)

I 23:31:11 Verifying Layer 1... (LBA: 2066624 - 4133247)

I 23:42:56 Exporting Graph Data...

I 23:42:56 Graph Data File: C:\Documents and Settings\Case\Application Data\ImgBurn\Graph Data Files\MATSHITA_DVD-R_UJ-868_KB19_WEDNESDAY-SEPTEMBER-21-2011_10-33_PM_MKM-003-00_2.4x.ibg

I 23:42:56 Export Successfully Completed!

I 23:42:56 Operation Successfully Completed! - Duration: 00:23:35

I 23:42:56 Average Verify Rate: 5,842 KB/s (4.2x) - Maximum Verify Rate: 8,533 KB/s (6.2x)

Link to comment
Share on other sites

Sometimes it's just due to the folder structure being used - something it doesn't like about it.

 

Other times it could be due to the booktype being used - and you can't change that on your drive, it's always set to DVD-ROM.

 

EDIT: Oh but sorry, your PS3 does play it... just stops at what you're assuming is the LB point.

 

Maybe the drive is doing a shocking job of burning the disc and the PS3 drive can't read it.

 

I have no faith in slimline drives, especially matshita ones.

Link to comment
Share on other sites

Sometimes it's just due to the folder structure being used - something it doesn't like about it.

 

Other times it could be due to the booktype being used - and you can't change that on your drive, it's always set to DVD-ROM.

 

EDIT: Oh but sorry, your PS3 does play it... just stops at what you're assuming is the LB point.

 

Maybe the drive is doing a shocking job of burning the disc and the PS3 drive can't read it.

 

I have no faith in slimline drives, especially matshita ones.

 

I thought it might be the drive, but having burned four or five copies at this point, they all stop at exactly the same time code point each time. The consistency doesn't lead me to believe that the drive is doing a bad job of burning the disc... It's probably the folder structure, as you mention. Someone on another forum wrote in that adding PS3_udate and PS3_vprm folders in his root fixed his issues, so maybe I'll try that.

Link to comment
Share on other sites

I doubt the folder structure would cause an issue like that.

 

It would just stop the machine from playing the disc at all.

 

Have you only been burning the same thing over and over again? Maybe it's a glitch in the file.

 

Of course if you've only been burning the same stuff over and over again, the LB would be in the same place too - so if the burn quality at the start of L1 is really low (which is usually the case), it would make it get stuck.

Link to comment
Share on other sites

I've been burning two different files, several times each. Sometimes in ISOs, sometimes just as AVCHD folders to the disc... Last night I tried just burning the mt2s file straight to the disc as data with no AVCHD folders, as the PS3 can play that. I popped it into the PS3, and it did a similar thing- it only listed the movie as 59 minutes long, and when it got to the end of that time (exactly half of my movie), it just locked up, so I had to eject the disc.

 

As I'm on a Mac, running XP so that I could use Imgburn, I finally booted back into OSX and tried doing the same thing (burning a UDF data disc of just the mt2s) with the open-source Burn program. Lo and behold, the PS3 recognized it and played it all perfectly. Since OSX doesn't have the ability to burn UDF 2.5 (So I heard) I had wanted to avoid just burning a data disc, but since it's the only thing that's worked for me, I'll take it!

 

Not sure if there's any more progress to be made, but perhaps it's just an issue with running XP on a Mac that caused the problem with Imgburn.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.