an.eternal.hum

Yeah, after some research it appears to be somewhat common amongst Mojave users, but I have two friends also using Mojave who had never heard of it. Decent explanation of it in this comment https://music.stackexchange.com/a/79410 There were two basic workarounds: Launching Audio/MIDI Setup's MIDI Studio window, which force-initializes CoreMIDI; this has to be done before launch every time. Apparently, there was also some known conflict with Korg drivers, because running Korg's USB-MIDI Uninstall utility https://www.korg.com/us/support/download/driver/1/285/3856/ solves the problem as well -- though for me, that simply means the Error dialogue doesn't launch every time. Unfortunately, besides those two things, everyone's solution was simply to upgrade to Catalina, which I can't do on this machine. No issues with my cables, have tried several ports, don't use any hubs. I'm coming up with nothing, which is why I'm fairly certain the issue still lies with that CoreMIDI issue.

@des99 -- I downloaded Hosting AU and messed around. No MIDI input from my keyboard or Alesis drums. Repeated this with Garageband, same result. It appears the machine itself is not reading MIDI. I'm certain this is related to that known CoreMIDI issue, but am absolutely clueless where to turn next.

Hi folks. So I run 10.4.1 on two different machines. One is using MIDI perfectly flawlessly as plug-and-play, the other is a head-scratcher. Everything works simply and correctly on a 2015 MBP running Catalina w/16GB RAM. However, my main studio machine is a MacPro3,1 with 40GB RAM running Mojave. Both Logic Pro X 10.4.1 Initially, when I would open Logic on the Mojave machine, I would get the “Error Initializing CoreMIDI”, which I understand to be a common issue with Mojave. I uninstalled all Korg drivers as is recommended as a fix, and now no longer get that error. However, Logic still does not recognize MIDI controllers. Particularly, I am trying to get my Alesis Nitro Mesh hooked up; my computer recognizes it by name as a USB device however. On the other machine it is instantly recognized and enabled in Logic as soon as I power it on. Software instruments, both stock Logic and external Plugins such as Kontakt still read data when controlled by Musical Typing, if that’s helpful at all. Any tips? Anyone deal with this?

Hi folks. Logic Pro 10.4.1 OS X 10.14.6 MacPro3,1 w/40GB RAM Alesis Nitro Mesh drums Hey folks. I'm having some trouble getting my studio Mac Pro to recognize this kit as a MIDI controller. So I'm on Mojave -- I know that the CoreMIDI issue is a thing on this OS. So I started by getting the "Error initializing CoreMIDI" dialogue every time I would launch Logic. I used the workaround shown HERE to use Audio/MIDI Setup's "MIDI Studio" window to initialize CoreMIDI and get Logic to recognize MIDI. However, Logic still does not recognize the Alesis kit as a MIDI device. Mac OS recognizes the Alesis via USB, by name -- so my computer is obviously reading it. It's simply Logic that is not recognizing the device. Musical Typing inputs MIDI data just fine, but I do not have any other MIDI devices around to troubleshoot external MIDI connections with. My other machine -- 2013 MBP Retina, running Catalina and Logic Pro X 10.4.1 -- the Alesis is recognized immediately by Logic and works flawlessly, so I know it's not an issue with the Alesis. But my studio computer is hopeless at the moment. Anyone have any advice?