Differences

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

--- playground:ios_core_midi_connections_explained [2019/05/13 11:08] – ↷ Page moved from sandbox:ios_core_midi_connections_explained to playground:ios_core_midi_connections_explained wim
+++ playground:ios_core_midi_connections_explained [2019/05/13 12:45] – [Types of connections] wim
@@ Line 2: / Line 2: @@
 It can be confusing understanding how to connect apps via MIDI in iOS. This article attempts to explain the concepts, common misconceptions, and troubleshooting techniques. The article is mainly focused on connections //between// apps, but also has a section about MIDI concepts within some common hosts.
-  NOTE: This article is mainly concerned with Host and IAA apps. The rise of AUv3 apps has thankfully simplified MIDI routing a lot within hosts so not as much needs to be said.
+<WRAP box>
+NOTE: This article is mainly concerned with Host and IAA apps. The rise of AUv3 apps has thankfully simplified MIDI routing a lot within hosts so not as much needs to be said.
+</WRAP>
 (Work in progress)
@@ Line 17: / Line 19: @@
 === App to App ===
 == Ports and Virtual Ports ==
-The most important concept to understand when connecting apps is that of virtual MIDI ports. These the ways apps identify MIDI end points. Virtual ports that send MIDI out are //source// ports, those that receive MIDI are //destination// ports. Some apps name source or destination ports differently, most don’t.
+The most important concept to understand when connecting apps is that of virtual MIDI ports. This is how apps identify MIDI end points. Virtual ports that send MIDI out are //source// ports, those that receive MIDI are //destination// ports. Some apps name source or destination ports differently, most don’t.
 Hardware, BlueTooth, and the Network session are ports as well. They can be senders, receivers, or both, depending on the hardware or apps using them.