Issue with MakeMKV and external USB enclosure?

The place to discuss Mac OS X version of MakeMKV
Post Reply
londoner
Posts: 3
Joined: Tue Feb 08, 2011 3:25 pm

Issue with MakeMKV and external USB enclosure?

Post by londoner »

[ MakeMKV v1.6.5 / DASPI 1.2 / LG CH10LS20 BluRay drive / JMicron based eSATA ->USB external enclosure / OS 10.6.6 ]

I am using a LG CH10LS20 BluRay drive in an external eSATA USB enclosure (Sumvision Tempest), details of eSATA ->USB interface below:

Code: Select all

  JM20336 SATA, USB Combo:
  Product ID:	0x2336
  Vendor ID:	0x152d  (JMicron Technology Corp.)
  Version:	 1.00
  Serial Number:	9A5943278888
  Speed:	Up to 480 Mb/sec
  Manufacturer:	JMicron
  Location ID:	0x24100000
  Current Available (mA):	500
  Current Required (mA):	2
Under normal usage (OSX 10.6.6) I can mount the drive and copy files to and from it without issue, including BluRays, but when using MakeMKV 1.6.5 (and 1.6.4 before it; albeit possibly not /exactly/ the same error) I get the error below:

I allow the disk to mount first in the Finder, which works fine, but when I start up MakeMKV the drive is recognised and then after scanning the title is recognised/displayed, but no details (in the right hand column) are shown and the 'protection field' is left empty. If I then press the 'BluRay -> Drive' button the process fails with the error below and the disk is unmounted from the Finder.

Code: Select all

Debug log started at Tue Feb 22 13:17:07 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/foo/MakeMKV_log.txt
002014:0000 Optical drive "DVD+R-DL MATSHITA DVD-R   UJ-868 KB19" opened in DASPI mode.
002014:0000 Optical drive "BD-ROM HL-DT-ST BDDVDRW CH10LS20 1.00" opened in DASPI mode.
001003:0020 DEBUG: Code 0 at ?lf4_`+2I f/`!Li?>v7)X+|(:213131318 thsi
DEBUG: Code 0 at 6{fMh;FO]PplR^L6DC&#/)Pz{:213130467
001003:0020 DEBUG: Code 0 at ?lf4_`+2I f/`!Li?>v7)X+|(:213131318
DEBUG: Code 0 at 6{fMh;FO]PplR^L6DC&#/)Pz{:213130467
001003:0020 DEBUG: Code 268435459 at %4<CY"<^I3P!(htGzw,{"p:121262302
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
001003:0020 DEBUG: Code 2281701379 at +>@PH894}5 iZK1(:29397357
If I try to use MakeMKV on a PC with the drive in the external USB enclosure I get a similar symptoms to the above (albeit possibly not exactly the same error, sorry I don't have the log file to hand, can get them if it helps).

However, if I mount the drive internally via eSATA in a PC the drive works fine with MakeMKV, which kind of points to an issue with the USB->eSATA interface rather than the drive itself.

At this point I would have pointed the finger at my enclosure, but the drive works perfectly (in the external enclosure) for any other operation, including other BluRay ripping programs on both the Mac and PC.

Unfortunately the PC I have been testing with isn't generally available to me or else I would have just scrapped the enclosure and gone with eSATA->eSATA internally.

Many thanks and please do let me know if there is any other debug information I can supply.
mike admin
Posts: 4065
Joined: Wed Nov 26, 2008 2:26 am
Contact:

Re: Issue with MakeMKV and external USB enclosure?

Post by mike admin »

This is a confirmed bug with this particular USB chipset ( JMicron ). The exact reason is still unknown.
londoner
Posts: 3
Joined: Tue Feb 08, 2011 3:25 pm

Re: Issue with MakeMKV and external USB enclosure?

Post by londoner »

Thanks Mike.

I ended up using a eSATA to USB adaptor off flea bay, which worked fine and may be a useful / cheap workaround to other hitting the same issue with this enclosure.
Post Reply