1.6.5 DASPI troubleshooting

[mike admin]

Here are good news and bad news. Bad news is that if you ever had DASPI-related issues in 1.6.4, you'll likely to have them in 1.6.5 too. The good news is that version 1.6.5 has additional logging code that should help troubleshoot the problem.

Two DASPI-related problems were reported:

• MakeMKV can't access the drive at all, prints "code 5" errors. Seems to happen only on external USB drives.
• Eject button doesn't work and locks the disc in drive.

If you encounter either of these problems, please make sure that "Log Debug messages" is enabled in preferences. Then reproduce the problem and share your MakeMKV.log file either here, via PM or by sending to support@makemkv.com . Make sure to send the full log file and not just copy debug output from bottom pane, as log file might contain additional information.

To work around "eject" problem, please try to close MakeMKV, launch it again and press eject once again.

[woodmeister]

Odd problem, in that it works on machine and not another. On my iMac (early 2009),
the latest version works just fine. No issues as far as I could see doing some limited testing.
With an external BD drive, either USB connected or Firewire connected. On my MacMini (2010)
when I open MakeMKV with the same drive connected, it just sits forever looking at the internal
drive and never looks for the external. The only thing that can be done is quit the application from
the menu. Clicking the stop icon in the window does nothing. It just continues to sit there searching.
If I do a kextunload on the DASPI driver and restart MakeMKV, it almost immediately finds the disk in
the external BD drive. So, far everything seems to be fine that way.

When my current test rip is done, I'll enable the logging and then re enable the driver and
get a log file.

[woodmeister]

Here's a log file from my MacMini when things go amok:

Debug log started at Wed Feb 16 20:03:06 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/woodman/MakeMKV_log.txt
001003:0020 DEBUG: Code 5 at YfjF{";&#,B-2r:29395563
001003:0020 DEBUG: Code 5 at YfjF{";&#,B-2r:29395563
001003:0020 DEBUG: Code 83886085 at +>@PH894}5 iZK1(:213131502
001003:0020 DEBUG: Code 0 at +>@PH894}5 iZK1(:213131088
001003:0020 DEBUG: Code 0 at ARlDRF+g!QZO/)&:213130605
001003:0020 DEBUG: Code 117506113 at YfjF{";&#,B-2r:29395241
001003:0020 DEBUG: Code 117506113 at YfjF{";&#,B-2r:29395241
001003:0020 DEBUG: Code 117506113 at +>@PH894}5 iZK1(:213131502
001003:0020 DEBUG: Code 0 at +>@PH894}5 iZK1(:213131088
001003:0020 DEBUG: Code 0 at ARlDRF+g!QZO/)&:213130605
005042:0000 The program can't find any usable optical drives.
Application exited at Wed Feb 16 20:04:26 2011

What is really strange here is that the internal DVD drive disappears
from the system completely after I quit Make MKV. It no longer
shows up in the System Profiler or in Disk Utility. When this log was created,
there were no disks in either drive, which is what you want if you want
to read BD stuff from the hard drive. Also, I had pressed the stop icon
when this log was created and the dialog came up, told it I really wanted to
stop. And again, it just went back to the same screen and kept counting
as if it was looking. Had to select quit from the menu to get out.

I restarted the computer and all drives show up. I then started MakeMKV
again, and ended up with the same results when I repeat the process.
When I remove daspi.kext and reboot, everything works
just fine without any disappearing drives and with no discs in either drive
and I can read and stream my BD backup rips and pretty much all else
works fine.

Once again, the odd thing is that things seemed to be just fine on my iMac.
Between the iMac and the Mini, they do have different DVD drives and more than likely
different SATA controllers and therefor different drivers. Might be some clue there.

[vinger]

Hi Mike,

I'm french. So excuse me for my bad English.
I'm also one of the first MAC users of MakeMKV.
BUT, now it doesn't work fine, since I've upgrade to the 1.6.4 release.
I have an USB SilverStone Bluray drive which worked fine for all my BR (except AVATAR : I've posted it in April).
To explain my problem, I can focus on some new behaviours when I try to rip a BR.
Before : My BR was unmount and the process continue
Now : The BR stay on my desktop when the process begun. then there are many error message and after a moment the message "Failed to open disk" appears and the BR was unmounted... and it's finished. MakeMKV
I don't understand, so I install MakeMKV on my other MacMini, but the problem is exactly the same !
So I join my MAkeMKV.log file when I try to rip HOME BR, and a screen capture when it stops after errors...

MakeMKV_log.txt

MakeMKV PB.png

Thanks for your HELP

Best regards,

Vincent

[riplin]

Another thing I noticed, I'm not sure if it's related, is that, when using the close / restart / eject procedure, MakeMKV leaves a zombie process behind (makemkvcon), some of which take up over 500MB of memory.

One last thing (that's definitely not related ) is that i noticed you're now storing the window position / size between launches. Every time i restart, the window gets a little bit smaller, as if it's not accounting for either the title bar height or the status bar height.

[mike admin]

Please see http://www.makemkv.com/forum2/viewtopic.php?f=4&t=2751