Failed ripping, not sure what error means

Please post here for issues related to UHD discs
Post Reply
dinesh
Posts: 10
Joined: Mon Mar 13, 2023 1:24 pm

Failed ripping, not sure what error means

Post by dinesh »

i was trying to rip a 4K UHD disc and it ended with the following error:
Title #00171.mpls has length of 12 seconds which is less than minimum title length of 600 seconds and was therefore skipped
Title #00102.mpls has length of 216 seconds which is less than minimum title length of 600 seconds and was therefore skipped
File 00243.mpls (angle 1) was added as title #0
File 00243.mpls (angle 2) was added as title #1
File 00243.mpls (angle 3) was added as title #2
File 00244.mpls (angle 1) was added as title #3
File 00244.mpls (angle 2) was added as title #4
File 00244.mpls (angle 3) was added as title #5
File 00247.mpls was added as title #6
Title 00247.mpls(2) is equal to title 00247.mpls and was skipped
Title 00249.mpls is equal to title 00247.mpls and was skipped
File 00249.mpls(1) was added as title #7
File 00251.mpls was added as title #8
Title 00251.mpls(2) is equal to title 00251.mpls and was skipped
Title 00253.mpls is equal to title 00251.mpls and was skipped
File 00253.mpls(1) was added as title #9
Title #00100.m2ts has length of 14 seconds which is less than minimum title length of 600 seconds and was therefore skipped
Title #00104.m2ts has length of 0 seconds which is less than minimum title length of 600 seconds and was therefore skipped
File 00336.m2ts was added as title #10
Title 00247.mpls is equal to title 00249.mpls(1) and was skipped
Title 00251.mpls is equal to title 00253.mpls(1) and was skipped
Operation successfully completed
Saving 1 titles into directory C:/MakeMKV
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom0' at offset '33364899840'
udf: node fe/efe failed!
The source file '/BDMV/STREAM/00336.m2ts' is corrupt or invalid at offset 28487012352-28487018496, attempting to work around
Too many AV synchronization issues in file '/BDMV/STREAM/00336.m2ts' (title #-) , future messages will be printed only to log file
The source file '/BDMV/STREAM/00336.m2ts' is corrupt or invalid at offset 28507699200, attempting to work around
Too many AV synchronization issues in file '/BDMV/STREAM/00336.m2ts' (title #-) , future messages will be printed only to log file
Too many AV synchronization issues in file '/BDMV/STREAM/00336.m2ts' (title #-) , future messages will be printed only to log file
AV synchronization issues were found in file 'C:/MakeMKV/Blade Runner 2049 - 2017_t08.mkv' (title #9)
AV sync issue in stream 1 at 0:56:00.976 with duration of 15.833ms : audio gap - 19 missing frame(s)
AV sync issue in stream 1 at 0:56:00.995 with duration of 28.333ms : audio gap - 34 missing frame(s)
AV sync issue in stream 1 at 0:56:01.026 with duration of 30ms : audio gap - 36 missing frame(s)
AV sync issue in stream 1 at 0:56:01.058 with duration of 16.666ms : audio gap - 20 missing frame(s)
AV sync issue in stream 1 at 0:56:01.116 with duration of 14.166ms : audio gap - 17 missing frame(s)
AV sync issue in stream 0 at 0:56:01.649 : video frame timecode differs by +41.708ms
AV sync issue in stream 1 at 0:56:02.048 with duration of 31.666ms : audio gap - 38 missing frame(s)
Failed to save title 8 to file C:/MakeMKV/Blade Runner 2049 - 2017_t08.mkv
0 titles saved, 1 failed
When I tried ripping, it failed after running for about 20 mins. Does anyone know what may have gone wrong ?
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: Failed ripping, not sure what error means

Post by Woodstock »

Code: Select all

Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom0' at offset '33364899840'
Usually you see errors like this with drives that run out of power "at speed". Things get flowing very fast, then the drive just shuts off because the power is inadequate.

Does the offset change with different attempts to rip? Is it an external drive, powered by USB?
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
dinesh
Posts: 10
Joined: Mon Mar 13, 2023 1:24 pm

Re: Failed ripping, not sure what error means

Post by dinesh »

It is an external blu ray drive. The model is this one:
archgon Star UHD External 4K-Ultra HD BD Player, Blu-ray BDXL Burner for PC

It has been custom flashed as well. Do I need to change any settings ?
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: Failed ripping, not sure what error means

Post by Woodstock »

Are you powering it from a USB3 port, or a pair of USB2 ports?

Many of these types of drive will work just fine from a single USB3 port that is "fully powered". When powered by USB2 ports, though, they can run out of power at full speed.

USB2 can run out of power if plugged in with just one cable. Even with multiple cables, if they're plugged in to the sample place, you can overwhelm the power source if it isn't "fully powered".

If the offset of the error changes with the rip, that's a strong possibility.

If it is ALWAYS at the same spot, then it's more likely a problem with the disk itself.

A "fix" for the power issue is to slow down the rip somehow. I used to do it by ripping to a slow USB device, so the disk never spun at maximum speed. But USB data drives have gotten so much faster nowadays...
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
dinesh
Posts: 10
Joined: Mon Mar 13, 2023 1:24 pm

Re: Failed ripping, not sure what error means

Post by dinesh »

Thanks for the explaination. I am using a USB3 port. I tried switching to another port, but this time, the disc was not readable at all.

I feel something is wrong with the disc itself, as it was an old disc used quite a bit already.
Post Reply