I received a message from a producer who was having trouble with his M-Audio Keyboard not connecting to Logic Pro.
We arranged a time to connect, established a remote connection and I had a look at his system. First, I checked inside Logic’s MIDI environment and in OSX’s Audio MIDI Setup to see if the keyboard was being recognised by Logic and macOS. I confirmed that it was being recognised, but when my client pressed a key, no MIDI data was being sent into Logic. An unusual problem.
We started with a few basic troubleshooting steps, such as reconnecting the USB and testing the connection by swapping USB cables. Neither made a difference.
I downloaded the free and excellent MIDIPipe software to remove Logic as a variable. MIDIPipe allowed me to view raw MIDI data being set to any port of the Mac and I was able to confirm that no MIDI was coming from the Keystation. Since Logic and MIDIPipe were showing the same results, this indicated that something was wrong with the keyboard itself.
I downloaded the manual to access the codes for the Advanced Function keys and I talked my client through the button and key combinations to access the MIDI on/off features. After testing more variables using the Advanced Functions, we ran the Factory Reset combination and MIDIPipe suddenly started displaying normal MIDI key press data.
We reopened Logic Pro and confirmed that the MIDI was now working fine. I spent the remainder of the one-hour session by creating written instructions for my client on how to run the factory reset procedure on the Keystation again if the problem came back.
About the Author
I’m the owner and lead technician for Audio Support, a small company based in London, UK that connects remotely with clients worldwide to help them with their music technology issues. I’ve run Audio Support since 2005 and in that time I’ve seen and solved thousands of recording studio problems.
Outside of Audio Support, I run music workshops at a local school, play bass in a 90s tribute function band and perform modular synth jams with friends on Twitch.
Get support for similar problems:
More Logic Pro problems solved
- Allowing PreSonus Drivers in OSX Security Preferences
- Moving Sample Libraries to Improve Logic Pro Loading Speeds
- Diagnosing Slow Loading Problems in Logic Pro
- Visiting a Guitarist to Help With His Logic Pro Recording Setup
- Lesson on Using Automation in Logic Pro
- Komplete Kontrol Missing Presets in Logic Pro
- Explaining the MIDI options when setting up an Arturia Keylab Essential 61 as a control surface in Logic Pro
- Creating a Custom Project Template for Guitar Recording in Logic Pro
- Audio Unit Crashes in Sonoma 14.4.1 – Resolved by 14.5 Update?
- Audio Recording Delayed in Logic Pro – Solved
- Three Methods to Improve Logic Pro’s Performance on an Older iMac
- Sample Rate Problems Using an Audient ID24 and ASP800 in Logic Pro – Solved
- Pitch Changes Randomly Occurring on Logic Pro Synths – Solved
- M-Audio Keystation 88 II not sending MIDI to Logic Pro – Solved
- Problems setting up an SPL Transient Designer as an I/O effect in Logic Pro – Solved
- Logic Pro Disk Overload on Mac Mini M2 – Solved
- IK Multimedia AXE I/O Audio Interface Not Working with Logic Pro X – Solved
- Building Custom Vocal Distortion Presets in Logic Pro X
- Evolve Mutations Sample Library Missing in Kontakt – Solved
- Logic Pro playhead stuck at beginning of song
- No sound from certain MIDI regions when assigning sounds to Native Instruments Kontakt
- Restoring slowed down audio regions in Logic Pro
- Installing Spitfire and Toontrack plugins
- Logic Pro X not opening – ‘Bundle Error’ – solved
- AKAI MPK249 Pitch wheel problem fixed
- Installing Antares Auto-Tune and Vocodist
- Locating missing files in Kontakt
- Logic Pro solo function not working with an analogue summing mixer
- Diagnosing problems with USB hubs
- Transferring MIDI song files from Logic to an FA06 keyboard
- Diagnosing noise problems with Yamaha FX550 effects box
- Installing Antares Auto-Tune Pro X
- Diagnosing issues with noise in vintage effects boxes