Solution dysamoria Posted December 29, 2019 Solution Share Posted December 29, 2019 Public service announcement! Just in case anyone comes looking around here like I did... If you're using Logic and the IAC MIDI driver to send MIDI from Logic to another app (maybe to control a WINE-hosted Windows VST synth, in my case), you will probably encounter problems with MIDI loopback. It may sound like insanely loud playback, with hung notes, insanely duplicated notes, crashing software, etc. This is because Logic is sending MIDI out to the IAC driver AND listening to the same port for incoming MIDI data. The solution for me was to go to Logic's Preferences -> MIDI -> Inputs, and disable/uncheck the IAC MIDI ports in the list of MIDI Input ports. I knew there must be a loopback, but didn't know where to find the settings or the specific causation. Then I stumbled onto it, remembering that Logic treats MIDI ports more globally than some other DAWs (I came from Cakewalk Sonar, years ago, where in/out MIDI ports were configured per track). Once I found the appropriate preference area, BAM, an hour of troubleshooting ended in a couple clicks. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted December 29, 2019 Share Posted December 29, 2019 Cool. We used to solve this by cabling the IAC port from the Physical Input object (MIDI Click and Ports layer of the MIDI Environment) into a dead end, for example a Monitor object, which would subtract it from the SUM input that is cabled into the Sequencer input: viewtopic.php?t=10161 Quote Link to comment Share on other sites More sharing options...
dysamoria Posted December 29, 2019 Author Share Posted December 29, 2019 Cool. We used to solve this by cabling the IAC port from the Physical Input object (MIDI Click and Ports layer of the MIDI Environment) into a dead end, for example a Monitor object, which would subtract it from the SUM input that is cabled into the Sequencer input: viewtopic.php?t=10161 Oh! Thanks for mentioning that. Is that a better method for any reason that I might benefit from? Quote Link to comment Share on other sites More sharing options...
fuzzfilth Posted December 29, 2019 Share Posted December 29, 2019 Well, who knows. In any case, mute-able MIDI Inputs are quite new, so David told you what worked for the past 15 (?) years. Also, muted MIDI Ins are global, routing an IAC bus to a dead end is per project, so that may determine which method to choose. Quote Link to comment Share on other sites More sharing options...
dysamoria Posted December 30, 2019 Author Share Posted December 30, 2019 Thanks for confirming the difference between these methods. It sounded like the difference was per project or global. In my current usage situation, global works well for me. I was just wondering if there’s a situation where that would be problematic and therefore maybe I ought to also get used to editing the environment objects for this. I don’t currently need to have Logic receive inter-app MIDI. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted December 30, 2019 Share Posted December 30, 2019 I would continue your method unless you're getting issues with it; but I can't think of why it would be problematic. Quote Link to comment Share on other sites More sharing options...
dysamoria Posted December 31, 2019 Author Share Posted December 31, 2019 Thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.