Logic MIDI control surface issue (Native Instruments)

Hi Pancenter,

Sorry to take so long, it's been a hectic weekend. I still have the intention to do some testing with the Minilogue MIDI driver to see if I can duplicate the issue, but I'm pretty sure that was the problem, since everything has been working fine since removing it. As far as the "duplicate midi inputs on device restart", we discussed this on the NI forum and it's getting reported as a "bug". Apparently it was unrelated to why the errors were occurring.. You've been of great help, so thank you again!

Hi Pancenter,

Thank you for your reply. Unfortunately this did not resolve the issue. All the duplicates that seem to get generated in Logic don't appear there. I have done some testing and have a much clearer idea of what's happening, but it seems that I can't. I suppose I'll make a new post, but I hope to see you there..

The MIDI Drivers folder under ~/Library appears empty to me.

The MIDI Devices folder only seems to contain the Generic device you mentioned. If I look in the MIDI drivers folder in that same location it only shows "KorgUSBMIDIDriver.plugin" which I'm pretty sure is the USB MIDI driver for my Korg Minilogue, which I currently have disconnected while troubleshooting this issue.

Hi Pancenter,

Thanks again for your help. I did like you suggested. The only thing that happened is that Logic auto detected the Komplete Kontrol A49, like it would when you plug it in the first time. After rebooting my system again I once again got the Error initializing CoreMidi, and another duplicate set of inputs for the Maschine Mikro MK3 and Komplete Kontrol A DAW (I'm not quite sure what this second one relates to). The long list of MIDI inputs didn't get cleaned up by this either I'm afraid.

I suspect some of the inactive (greyed out) duplicates that are generating the "Error Initializing Core Midi" errors, and I found that after deactivating these "old" versions and keeping the new ones to set to "On" the devices will function normally once I restart Logic. However as you can probably imagine this problem keeps repeating itself with every reboot..

Hi Pancenter,

I did run a normal system update when I got prompted by my Mac about a week ago. Before that I updated everything I could when I got it in December. I did some more testing and verified that the Komplete Kontrol A49 is generating the " Komplete Kontrol A DAW" duplicates and the Maschine Mikro is generating the "Maschine Mikro MK3" Midi input duplicates.

I did install the Monologue driver at a later point (somewhere in January perhaps) but the problems didn't start exactly when I installed it. Just to eliminate it as a factor though I uninstalled the driver using Korg's uninstaller. This is what happened: until I uninstalled the driver I would get the CoreMidi error every startup (this only started in the last couple of days). I just uninstalled it and rebooted my system a couple of times to test. I'm no longer getting the CoreMidi Error (or haven't yet) but the duplicate midi inputs are still getting generated.

Hi again!

Thanks again for all the effort you are putting in. It's hard to convey on the internet, but it's really appreciated.

I have a new MacBook Pro 15" 2018 with 16gb, 2,6 Ghz Intel Core i7. Everything is as up to date as I can get it.

The Native Instruments controllers have their own software (basically sound libraries) that you can also run as a plugin in your DAW. When first using/installing the controllers you go through a 4 step program on their site that helps you install the software and update the firmware: https://www.native-instruments.com/en/specials/komplete/komplete-kontrol-setup/ which I did for both devices in the manner specified (and did again when the issues started occurring).

On the NI forum we've been going over this as well there are a lot of similarities with the steps you are proposing. Someone tested with his/her Mikro as well and noticed that in Logic the another MIDI input for the Mikro would get created every time the device has been powered down and powered back on again. So at least we've determined that it isn't unique to my system. I'm hoping we can still figure out why the duplicates get generated (if only to prevent it from causing issues in the future) and how to purge the MIDI inputs list in logic. Somehow it doesn't feel like a good idea to have hundreds or thousands of midi inputs accumulating in that list..

My current assessment is that both issues might be unrelated: I likely got the CoreMidi Errors from the Korg Minilogue drivers which caused all midi devices to become inactive. While looking for the issue I stumbled upon the MIDI input duplicates and assumed both issues were connected since I haven't really working with the Minilogue when these problems started occurring.

Tomorrow I'll try and and do some tests with the Minilogue USB/MIDI driver, see if their forums have some information on this and if its possible to update the Minilogue firmware.

I also understand what you're saying about being careful with the updates, but somehow, in my mind I thought the Pro series were designed exactly to accommodate these types of "heavy" usage and integration. I always felt that the Mac OS was better with driver integration etc.