Error initializing coremidi

This has been a known issue for a while now and I’m hoping Apple can take some solid steps to address it. For me, as it’s been for many, it would seem, the update to Mojave has caused some serious issues with initializing Core MIDI when opening Logic Pro X. This is an issue that is persisting throughout updates to Logic and to OS X and it’s becoming quite frustrating. It seemed to have gotten a LITTLE bit better with the last update (I would normally launch Logic once, receive the «Error to initialize» message, quit, re-launch Logic, and everything would be fine) but today it’s much, much worse. I restarted my machine and Logic many times before MIDI started working. I also tried the workaround of launching Audio/MIDI setup before re-launching Logic, and that didn’t work. Finally, after launching Logic seven or eight times, core MIDI initialized and now it’s working.

I use Logic professionally and this is a giant time-waster. I love the software but I’m hesitant to continue updating OS X if these launch issues are going to get worse with each update. Esteemed Audio/MIDI engineers at Apple, I’m imploring you to look into these issues seriously, I know I’m not alone!

(For the sake of being thorough: my machine is a 2013 iMac that’s still running like a champion after six years! My interface is a Steinberg UR-22, which I’ve been very happy with overall. I run one MIDI input into that from a Yamaha controller and a second MIDI input directly from the USB MIDI connection on an M-Audio Axiom Pro 61.)

So I learned on another forum that the problem is caused by a hard coded timeout in Logic Pro X for initializing CoreMidi, and that with the most recent versions of OS X, CoreMidi takes significantly longer to load than with prior versions of the OS. Considering how many professional musicians use Macs and Logic Pro to get stuff done, it is absolutely appalling and unforgivable that Apple hasn’t fixed this problem yet. It’s a totally known issue. I suspect it’s a politics issue of the Logic Pro team pointing to the OS X team and saying it’s their problem to fix, and the OS X team pointing to the Logic Pro team and saying they should just remove the hard coded timeout limit, and neither team is budging.

So for now, those of us experiencing this problem must always remember to first open Audio Midi Setup, then go to Window / Show Midi Studio and let it fully initialize and display all the midi drivers, and then—and only then—load Logic Pro X. And when that doesn’t work, reboot and retry that sequence.

The product teams at Apple should really be embarrassed.

1. Today I bought a Maschine Mikro MK3 as an alternative to my Maschine MK3 when I am on the go. However, it does not show up as controller surface in Logic Pro X as my Maschine Mikro does. Not even the transport controls work!

   Is this a bug or a missing feature?

2. Two of the same devices might conflict in logic controller section. This happened to me with two different makes of devices that had the same function. I had to trash preferences for logic and reintroduce them to logic.

   Sent from my iPad using Tapatalk

3. Thanks for your reply! However, I do not have my Maschine MK3 connected to Logic Pro X, only the Maschine Mikro Mk3. This is with a fresh install of Logic Pro X that has never seen my Maschine MK3. Same thing happen if I remove the .cs file from my user library.

4. Hi! The issue I’m experiencing is somewhat the same. I use a Komplete Kontrol A49 and other than the functionality in the NI software I really enjoy how the transport controls function in Logic Pro X. I bought the Maschine Mikro MK3 expecting that it would have the same functionality. My idea was that I could use it with the NI software plugin in Logic, but also use it as a normal midi controller (like my old Akai MKP25) when not using the NI plugin. I was expecting it to just be plug and play, but I can’t seem to get it to work. I’ve been forum hopping and trying different things, amongst others adding it as a control surface in Logic.

   What stands out to me is that you can install the Maschine MK3 as a control surface, but the Maschine Mikro doesn’t seem to appear as an option in the install menu. I don’t understand why this is, as it would seem like quite an oversight to be able to do this with the Maschine MK3 but not the Mikro.. Does anyone know if there is a solution to this? Or should I return te device?

   I also tried this option by the way with no result: https://support.native-instruments….ler-for-Host-Transport-Control-in-Logic-Pro-X. HALP!

5. The Mikro-MK3 is more limited in MIDI mode than the full MK3 and does not have a «Control Surface mapping» inside Logic but you can map all the buttons yourself if you want with MIDI learn in the «Key Commands» Menu. The pads are plug and play tho…Yeah, because it has no Control Surface Mapping as I said above.

   IMO A Mikro-MK3 needs easy MIDI even more than an MK3 because people are more likely to buy it with the intention of using it to control their DAW, especially the new «newbie» target audience… NI doesn’t seem to agree, last time there was an official statement about similar issues they said they «were trying to establish if there’s a real need from customers» for better MIDI before they commit to making it happen, you can point your opinion here: https://www.native-instruments.com/forum/threads/announcing-maschine-mikro-mk3.335575/
   Good luck with that.

   Yes, there is. Map the buttons yourself, pretty easy to do. Here’s an example, let’s say I want to Map the Mikro’s Play button:
   Enable MIDI Mode on the Mikro, search for «Play» in Logic’s Key Commands Menu, press «Learn New Assignment» and press the button on the Mikro. Repeat for everything you want to map and it’s done.
   That’s for «Host Transport Control», which means the ability to use the Transport without switching to MIDI Mode, which means you can use the transport while the unit is still controlling Maschine plugin; unfortunately, that requires Controller Editor support and this is another thing that the Mikro MK3 does not have.It’s up to you how important a mapping preset and Host Transport Control(+Controler Editor) support really is for you and if the lack of both justifies returning the unit.

   • Informative x 1

6. Hi D-One,

   Thank you for your in depth and and super clear reply. It is very much appreciated. I’m sad to hear that this is the current status quo though. Like you say, from a consumer perspective it would have made so much sense to have this functionality for specifically the Mikro. Guess I’ll voice my feedback in the thread you suggested, for all the good it’ll do me.. I’ll also mess around with the manual mapping. I’d like to give the device a real chance, the hardware is top notch. Thanks again for your help

7. Hi D-One, sorry for pestering you. I did like you suggested, and generally it worked pretty easily with your guide. However, I find that I have to press every button twice for it to do what I want. I can’t seem to locate the issue. Do you have any advice for me regarding this? Also do you know if there is a way to set the rotary control knob to scroll through a project (like the knob on the A49)? Thanks again for your help.

8. Hi, don’t worry its all good.
   Oh… It does indeed, sorry I am not a Logic User and I just quickly tried without testing much, my bad.

   Here’s the deal, the Mikro-MK3 transport buttons work as a toggle, meaning press it once and it sends velocity 127, press it again and it sends velocity 0, this is good to map things to On/Off but in this case it creates an issue because the Logic expects the same velocity not two different ones, to fix it simple map the buttons twice, like so:

   • Press «Learn New Assignment in Logic and press Play on the Mikro-MK3,
   • Press «Learn New Assignment» again and Play again.
   • If you see one mapping at 0 and another at 127 it will work correctly.

   I think you just map the encoder right turn to «Select next track» and left to «Select Previous track», for me there’s a conflict with volume, probably because I messed around too much and broke something, test it and let me know.

   As far as the OP goes I think it’s pretty much solved so ill tag the thread accordingly.
   I might make a Guide Thread for this or attempt to make Custom Controller Mapping.

9. Hi D-One, you are an absolute legend. This gave me all the functionality I require. Of course it would be best and more elegant to have the device supported and not have to switch between modes, but for now I think this will work just fine. Thanks again!

10. Hhah thanks!
    It certainly would make the MikroMk3 a lot more useful but I am not sure if that will ever happen, or when… all we can do is pray for them to «determine that there is a genuine demand for it».

11. Well. I’m sorry to keep coming back for the same thing but stuff is getting weird.
    After all the above everything seemed to be working fine. Then this happened: I was working on a project in Logic Pro X, just a couple of audio tracks, nothing MIDI or NI plugin related. I had to restart my Mac (which is just 2 months old btw) and suddenly got a «Error Initializing CoreMidi» and suddenly my midi devices stopped functioning. I tried a number of things including restarting without MIDI devices hooked up, but kept on getting the error.

    The 2 midi devices I currently have hooked up are the Mikro and the A49.
    I’ve been troubleshooting and among other did the following: «Preferences > Reset all preferences except key commands» which seemed to do nothing. Then I did the following: «Preferences > MIDI > Reset all MIDI drivers». Again, nothing seemed to happen other than me not getting the error anymore. Nevertheless, the MIDI devices still weren’t working. Then under the MIDI menu I discovered the tab «Inputs». It kind of freaked me out because it was showing the following:

    

    

    I don’t know how or why, but there are dozens of «Maschine Mikro MK3» and «Komplete Kontrol A DAW» listings. I don’t know of this is a logic/Mac issue, or a NI hardware issue. All these devices were marked as «On». I deactivated them all, and as is visible in the images only activated the white Maschine Mikro MK3 and Komplete Kontrol A49 listings (all the others are greyed out). Both devices seem to work again like before, however all the key command’s I’ve mapped to the Mikro seem to be gone. They are still visible in the key commands menu but do nothing. I tried mapping some keys again, and they work again. The mapping itself is identical though. In the below example the bottom 2 «Control change 57» listings are the «old» ones, and the top 2 are the new ones:

    

    I think that for some reason Logic is not identifying my Mikro as the same MIDI device I originally mapped the keys to.

    So in summary: I don’t know if this is a Mikro driver/hardware issue, or if it’s a logic/Mac issue. I’ll reach out to Apple and ask them about this as well. I have a feeling I might have gotten the CoreMidi error because logic was seeing too many devices simultaneously. Is this by any chance a know issue to anyone? And how do I prevent it from occurring? Why do I have so many listings of the Maschine Mikro MK3 and Komplete Kontrol A DAW in my MIDI inputs?

    I’m sorry if I’m posting this in the wrong forum, but as it seems related to the previous posts I thought it best to post here..

12. Oh boy… Do you have other Music software with MIDI capability? To test if this is only happening in logic.

13. Only garageband, it supports MIDI but the menus don’t go into much detail about what’s connected and what’s not. I’ve just finished re-mapping the Mikro and it seems to work fine again. I’ll try some different things to see if I can find out what’s the trigger that causes all these new MIDI inputs to get created..

14. I googled around and it seems to be a common issue only in Logic, check their forum for extra info.

15. Yea I’m currently researching the issue there as well. I find there’s a lot of ppl that have the CoreMidi error, which is where I got the reset options mentioned above. I haven’t been able to find anything relating to the midi input duplicates though. What I’m finding so far are solutions to the symptoms, not the problem. As soon as I find out anything useful I’ll let you know.

16. So, after some trial and error I’ve been able to figure out the following: whenever I restart my system and subsequently start Logic a new version of the «Maschine Mikro MK3» and «Komplete Kontrol A DAW» get created in Logic, visible in Preferences > Midi > Inputs. As far as I’ve been able to tell some of these newly created inputs generate the «Error initializing CoreMidi». When I get this error I can «solve» the problem by unchecking the «older» versions of the «Maschine Mikro MK3» and «Komplete Kontrol A DAW» inputs, and only leaving the newly created ones on. Then I have to restart Logic and everything «works» again.

    I’ve noticed that I can predict when I get the error by looking at the Logic startup screen when it’s opening. Logic automatically opens your latest project on startup. I have a new Mac, so it opens the project instantaneously. However this doesn’t happen when I’m about to get the error. I notice the loading screen hanging at this specific point:

    

    My main question is still: how do I keep this problem from occurring and stop these duplicate Inputs from getting generated?

    I’ve also started wondering about the «Komplete Kontrol A DAW» relates to? This appears on the list even before I got the Mikro, so seems to be related to my A49. However, there is also one «Komplete Kontrol A49» listed for which no duplicates seem to get generated.

17. Goto Mac utilities/audio-midi , bring up the midi window and see what’s going on there

18. Hi Aldred,

    Thanks for helping with this. Someone on the Apple forums suggested the same thing. However (to my mind at least) it didn’t seem to yield any results:

    

    In other words: all the duplicates that I’m seeing in Logic don’t appear here. I did remove my old AKAI MKP25 and Korg K61 controllers from this list since they are no longer in use. But other than that this is all I’m seeing. One interesting thing though is that the Mikro isn’t showing up here….

19. Mikro isn’t showing on my Mac
    I’ll check later with it plugged in tho , but my studio and kkmk2 show and they’re not plugged in

20. Yea, it’s hard to tell what things are related and which aren’t. The only thing I fear is that Apple will say it’s a NI issue and NI will say it’s an Apple issue >.<

Gary Fagin Registered Member Date Joined Dec 2004 Total Posts : 2	Posted 12/20/2004 8:11 PM (GMT -6)
I’ve been using Finale 2004 on my Mac (OS 10.2.8) with no problems since I received the software earlier this year. Today when I opened Finale 2004 it got stuck while initializing CoreMIDI and then the following error message appeared: «An error occurred while attempting to use CoreMIDI.» The program opens, but then does not respond to the MIDI keyboard. What is CoreMIDI? Any advice on how to correct the situation? Thank you, Gary Fagin Back to Top

Fergi Registered Member Date Joined Dec 2004 Total Posts : 68	Posted 12/21/2004 4:06 AM (GMT -6)
As far as I know, Core Midi is the system programme that runs all the midi interfacing and clocking and it shares its space with CoreAudio. Here’s a link : http://developer.apple.com/audio/coreaudio.html I’ve had the same problem once or twice, but it always goes away and seems to be just an error in initialisation. Wheh FInale starts it runs to Core Audio to set up midi connections with any outboard interfaces, and sometimes screws it up. I’ve found that by just reopening Finale it usually succeeds next time around. In the midi menu you can check all your connections using Audio Midi Setup. Gus Back to Top

Gary Fagin Registered Member Date Joined Dec 2004 Total Posts : 2	Posted 12/21/2004 11:14 PM (GMT -6)
Thanks, Gus, for your input. I spoke to Finale Tech Support today; they had me recongigure my MIDI audio set-up so it works now. Back to Top

Forum powered by dotNetBB v2.42EC SP3
dotNetBB © 2000-2023