Did a recent Software Update that was listed as a driver update. Should have known better.
LogicPro is timing out again and I'm getting the CoreMIDI error. This is really annoying, a huge time waster, and a disappointment. I thought it had been fixed.
AND this time around, keeping the AudioMIDI setup does not fix the problems.
Any clues on how I can clean up the drivers or figure out what's going on here?
Hi,
What did you upgrade from? OSX? Logic?
What is your MIDI interface?
What MIDI devices are connected?
There have been lots of issues with legacy MIDI drivers, devices and interfaces with the move to Catalina ( 64bit ) and Big Sur. Check with your MIDI vendor support and confirm support for your version of OSX for your device(s). This is a critical first step since the onus is on the Third party vendor to support OSX and many are lagging.
Here are a couple general housekeeping suggestions to start:
1) Make sure all your plugins (soft instruments, processing) fully support your version of OSX (and M1 hardware if applicable) and are up to date. Lots of legacy issues are causing lots of headaches and some started with Catalina. Critical: Remove and delete any Audio devices in the Apple Audio Midi Setup and uninstall any that are not valid.
2) Same for any MIDI devices ( keyboards, controllers, adapters or interfaces). Make sure all your devices fully support your version of OSX and are up to date. Remove and delete any MIDI devices in Logic ( Controllers ), in the Apple Audio Midi Setup and uninstall any drivers that are not valid.
I have seen an uptick with Midis Issue with since Logic 10.5 and here are my observations and tips:
1) Make sure ALL drivers are current and fully supported (Critical )
2) No USB hubs in the data chain to MIDI devices
3) Always start from a cold boot, no wake from sleep
4) No changing of accounts ( logout / login )
5) If using a combination of USB and a MIDI multi-port interface leave Port A open on the multi-port.
These steps solved about 99% of my ( and fellow musicians ) MIDI issues.
Hope this helps
( If this was helpful please mark as such or mark as solved if that is the case )
Hi,
What did you upgrade from? OSX? Logic?
What is your MIDI interface?
What MIDI devices are connected?
There have been lots of issues with legacy MIDI drivers, devices and interfaces with the move to Catalina ( 64bit ) and Big Sur. Check with your MIDI vendor support and confirm support for your version of OSX for your device(s). This is a critical first step since the onus is on the Third party vendor to support OSX and many are lagging.
Here are a couple general housekeeping suggestions to start:
1) Make sure all your plugins (soft instruments, processing) fully support your version of OSX (and M1 hardware if applicable) and are up to date. Lots of legacy issues are causing lots of headaches and some started with Catalina. Critical: Remove and delete any Audio devices in the Apple Audio Midi Setup and uninstall any that are not valid.
2) Same for any MIDI devices ( keyboards, controllers, adapters or interfaces). Make sure all your devices fully support your version of OSX and are up to date. Remove and delete any MIDI devices in Logic ( Controllers ), in the Apple Audio Midi Setup and uninstall any drivers that are not valid.
I have seen an uptick with Midis Issue with since Logic 10.5 and here are my observations and tips:
1) Make sure ALL drivers are current and fully supported (Critical )
2) No USB hubs in the data chain to MIDI devices
3) Always start from a cold boot, no wake from sleep
4) No changing of accounts ( logout / login )
5) If using a combination of USB and a MIDI multi-port interface leave Port A open on the multi-port.
These steps solved about 99% of my ( and fellow musicians ) MIDI issues.
Hope this helps
( If this was helpful please mark as such or mark as solved if that is the case )
Hi,
Your assumption that a driver is not closing out properly is most likely the issue ( a "dirty close") . I have seen situations like this and my suggestion is to always start from a cold boot, no wake from sleep. This steps resets all drivers and MIDI devices. If you have the patients to isolate the issue you would need to uninstall all MIDI drivers, reinstall one at a time and test until you find the culprit.
Prost
Don
Thanks Don. I didn't specify correctly - I did an Apple Software Update recently that was listed as a driver update. Prior to that, system was working perfectly. I'm on Catalina 10.15.7 and Logic Pro 10.6.3.
Specifically, my problem isn't with the midi chain, it's when Logic doesn't initially initialize the midi chain on my system, it's usually been a symptom of driver load at launch hang. My audio interface is a Clarett4Pre (Thunderbolt). Drivers are current.
Interestingly, the first time I boot the machine, the driver hang does not occur. But if I quit Logic and restart it, I get the hang. It's almost as if one of the drivers isn't shutting down properly.
Getting the "Error initializing CoreMIDI" error message again.
