o copied 1 failed since purchasing key

MKV playback, recompression, remuxing, codec packs, players, howtos, etc.
Post Reply
derreckjames
Posts: 2
Joined: Sat Feb 24, 2024 9:31 pm

o copied 1 failed since purchasing key

Post by derreckjames »

I was using beta for no problem for two months then decided to support and purchase the $60 reg key and since it fails every copy I try. I have used multiple dif discs as well as plugging in usb disc player out of hub and directly to machine as well as saving copy to actual macbook pro.

I checked and it says my version is 1.17.6 and it's "registered"

Any thoughts? Ideas?

Thanks
Woodstock
Posts: 9984
Joined: Sun Jul 24, 2011 11:21 pm

Re: o copied 1 failed since purchasing key

Post by Woodstock »

What error message(s) did you see when it failed?
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
derreckjames
Posts: 2
Joined: Sat Feb 24, 2024 9:31 pm

Re: o copied 1 failed since purchasing key

Post by derreckjames »

Error 'Scsi error - NOT READY:LOGICAL UNIT IS IN PROCESS OF BECOMING READY' occurred while reading '/BDMV/STREAM/00011.m2ts' at offset '23360661504'
Failed to save title 0 to file /Volumes/Blurays/Library/Bad Boys_t00.mkv
0 titles saved, 1 failed
Woodstock
Posts: 9984
Joined: Sun Jul 24, 2011 11:21 pm

Re: o copied 1 failed since purchasing key

Post by Woodstock »

That's a message that often shows up when the disk is not being read correctly, i.e., you "hit a bad spot". The drive keeps trying to read said bad spot, but the computer thinks it's gone off-line.

Some people see that when the drive spins too fast for the available power, but that's usually a USB-powered device. The offset will also move around on subsequent attempts to read the disk. Making sure your USB has enough power for the drive will usually fix that.

If the offset doesn't change, or it isn't connected (and powered) by USB, the disk may have a bad spot. Cleaning it can help.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
Post Reply