I tried burning a Blu-Ray but kept getting errors

Please post here for issues related to Blu-ray discs
Post Reply
wisetone
Posts: 4
Joined: Mon Jan 24, 2022 8:57 pm

I tried burning a Blu-Ray but kept getting errors

Post by wisetone »

When I tried to burn a film at the last 88 percent of the process it says

Code: Select all

MakeMKV v1.16.5 win(x64-release) started
Uses direct access option
Loaded contents of control table, trying to validate integrity of M2TS files.
File 00025.mpls was added as title #0
File 00034.mpls was added as title #1
Title 00000.mpls is the same as title 00034.mpls and is skipped
File 00008.mpls was added as title #2
Title #00001.m2ts has a length of 12 seconds, which is less than the minimum title length of 120 seconds and is therefore skipped
Title #00002.m2ts has a length of 10 seconds which is less than the minimum title length of 120 seconds and is therefore skipped
Title #00003.m2ts has a length of 1 second which is less than the minimum title length of 120 seconds and is therefore skipped
Title #00010.m2ts has a length of 23 seconds which is less than the minimum title length of 120 seconds and is therefore skipped
File 00013.m2ts was added as title #3
File 00014.m2ts was added as title #4
Title #00017.m2ts has a length of 0 seconds, which is less than the minimum title length of 120 seconds and is therefore skipped
File 00027.m2ts was added as title #5
File 00028.m2ts was added as title #6
File 00029.m2ts was added as title #7
File 00030.m2ts was added as title #8
File 00031.m2ts was added as title #9
File 00032.m2ts was added as title #10
File 00033.m2ts was added as title #11
Title #00034.m2ts has a length of 92 seconds, which is less than the minimum title length of 120 seconds and is therefore skipped
File 00035.m2ts was added as title #12
File 00036.m2ts was added as title #13
Title #00042.m2ts has a length of 52 seconds, which is less than the minimum title length of 120 seconds and is therefore skipped
Action taken
Save 1 title to folder D:/vedeo/CHARLIE_AND_THE_CHOCO
Title 1 was skipped
0 titles saved
Saves 1 title to folder D:/vedeo/CHARLIE_AND_THE_CHOCO
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22987536384'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22987536384'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22987536384'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22987536384'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22987536384'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22987536384'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22987536384'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22987536384'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22990221312'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22990614528'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22990614528'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22990614528'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22990614528'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22990614528'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22990614528'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22990614528'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22990614528'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22991468544'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22991468544'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22991468544'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22991468544'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22991468544'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22991468544'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22991468544'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22991468544'
Error 'SCSI error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred when reading '/BDMV/STREAM/00070.m2ts' at offset '22991861760'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred when reading '\Device\CdRom0' at offset '22991861760'
Error 'OS error - 

Translated with www.DeepL.com/Translator (free version)
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by Woodstock »

Burning isn't ripping. MakeMKV does ripping.

The error messages are consistent with a USB-powered drive spinning too fast for the power available to it. Make sure that the cable is plugged into a FULLY POWERED USB port, not an external hub (unless it has its own power supply).
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
wisetone
Posts: 4
Joined: Mon Jan 24, 2022 8:57 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by wisetone »

I use this blu ray player to rip them with Pioneer BDR-XD07TB I only have the usb connection to use cause my laptop doesn't have any disc drive :/
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by Woodstock »

In any case, USB-powered drives require fully-powered ports. Some require TWO powered ports, and come with a 2-headed cable. It is not normally a problem because most programs won't spin the drive at full speed... but MakeMKV can. When the drive tries to pull too much power from the port, the drive resets mid-rip.

If you're using the drive on a laptop, look at buying a POWERED USB hub that can provide at least 1 amp. USB 3 ports with a power supply are a good bet.

Some drives can have their speed limited in MakeMKV, but Pioneer drives don't do that right now.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
wisetone
Posts: 4
Joined: Mon Jan 24, 2022 8:57 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by wisetone »

Maybe if I use my gaming desktop computer it would help?
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by Woodstock »

What ever allows you to get enough current to the drive for the higher speeds you will see on longer rips.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
wisetone
Posts: 4
Joined: Mon Jan 24, 2022 8:57 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by wisetone »

I found out what the problem was, there is a protection on the blu-ray called AACS v12 which preventing me from ripping it.
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: I tried burning a Blu-Ray but kept getting errors

Post by Woodstock »

AACS v12 is ANCIENT. v76 has been out for a year now, and MakeMKV v1.16.5 can handle any AACS version up to 76 (higher with LibreDrive-compatible drives).

If you were experiencing an AACS issue, you wouldn't get any part of it ripped.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
Post Reply