Jump to content

ImgBurn Support Forum uses cookies. Read the Privacy Policy for more info. To remove this message, please click the button to the right:    I accept the use of cookies

Photo

L-EC Uncorrectable when Verifying DVD+R DL


Forum Rules

Read the Guides forum if you don't know how to do something. :readbook:
If you have a question or a problem, check the FAQ and use the Search to see if you can find the answer for yourself. :lightbulb:
If you're having trouble burning double layer media, read Here.
Still stuck? Create a new thread and describe your issue in detail.
Make sure you include a copy of the program's log in your post. No log = :chair:


  • Please log in to reply
8 replies to this topic

#1 Sarlacc Pit

Sarlacc Pit

    ISF Newbie

  • Members
  • Pip
  • 3 posts

Posted 23 November 2017 - 06:22 AM

I'm in the last steps of figuring out Harmy's Despecialized Star Wars Trilogy, which recommends ImgBurn in getting the .iso files onto a disk. I've chosen the AVCHD version so as to fit them onto a DVD+R DL (I don't have the capacity to write Blu-ray). I was able to burn both Star Wars and Empire Strikes Back and successfully played them back in a Blu-ray player (stunning work by Harmáček), but with Return of the Jedi, it finishes burning and then the verification fails at 72%. I have had four failures with ROTJ now; two failed at 72%, one failed at 50% (layer break trouble?), and one simply ejected after burning even though the verify box was checked, and now makes ImgBurn hang at "Getting Media Status..." whenever it is inserted.

 

I'm at a loss as to what to do. The file for ROTJ includes a checksum, which it generated correctly, ruling out any problems with the iso. The first two disks in the Verbatim DVD+DL pack burned just fine, then four failures, which I can't make sense of. I remember reading a member's rule of thumb where three bad disks means the pack is bad. I'm not sure here. I wonder if trying to burn Star Wars or Empire Strikes Back again would succeed or fail. The most likely problem is the burner, hp CDDVDW TS-H653T H6D1, which I suspect is laughably irrelevant as I can't find a single mention of it here or on any other similar forum. But then how did it burn the first two films correctly? Beginner's luck? The firmware is updated to the most recent version released on June 21st, 2006. The Update Firmware function in ImgBurn takes me to Firmware HQ, where the search gives me mostly Samsung firmware. There are a few HP products, but none of the model numbers match.

 

Something that I feel I should mention as it was point #3 in the above Double Layer Disk troubleshooting post: These are x8 Verbatim disks. Both SW and ESB were written at x4 and worked. I've tried other burn speeds after having trouble with ROTJ and found that the program always defaults to x4 when writing, even if I specify x6 or x8.

 

I did not save the log from when the disc was originally written because I thought I would play around with the burn speeds first, but here is a failed verification of one of the 72% disks. If you would like me to burn another disk so as to have more information, I'd be happy to.

I 16:37:40 ImgBurn Version 2.5.8.0 started!
I 16:37:40 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)
I 16:37:40 Total Physical Memory: 6,195,744 KiB  -  Available: 2,544,096 KiB
I 16:37:40 Initialising SPTI...
I 16:37:40 Searching for SCSI / ATAPI devices...
I 16:37:42 -> Drive 1 - Info: hp CDDVDW TS-H653T H6D1 (E:) (ATAPI)
I 16:37:42 Found 1 DVD±RW/RAM!
I 20:27:41 Operation Started!
I 20:27:41 Source Device: [0:1:0] hp CDDVDW TS-H653T H6D1 (E:) (ATAPI)
I 20:27:41 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: CMC MAG-D03-64)
I 20:27:41 Source Media Supported Read Speeds: 4x, 6x, 8x, 12x
I 20:27:41 Source Media Supported Write Speeds: 4x, 6x, 8x
I 20:27:41 Source Media Sectors: 4,121,312 (Track Path: OTP - L0: 2,060,656 - L1: 2,060,656)
I 20:27:41 Source Media Size: 8,440,446,976 bytes
I 20:27:41 Image File: C:\Users\User\Desktop\Star Wars\Return of the Jedi AVCHD ISO\ROTJ v2.5 AVCHD\ROTJ_DESPECIALIZED_v2.5_AVCHD.mds
I 20:27:41 Image File Sectors: 4,121,312 (MODE1/2048)
I 20:27:41 Image File Size: 8,440,446,976 bytes
I 20:27:41 Image File Volume Identifier: ROTJ_DEED_v2.5
I 20:27:41 Image File Volume Set Identifier: 48479767003EE26D
I 20:27:41 Image File Application Identifier: ImgBurn v2.5.8.0
I 20:27:41 Image File Implementation Identifier: ImgBurn
I 20:27:41 Image File File System(s): UDF (2.50)
I 20:27:41 Read Speed (Data/Audio): MAX / MAX
I 20:27:42 Read Speed - Effective: 5x - 12x, 12x - 5x
I 20:27:43 Verifying Session 1 of 1... (1 Track, LBA: 0 - 4121311)
I 20:27:43 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 4121311)
I 20:27:43 Verifying Layer 0... (LBA: 0 - 2060655)
I 20:33:32 Verifying Layer 1... (LBA: 2060656 - 4121311)
W 20:37:03 Failed to Read Sectors 3007216 - 3007247 - Reason: L-EC Uncorrectable Error
W 20:37:13 Failed to Read Sector 3007233 - Reason: L-EC Uncorrectable Error
W 20:37:13 Sector 3007233 maps to File: \BDMV\STREAM\00000.m2ts
W 20:37:17 Retrying (1)...
W 20:37:26 Retry Failed - Reason: L-EC Uncorrectable Error
W 20:37:38 Failed to Read Sector 3007233 - Reason: L-EC Uncorrectable Error
W 20:37:38 Sector 3007233 maps to File: \BDMV\STREAM\00000.m2ts
W 20:37:47 Failed to Read Sector 3007234 - Reason: L-EC Uncorrectable Error
W 20:37:47 Sector 3007234 maps to File: \BDMV\STREAM\00000.m2ts
W 20:37:49 Retrying (1)...
W 20:37:58 Retry Failed - Reason: L-EC Uncorrectable Error
W 20:37:59 Retrying (2)...
W 20:38:08 Retry Failed - Reason: L-EC Uncorrectable Error
W 20:38:10 Failed to Read Sector 3007234 - Reason: L-EC Uncorrectable Error
W 20:38:10 Sector 3007234 maps to File: \BDMV\STREAM\00000.m2ts
W 20:38:19 Failed to Read Sector 3007235 - Reason: L-EC Uncorrectable Error
W 20:38:19 Sector 3007235 maps to File: \BDMV\STREAM\00000.m2ts
W 20:38:30 Failed to Read Sector 3007236 - Reason: L-EC Uncorrectable Error
W 20:38:30 Sector 3007236 maps to File: \BDMV\STREAM\00000.m2ts
W 20:38:49 Failed to Read Sector 3007237 - Reason: L-EC Uncorrectable Error
W 20:38:49 Sector 3007237 maps to File: \BDMV\STREAM\00000.m2ts
W 20:39:06 Failed to Read Sector 3007238 - Reason: L-EC Uncorrectable Error
W 20:39:06 Sector 3007238 maps to File: \BDMV\STREAM\00000.m2ts
W 20:39:15 Failed to Read Sector 3007239 - Reason: L-EC Uncorrectable Error
W 20:39:15 Sector 3007239 maps to File: \BDMV\STREAM\00000.m2ts
W 20:39:25 Failed to Read Sector 3007240 - Reason: L-EC Uncorrectable Error
W 20:39:25 Sector 3007240 maps to File: \BDMV\STREAM\00000.m2ts
W 20:39:34 Failed to Read Sector 3007241 - Reason: L-EC Uncorrectable Error
W 20:39:34 Sector 3007241 maps to File: \BDMV\STREAM\00000.m2ts
W 20:39:43 Failed to Read Sector 3007242 - Reason: L-EC Uncorrectable Error
W 20:39:43 Sector 3007242 maps to File: \BDMV\STREAM\00000.m2ts
W 20:39:53 Failed to Read Sector 3007243 - Reason: L-EC Uncorrectable Error
W 20:39:53 Sector 3007243 maps to File: \BDMV\STREAM\00000.m2ts
W 20:40:02 Failed to Read Sector 3007244 - Reason: L-EC Uncorrectable Error
W 20:40:03 Sector 3007244 maps to File: \BDMV\STREAM\00000.m2ts
I 20:40:09 Abort Request Acknowledged
W 20:40:12 Failed to Read Sector 3007245 - Reason: L-EC Uncorrectable Error
W 20:40:12 Sector 3007245 maps to File: \BDMV\STREAM\00000.m2ts
E 20:40:12 Failed to Verify Sectors!
I 20:40:13 Exporting Graph Data...
I 20:40:13 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\hp_CDDVDW_TS-H653T_H6D1_WEDNESDAY-NOVEMBER-22-2017_8-27_PM_CMC_MAG-D03-64.ibg
I 20:40:13 Export Successfully Completed!
E 20:40:13 Operation Aborted! - Duration: 00:12:31
I 20:40:13 Average Verify Rate: 8,073 KiB/s (6.0x) - Maximum Verify Rate: 16,805 KiB/s (12.4x)


#2 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,303 posts
  • Gender:Male
  • Location:United Kingdom

Posted 23 November 2017 - 06:37 AM

Your discs do not have the correct MKM-003-00 MID, so the double layer 'pinned' thread still applies.

The program saves the log by default. You can access it via the Help menu.
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!

#3 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,541 posts
  • Gender:Male

Posted 23 November 2017 - 03:08 PM

Yeah, it could be the CMC MAG DVD+R DL discs you're using.  CMC MAG is CMC Magnetics, the absolute bottom of the barrel optical disc manufacturer.  When it comes to DVD+R DL, the only really viable option is Verbatim DataLifePlus MKM kind.  Although I've had good results with TDK's DVD+R DL in the past, I still stick with Verbatim's.  NOT Verbatim's Life Series you find in brick and mortar stores.  They will be CMC.



#4 Sarlacc Pit

Sarlacc Pit

    ISF Newbie

  • Members
  • Pip
  • 3 posts

Posted 23 November 2017 - 04:42 PM

I see. I was a bit confused on that topic, I didn't know whether the ID in the pinned post labelled as "Dye" was a different thing than the MID. I simply assumed that since the packaging said x8 that I was using MKM-003-00. The post specified two types of Verbatim DVD+R DL, which I interpreted as there being only two types made by Verbatim, period. So, just to make absolutely sure, the way for me to purchase correctly would be to always look for "DataLife Plus" on the package?

 

As in, this is absolutely a waste of time since it's actually CMC MAG,

ABG9_131243343232311950P50rVkkufq.jpg

 

While this is the way to go?

17-130-269-03.jpg

I'm curious, what causes this to happen with the Verbatim brand? The pinned post emphasizes Verbatim and disparages CMC, RITEK, and RICOH, but I bought the first photo at a brick and mortar, which was CMC disks with the Verbatim name on it. Why would Verbatim risk their reputation by selling both low quality and high quality products under its name, with only a single trivial difference on the package that the layman wouldn't catch? Do they package any other kind of non-MKM disk? Is MKM another disk manufacturer that is a separate entity from Verbatim, like CMC is? Why doesn't Verbatim sell MKM in brick and mortar stores?

 

I suggest editing the pinned post to state that 1) the listed MKM numbers correspond to the MID that is shown in the program, and 2) that only Verbatim DataLife Plus is being recommended, not just any disk pack with the Verbatim name slapped on it. I think It would help the inexperienced such as myself. Did Verbatim only start packaging non-MKM disks after 2008?

 

Also, is my drive considered old enough to need the x2.4 disks (MKM-001-00)? Since I've actually had successful playback with two of the CMC MAG-D03-64, rated for x8, burning at x4 speed, I assume that if I get the MKM-003-00, that it will simply default to x4 again and succeed.

 

 

Thanks for telling me that logs are saved. Here's a full burn log of the 50% disk, just in case.

I 20:28:52 ImgBurn Version 2.5.8.0 started!
I 20:28:52 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)
I 20:28:52 Total Physical Memory: 6,195,744 KiB  -  Available: 1,394,080 KiB
I 20:28:52 Initialising SPTI...
I 20:28:52 Searching for SCSI / ATAPI devices...
I 20:28:52 -> Drive 1 - Info: hp CDDVDW TS-H653T H6D1 (E:) (ATAPI)
I 20:28:52 Found 1 DVD±RW/RAM!
I 20:35:58 Operation Started!
I 20:35:58 Source File: C:\Users\User\Desktop\Star Wars\Return of the Jedi AVCHD ISO\ROTJ v2.5 AVCHD\ROTJ_DESPECIALIZED_v2.5_AVCHD.mds
I 20:35:58 Source File Sectors: 4,121,312 (MODE1/2048)
I 20:35:58 Source File Size: 8,440,446,976 bytes
I 20:35:58 Source File Volume Identifier: ROTJ_DEED_v2.5
I 20:35:58 Source File Volume Set Identifier: 48479767003EE26D
I 20:35:58 Source File Application Identifier: ImgBurn v2.5.8.0
I 20:35:58 Source File Implementation Identifier: ImgBurn
I 20:35:58 Source File File System(s): UDF (2.50)
I 20:35:58 Destination Device: [0:1:0] hp CDDVDW TS-H653T H6D1 (E:) (ATAPI)
I 20:35:58 Destination Media Type: DVD+R DL (Disc ID: CMC MAG-D03-64)
I 20:35:58 Destination Media Supported Write Speeds: 4x, 6x, 8x
I 20:35:58 Destination Media Sectors: 4,173,824
I 20:35:58 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes)
I 20:35:58 Write Mode: DVD
I 20:35:58 Write Type: DAO
I 20:35:58 Write Speed: 6x
I 20:35:58 DVD+R DL Reserve Track: No
I 20:35:58 Link Size: Auto
I 20:35:58 Lock Volume: Yes
I 20:35:58 Test Mode: No
I 20:35:58 OPC: No
I 20:35:58 BURN-Proof: Enabled
I 20:35:58 Write Speed Successfully Set! - Effective: 8,310 KB/s (6x)
I 20:35:58 Optimal L0 Data Zone Capacity: 2,060,656
I 20:35:58 Optimal L0 Data Zone Method: ECC Block Boundary
I 20:36:40 Set L0 Data Zone Capacity Succeeded!
I 20:36:40 L0 Data Zone Capacity - Effective: 2,060,656
I 20:36:42 Filling Buffer... (80 MiB)
I 20:36:44 Writing LeadIn...
I 20:37:01 Writing Session 1 of 1... (1 Track, LBA: 0 - 4121311)
I 20:37:01 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4121311)
I 20:37:01 Writing Layer 0... (LBA: 0 - 2060655)
I 20:47:01 Writing Layer 1... (LBA: 2060656 - 4121311)
I 20:59:37 Synchronising Cache...
I 20:59:47 Closing Track...
I 20:59:49 Finalising Disc...
I 21:00:40 Exporting Graph Data...
I 21:00:40 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\hp_CDDVDW_TS-H653T_H6D1_MONDAY-NOVEMBER-20-2017_8-35_PM_CMC_MAG-D03-64_6x.ibg
I 21:00:40 Export Successfully Completed!
I 21:00:40 Operation Successfully Completed! - Duration: 00:24:42
I 21:00:40 Average Write Rate: 6,078 KiB/s (4.5x) - Maximum Write Rate: 8,229 KiB/s (6.1x)
I 21:00:40 Cycling Tray before Verify...
W 21:00:47 Waiting for device to become ready...
I 21:00:59 Device Ready!
I 21:01:09 Operation Started!
I 21:01:09 Source Device: [0:1:0] hp CDDVDW TS-H653T H6D1 (E:) (ATAPI)
I 21:01:09 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: CMC MAG-D03-64)
I 21:01:09 Source Media Supported Read Speeds: 4x, 6x, 8x, 12x
I 21:01:09 Source Media Supported Write Speeds: 4x, 6x, 8x
I 21:01:09 Source Media Sectors: 4,121,312 (Track Path: OTP - L0: 2,060,656 - L1: 2,060,656)
I 21:01:09 Source Media Size: 8,440,446,976 bytes
I 21:01:09 Image File: C:\Users\User\Desktop\Star Wars\Return of the Jedi AVCHD ISO\ROTJ v2.5 AVCHD\ROTJ_DESPECIALIZED_v2.5_AVCHD.mds
I 21:01:09 Image File Sectors: 4,121,312 (MODE1/2048)
I 21:01:09 Image File Size: 8,440,446,976 bytes
I 21:01:09 Image File Volume Identifier: ROTJ_DEED_v2.5
I 21:01:09 Image File Volume Set Identifier: 48479767003EE26D
I 21:01:09 Image File Application Identifier: ImgBurn v2.5.8.0
I 21:01:09 Image File Implementation Identifier: ImgBurn
I 21:01:09 Image File File System(s): UDF (2.50)
I 21:01:09 Read Speed (Data/Audio): MAX / MAX
I 21:01:10 Read Speed - Effective: 5x - 12x, 12x - 5x
I 21:01:10 Verifying Session 1 of 1... (1 Track, LBA: 0 - 4121311)
I 21:01:10 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 4121311)
I 21:01:10 Verifying Layer 0... (LBA: 0 - 2060655)
I 21:07:08 Verifying Layer 1... (LBA: 2060656 - 4121311)
W 21:07:41 Failed to Read Sectors 2099216 - 2099247 - Reason: L-EC Uncorrectable Error
W 21:07:51 Failed to Read Sector 2099235 - Reason: L-EC Uncorrectable Error
W 21:07:51 Sector 2099235 maps to File: \BDMV\STREAM\00000.m2ts
W 21:08:10 Retrying (1)...
W 21:08:20 Retry Failed - Reason: L-EC Uncorrectable Error
W 21:08:24 Retrying (2)...
W 21:08:33 Retry Failed - Reason: L-EC Uncorrectable Error
W 21:08:36 Failed to Read Sector 2099235 - Reason: L-EC Uncorrectable Error
W 21:08:37 Sector 2099235 maps to File: \BDMV\STREAM\00000.m2ts
W 21:08:46 Failed to Read Sector 2099236 - Reason: L-EC Uncorrectable Error
W 21:08:46 Sector 2099236 maps to File: \BDMV\STREAM\00000.m2ts
W 21:13:15 Failed to Read Sector 2099237 - Reason: L-EC Uncorrectable Error
W 21:13:15 Sector 2099237 maps to File: \BDMV\STREAM\00000.m2ts
W 21:13:26 Failed to Read Sector 2099238 - Reason: L-EC Uncorrectable Error
W 21:13:26 Sector 2099238 maps to File: \BDMV\STREAM\00000.m2ts
W 21:14:03 Failed to Read Sector 2099239 - Reason: L-EC Uncorrectable Error
W 21:14:03 Sector 2099239 maps to File: \BDMV\STREAM\00000.m2ts
W 21:14:21 Failed to Read Sector 2099240 - Reason: L-EC Uncorrectable Error
W 21:14:21 Sector 2099240 maps to File: \BDMV\STREAM\00000.m2ts
W 21:14:30 Failed to Read Sector 2099241 - Reason: L-EC Uncorrectable Error
W 21:14:30 Sector 2099241 maps to File: \BDMV\STREAM\00000.m2ts
W 21:14:40 Failed to Read Sector 2099242 - Reason: L-EC Uncorrectable Error
W 21:14:40 Sector 2099242 maps to File: \BDMV\STREAM\00000.m2ts
W 21:14:49 Failed to Read Sector 2099243 - Reason: L-EC Uncorrectable Error
W 21:14:49 Sector 2099243 maps to File: \BDMV\STREAM\00000.m2ts
W 21:14:59 Failed to Read Sector 2099244 - Reason: L-EC Uncorrectable Error
W 21:14:59 Sector 2099244 maps to File: \BDMV\STREAM\00000.m2ts
W 21:15:09 Failed to Read Sector 2099245 - Reason: L-EC Uncorrectable Error
W 21:15:09 Sector 2099245 maps to File: \BDMV\STREAM\00000.m2ts
W 21:15:18 Failed to Read Sector 2099246 - Reason: L-EC Uncorrectable Error
W 21:15:18 Sector 2099246 maps to File: \BDMV\STREAM\00000.m2ts
W 21:15:28 Failed to Read Sector 2099247 - Reason: L-EC Uncorrectable Error
W 21:15:28 Sector 2099247 maps to File: \BDMV\STREAM\00000.m2ts
W 21:15:57 Failed to Read Sector 2099298 - Reason: L-EC Uncorrectable Error
W 21:15:57 Sector 2099298 maps to File: \BDMV\STREAM\00000.m2ts
W 21:16:07 Failed to Read Sector 2099299 - Reason: L-EC Uncorrectable Error
W 21:16:07 Sector 2099299 maps to File: \BDMV\STREAM\00000.m2ts
W 21:16:16 Failed to Read Sector 2099300 - Reason: L-EC Uncorrectable Error
W 21:16:16 Sector 2099300 maps to File: \BDMV\STREAM\00000.m2ts
W 21:16:26 Failed to Read Sector 2099301 - Reason: L-EC Uncorrectable Error
W 21:16:26 Sector 2099301 maps to File: \BDMV\STREAM\00000.m2ts
W 21:16:36 Failed to Read Sector 2099302 - Reason: L-EC Uncorrectable Error
W 21:16:36 Sector 2099302 maps to File: \BDMV\STREAM\00000.m2ts
W 21:16:46 Failed to Read Sector 2099303 - Reason: L-EC Uncorrectable Error
W 21:16:46 Sector 2099303 maps to File: \BDMV\STREAM\00000.m2ts
W 21:16:56 Failed to Read Sector 2099304 - Reason: L-EC Uncorrectable Error
W 21:16:56 Sector 2099304 maps to File: \BDMV\STREAM\00000.m2ts
W 21:17:05 Failed to Read Sector 2099305 - Reason: L-EC Uncorrectable Error
W 21:17:05 Sector 2099305 maps to File: \BDMV\STREAM\00000.m2ts
I 21:17:13 Abort Request Acknowledged
W 21:17:15 Failed to Read Sector 2099306 - Reason: L-EC Uncorrectable Error
W 21:17:15 Sector 2099306 maps to File: \BDMV\STREAM\00000.m2ts
E 21:17:16 Failed to Verify Sectors!
I 21:17:17 Exporting Graph Data...
I 21:17:17 Graph Data File: C:\Users\User\AppData\Roaming\ImgBurn\Graph Data Files\hp_CDDVDW_TS-H653T_H6D1_MONDAY-NOVEMBER-20-2017_8-35_PM_CMC_MAG-D03-64_6x.ibg
I 21:17:17 Export Successfully Completed!
E 21:17:17 Operation Aborted! - Duration: 00:16:06
I 21:17:17 Average Verify Rate: 4,359 KiB/s (3.2x) - Maximum Verify Rate: 33,486 KiB/s (24.8x)


#5 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,541 posts
  • Gender:Male

Posted 23 November 2017 - 05:15 PM

I haven't read the pinned post, so I don't know what they're saying by Dye, but dye is generally determined by the manufacturer of the media.  Meaning that certain dyes work better than others and that each manufacturer makes their own dye.  And when they moved to Blu-Ray, they changed MID to DID (Disc ID) just to make it more confusing.  The MID is what really matters because that will tell you the manufacturer of the media.

 

 

Yes, look for DataLifePlus on the package.  But, here's the catch.  You probably won't find any DataLifePlus media in a brick and mortar store.  I only find them online.  I get mine from Amazon.com.

 

 

Yeah, the label on your first image says they're Life Series.  That means they're CMC's junk brands.  That 2nd image is what you're after.  Or something similar with DataLifePlus on the label.

 

 

Now, switching from CMC to MKM is not a magic bullet that cures all issues.  However, the majority of issues we see on this board are caused by CMC and other cheap media and when people switch to, in this case, MKM DVD+R DL, their problems tend to disappear.  So, it's what I generally recommend to start troubleshooting verify issues with.

 

 

The bottom line, sadly, is Verbatim is a business and all they care about is money.  :greedy:  If they can leverage their good name and still slap it on junk media like CMC, they will do it.  Verbatim used to make their own quality BD-RE.  Now, they only make CMC BD-RE with their name on it.  They know that most people won't know the finer details of what you should and shouldn't buy.  They know that people want to spend as little as possible, so they take advantage of that by slightly lowering the price of the CMC media they slap their good name on.  I wish it weren't the case, but the bottom line is they don't care.  Optical media market is dying, and Verbatim is trying to squeeze out the last dime they can from a drying revenue source.

 

 

Verbatim uses, as far as I know, two manufacturers.  They don't make their own.  CMC, the junk, and MKM, which is Mitsubishi Chemical Corporation aka MCC.  Notice now CMC calls themselves something close to MCC to try and trick people?  :rolleyes:  Mitsubishi is the highest quality manufacturer out there now that Taiyo Yuden has closed up shop.

 

 

Verbatim probably, I don't know for sure, doesn't sell MKM media in stores because it costs more for higher quality.  Even though the cost is about double, you're still only paying like $1 per blank.  However, people would rather spend 50 cents over a dollar.  Of course, if they knew the quality difference, they'd spend the extra 50 cents because it's only 50 cents.  Plus, there's a bigger profit margin on CMC media because it costs less to manufacture.

 

 

I know Verbatim has been using CMC since after 2010, but as to exactly when they were, I couldn't tell you.

 

 

The age of your drive could be a factor.  It could be so old that newer media is just not tolerated by the drive.  The maximum rated write speed is determined by the write strategy in the firmware of your drive.  A firmware update for you drive may increase maximum write speed.  However, it's always possible your case may be, given the age of your drive, your drive will default to something slower like 2.4x.  If it tolerates the media at all.  It could be the case in this instance the failure you're experience is caused by newer media on an older drive.  However, I would start with trying the quality blanks first and then working downwards in terms of troubleshooting.

 

 

According to your log, it looks like you're failing Verify right near the layer change, shortly after the start of the 2nd layer.  The vast majority of failures on cheap DL media will occur in a Verify at the layer change.



#6 Sarlacc Pit

Sarlacc Pit

    ISF Newbie

  • Members
  • Pip
  • 3 posts

Posted 04 December 2017 - 10:58 PM

I've just received the x8 DataLife Plus disks, written to them, and gotten 100% verification. I'll be able to try them in a Blu-ray player this weekend. Thank you both so much for your help!



#7 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,541 posts
  • Gender:Male

Posted 04 December 2017 - 11:11 PM

Now might come another problem.  The verification problem has been resolved by the higher quality Verbatim media, but your player may not particularly like DL BD media, regardless of the manufacturer.  Or it may just be picky on Verbatims.  It really is a sort of crap shoot of trial and error.  For instance, I know my Playstation 3 will play BD movies written to Verbatim BD-RE DL, but I've never written a single BD-R DL before.  And I know that the PS3 is picky about BD media.  It will play Verbatim BD-R fine but will not properly play Memorex BD-R made by Ritek.  Verbatim BD-RE, back when they made them and not CMC, also play fine in the PS3.

 

 

What you'll want to look for first is that your Blu-Ray player even recognizes that you inserted a BD-R DL to play.  If it finds it, that's the first hurdle overcome.  Then, what you'll want to look for is playback of the BD-R DL.  You'll want to look for skips, hisses, pauses, and pops in the audio/video.  Especially if it stops playing and then "skips" ahead.



#8 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,303 posts
  • Gender:Male
  • Location:United Kingdom

Posted 05 December 2017 - 07:05 AM

This thread is about DVD+R DL media, not BD media :)
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!

#9 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,541 posts
  • Gender:Male

Posted 05 December 2017 - 04:07 PM

Got my wires crossed with that other thread where the poster had problems with BD-R DL media not playing on his player.  I had forgotten he had resolved that by coming to the conclusion that his player was the problem.

 

 

Anyway, SOME :) of what I said still applies.  The next step is getting the player to recognize a DVD+R DL had been inserted.  Then, testing it by playing to see if there any playback problems like skips, pauses, hisses, or pops.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users