This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
playground:ios_core_midi_connections_explained [2019/05/13 12:47]
wim [Types of connections]
playground:ios_core_midi_connections_explained [2019/05/13 13:19]
wim [Common Misconceptions]
Line 41: Line 41:
 ===== Common Misconceptions ===== ===== Common Misconceptions =====
-Certain things about Core MIDI are unintuitive (to some people). Getting past these also helps to reduce problems.+Certain things about Core MIDI are unintuitive to some people. Getting past these also helps to reduce problems. 
 +**Each app should be pointed to the other** 
 +It seems natural when connecting two apps to set the second as the output in the first app, and the first as the input in the second app. **//But this is wrong//**. Remember about virtual ports? Let’s say App A has a virtual port called “App A MIDI” and App B has one called “App B MIDI”. If App A is sending to App B MIDI port, then generally App B will not need any setting at all. But, if it does, it needs to be set to listen to **//its own//** virtual MIDI port, which is actually named App B MIDI. On the other hand, if App A just sends out MIDI over its own virtual MIDI port, then App B should be set to listen to the port named App A. 
 +So, the basic rule of thumb is: **//If you have to make settings in both apps, make sure the port is the the same in both apps.//** For example, if sending to Gadget from AUM, set AUM’s output to Gadget, and Gadget’s input to Gadget. Or, if sending KB-1 to AUM, you might set KB-1 to Virtual Output (KB-1’s own Virtual Midi port). In this case, you would set AUM to listen to KB-1. 
 +** Misconception #2 **
 ==== “From” and “To” connection confusion ==== ==== “From” and “To” connection confusion ====
  • playground/ios_core_midi_connections_explained.txt
  • Last modified: 2019/05/13 13:26
  • by wim