www.makemkv.com

Update - the underlying bug in OS X was fixed in Yosemite developer preview 4. MakeMKV is fully compatible with OS X 10.10 Yosemite

As of now, MakeMKV is not compatible with the latest version of OS X - 10.10 "Yosemite" . The reason is a quiet withdrawal of an API that is required for MakeMKV GUI communication with makemkvcon process. So, while console-only makemkvcon would function as expected, launching the GUI would produce "Application failed to initialize" error. The fix is unlikely to arrive before official OS X release, while OS X 10.10 is in beta.

Technical details:
In 10.10 Apple rewrote from scratch so-called launchd daemon and related libraries. As part of that, so-called "bootstrap" API is no longer working, specifically the NSMachBootstrapServer::registerPort (which uses a low-level undocumented bootstrap_register2 API) no longer functions. As part of launchd rewrite, Apple removed all debugging and logging facilities (really, the "log" option in launchctl is now deprecated). Also, no source code is provided for the new daemon before OS release.
So, presently, the API that is declared as non-deprecated no longer functions, there is no (documented) way to enable logging, no source code and no debugging resources whatsoever. As noted earlier, the fix is unlikely to arrive before official OS X release.

Thanks for this information; this is quite troubling. I rely heavily on MakeMKV but I also want to be able to upgrade to Yosemite pretty much at the time it is released. Of all the third party apps and extensions etc. that I use, currently (Yosemite DP 5) the only one that is not already working is MakeMKV .

As far as I can see from the documentation this class/method (NSMachBootstrapServer::registerPort) should still work under OS X 10.10. Have you logged a bug with Apple on this? If there is some bug in this area then it could affect other software as well.

ChrisJ60 wrote:...As far as I can see from the documentation this class/method (NSMachBootstrapServer::registerPort) should still work under OS X 10.10. Have you logged a bug with Apple on this? If there is some bug in this area then it could affect other software as well.

I've seen this sort of thing before from Apple, it isn't uncommon for something that is supposed to work, not to work until after the release. It's very possible it will be resolved with the GM.

One alternative, if you could call it that, would be to run MakeMKV in a 10.9 VM under Parallels/VMWare/VirtualBox. This would give you the best of both worlds until a true solution can be found. VM's generally run slower because they don't have 3D acceleration however you're just talking about disc IO so it shouldn't be limited. I am going to experiment with this myself as I am in your same boat.

So, how do I enter a registration key for makemkvcon? (v1.8.11 is the current release.) Edit: For anyone else trying to figure this out, you can copy the MakeMKV folder from ~Library on your Mavericks install, and manually edit settings.conf to insert an updated key, if you need. It's probably also sufficient to create an empty settings.conf in that location and just add the single line:

Just in case anyone else finds this thread via Google and then can't find the MakeMKV folder in ~/Library/ -- that's because it isn't there

It's ~/.MakeMKV/

Which I knew, but forgot, and went a little nutty trying to find.

However, even after copying the ~/.MakeMKV/settings.conf file from my Mavericks Mac to my Yosemite Mac, I still get an error: "Application failed to initialize"

This is with version 1.8.12 of MakeMKV using the first version of the Yosemite public beta.

TJLuoma wrote:Just in case anyone else finds this thread via Google and then can't find the MakeMKV folder in ~/Library/ -- that's because it isn't there It's ~/.MakeMKV/

It must have moved at some point, so I assume both work. Mine was in ~/Library/MakeMKV.

TJLuoma wrote:However, even after copying the ~/.MakeMKV/settings.conf file from my Mavericks Mac to my Yosemite Mac, I still get an error: "Application failed to initialize

Yes, this procedure is just to get makemkvcon working if it's complaining about an out of date registration (since the MakeMKV app doesn't work on Yosemite). The problem with the MakeMKV app itself is completely different.

Just tried Beta 2 release and MKV failed at launch. Sent a bug report to Apple about it. Don't know if it will help any. Hope you get it working for final release.

Is there documentation anywhere for the console version that does work? I glanced through the faq and help docs but didn't spot it. Even if I can get it working via command line, it's worth it.

DJRumpy wrote:Is there documentation anywhere for the console version that does work? I glanced through the faq and help docs but didn't spot it. Even if I can get it working via command line, it's worth it.

http://www.makemkv.com/forum2/viewtopic ... 014#p34880

Thanks and much appreciated. Exactly what I needed.

I just get a generic failure reading disc. :/

It sees the correct drive. Indicates it's in direct disk mode and then errors.

/Applications/MakeMKV.app/Contents/MacOS/makemkvcon info disc:1

MakeMKV v1.8.12 darwin(x86-release) started
Optical drive "BD-ROM Optiarc BD ROM BC-5500S 1.75d" opened in OS access mode.
Failed to open disc
Total 0 titles

DJRumpy wrote:/Applications/MakeMKV.app/Contents/MacOS/makemkvcon info disc:1

MakeMKV v1.8.12 darwin(x86-release) started
Optical drive "BD-ROM Optiarc BD ROM BC-5500S 1.75d" opened in OS access mode.
Failed to open disc
Total 0 titles

Looks like you only have one drive, but you are specifying disc:1 which is the second drive (drives are 0 based). See the notes in my other post for details.

No I have two drives. The internal DVD-Rom and my external BD-Rom.

DJRumpy wrote:No I have two drives. The internal DVD-Rom and my external BD-Rom.

Hmm tough to say. When I run the command it shows both drives, even though I am scanning only the 2nd: