The place to discuss Mac OS X version of MakeMKV
-
cbrad
- Posts: 8
- Joined: Tue Jan 25, 2011 10:20 pm
Post
by cbrad » Tue Feb 22, 2011 4:34 am
mike admin wrote:The first 3 messages, you can't get them in 1.6.5 - the bug was fixed. Is it correct? For the rest, please update DASPI to 1.2 and see if it changes anything.
I have installed DASPI 1.2. I inserted a bluray disc and waited for it to appear in the finder before starting makemkv. Makemkv failed to open the disc.
Code: Select all
Debug log started at Tue Feb 22 04:27:44 2011 , written by MakeMKV v1.6.5 darwin(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.6.5 darwin(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/cbrad/MakeMKV_log.txt
002014:0000 Optical drive "DVD+R-DL PIONEER DVD-RW DVR-K06 Q609" opened in DASPI mode.
002014:0000 Optical drive "BD-RE HL-DT-ST BD-RE BH10LS30 1.00" opened in DASPI mode.
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
<snip> lots of the same lines</snip>
005010:0000 Failed to open disc
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
<snip> lots of the same lines</snip>
Application exited at Tue Feb 22 04:29:00 2011
-
efithian
- Posts: 15
- Joined: Mon Mar 07, 2011 5:43 pm
Post
by efithian » Fri Mar 11, 2011 1:11 am
I haven't had any problems ripping, except for a scratched disc. Writes pretty well on Ritek 25GB disks. My drive is installed in a MacPro 3.3GHz 6-core Westmere with 5TB drive space and 10GB ram. I was making some dvd copies of some stuff, so I recorded blank dvds on both the LG and the Apple drive at the same time with no problems.
It appears to take about 40 minutes to rip a BR disc and about 30 minutes to write a 25GB BR disc at 4x. It shows up under WinXP in Parallels 4 and is useful for firmware upgrades, but I can't play anything on it, but that isn't important. The drive was $80.
-
mike admin
- Posts: 4067
- Joined: Wed Nov 26, 2008 2:26 am
-
Contact:
Post
by mike admin » Sat Mar 12, 2011 9:24 am
The next version will add a workaround for a confirmed bug in JMicron-based USB-SATA bridge chipsets. Your enclosure seem to use this chipset. As for the drive, after riplock is removed with mediaspeededit, this drive is of the best drives around.
-
cbrad
- Posts: 8
- Joined: Tue Jan 25, 2011 10:20 pm
Post
by cbrad » Sat Apr 02, 2011 10:53 pm
mike admin wrote:The next version will add a workaround for a confirmed bug in JMicron-based USB-SATA bridge chipsets. Your enclosure seem to use this chipset. As for the drive, after riplock is removed with mediaspeededit, this drive is of the best drives around.
Thank you and well done. Version 1.66 works!
-
priitv8
- Posts: 19
- Joined: Wed Jan 26, 2011 6:20 pm
Post
by priitv8 » Sun Apr 03, 2011 11:14 am
For what it's worth for the developers: now, using the MakeMKV 1.6.6 and DASPI 1.2 driver with the same JMicron USB-to-ATA Bridge and Sony BPD-100 drive, the ripping progresses farther, than it used to (seen also in the log), but ultimately fails at the same spot:
Code: Select all
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT COMMUNICATION FAILURE' occurred while reading '/AACS/MKB_RO.inf' at offset '1856'
003303:0000 The volume key is unknown for this disc - video can't be decrypted
-
Attachments
-
- MakeMKV_log_MR.txt
- (204.8 KiB) Downloaded 463 times
-
mike admin
- Posts: 4067
- Joined: Wed Nov 26, 2008 2:26 am
-
Contact:
Post
by mike admin » Mon Apr 04, 2011 7:36 am
priitv8 wrote:For what it's worth for the developers: now, using the MakeMKV 1.6.6 and DASPI 1.2 driver with the same JMicron USB-to-ATA Bridge and Sony BPD-100 drive, the ripping progresses farther, than it used to (seen also in the log), but ultimately fails at the same spot:
Code: Select all
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT COMMUNICATION FAILURE' occurred while reading '/AACS/MKB_RO.inf' at offset '1856'
003303:0000 The volume key is unknown for this disc - video can't be decrypted
In your log file the error is
Code: Select all
002003:0000 Error 'Scsi error - HARDWARE ERROR:LOGICAL UNIT COMMUNICATION FAILURE' occurred while reading '/BDMV/CLIPINF/00360.clpi' at offset '0'
. Is it always happening at the same place or at random files/positions?
Even if it sounds silly, can you try another USB cable?
-
priitv8
- Posts: 19
- Joined: Wed Jan 26, 2011 6:20 pm
Post
by priitv8 » Sun Apr 10, 2011 11:16 am
mike admin wrote:Is it always happening at the same place or at random files/positions?
Well, on the same disk, always the same file/offset, apparently. But I've also managed to get different results between different run sessions. That's a bit confusing. See the attached logs for details.
mike admin wrote:Even if it sounds silly, can you try another USB cable?
It's a bit complicated, because I'm using the USB-to-(S)ATA adapter that has the USB cable integrated:
http://www.manhattan-products.com/en-US ... de-adapter
-
Attachments
-
- MakeMKV_logs.zip
- Logs
- (355.91 KiB) Downloaded 480 times