Blu-ray drive is missing from MakeMKV's list

[etPhoneHome]

I'm running MakeMKV in Windows.

I have two drives in my PC: a DVD drive and a new Pioneer Blu-ray drive. MakeMKV lists only the DVD drive in its list. Windows sees this drive just fine.

When it's scanning, I see it hesitate on both CdRom3 and CdRom5, but it only lists the DVD drive, which is CdRom5. I'm guessing that CdRom3 is my BD drive and MakeMKV isn't happy about something.

This drive works fine when plugged into a different computer. On that PC, MakeMKV sees the drive and it can rip just fine. It's just the combination of this drive in this PC that MakeMKV doesn't like.

UAC is disabled, which means Run As Administrator shouldn't do anything different, but I tried that anyway and it didn't make a difference.

Here is the debugging info that it spits out on startup:

DEBUG: Code 3221225653 at al<8}hH<r8Zi8C:29395241
DEBUG: Code 3221225653 at al<8}hH<r8Zi8C:29395241
DEBUG: Code 3221225653 at %g3Xf-sw:<Jd~`.I:29395379
DEBUG: Code 0 at %g3Xf-sw:<Jd~`.I:121263314
DEBUG: Code 3 at ~3}0ciW"6gB)vrqm0XW0$j,o^}:121261681

Any ideas?

Edit: I just connected this drive using a USB3 SATA bridge and it works that way. It doesn't work when connected directly to my motherboard. Why would that make a difference?

[Woodstock]

One thing to remember is that Windows has some "issues" with USB devices... The same device plugged into a different hub or even port ON a hub will be treated as a different device. Sometimes, it is obvious about this - try moving an USB serial port around, and watch it change COMx numbers. Sometimes it isn't so obvious, unless you're watching it say that it is "loading drivers" and "your device is now ready to use".

If Windows has a reason to dislike a device, it will remember where that device was plugged in, and will continue to dislike it if you plug it in there. But, plug it into a different port, "NEW DEVICE! I'LL SEARCH FOR DRIVERS NOW!"

I have a flash drive that works just fine plugged into the LEFT front USB port, but not the RIGHT front.

Oh, and sometimes (but not always), rebooting will make the same device start working.

[etPhoneHome]

Thanks for the tips, but I've tried them all already.

To clarify: this drive WORKS with my USB3-to-SATA bridge device, but DOES NOT work when directly connected via SATA internally to my mobo.

This is the drive I'm using: the Pioneer BDR-2209 (a.k.a. BDR-209UBK)

Windows sees the drive just fine. It gets a drive letter, and I can browse the files, open things, etc. It works perfectly EXCEPT that MakeMKV doesn't list it as a drive available for ripping.

Is it possible that the BD drive manufacturers have figured out a way to confuse MakeMKV into not supporting this drive?

[mike admin]

For some reason the drive rejects any scsi commands with an "timeout" error message. Can you check if ImgBurn works with your drive?

[varase]

For some reason the drive rejects any scsi commands with an "timeout" error message

More likely the driver is issuing a SCSI command which the drive blithely ignores causing the driver to eventually time out the command (or actually channel program since this is SCSI).

Is there a driver/protocol converter you have to install which translates SCSI commands to SATA? Isn't that why you have to install an ASPI driver for a non-SCSI drive?