MIDI Designer Reference Manual

User Tools

Site Tools

Trace:

Differences

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

Link to this comparison view

manual:03_connections_redux [2023/12/29 21:15] – ↷ Page name changed from manual:connections_redux to manual:03_connections_redux jkhiser-wikimanual:03_connections_redux [2026/05/01 12:11] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Connections (Revised) =======+====== Chapter 3: MIDI Connections =======
  
 <wrap lo>updated Dec 2023 for MD 3.0</wrap> <wrap lo>updated Dec 2023 for MD 3.0</wrap>
Line 36: Line 36:
 For inputs, //Thru// option will echo MIDI input to all connected outputs. For inputs, //Thru// option will echo MIDI input to all connected outputs.
  
-{{ :playground:connectons_examples.png?direct&300 | }} +{{ :manual:connections_examples.png?direct&300 |}}
 ===== USB (Hardware) Connection ===== ===== USB (Hardware) Connection =====
  
Line 73: Line 72:
 Once connected with BT, connections __typically__ reconnect when the device is available. Once connected with BT, connections __typically__ reconnect when the device is available.
  
-{{ :playground:bluetooth_two_step.png }}+{{ manual:bluetooth_two_step.png }}
  
 Note: Bluetooth MIDI connections cannot be initiated from the OS Bluetooth menu, but one active will appear in that menu. Note: Bluetooth MIDI connections cannot be initiated from the OS Bluetooth menu, but one active will appear in that menu.
  
-{{  :playground:bluetooth_status.png?direct&400  |}}+{{  manual:bluetooth_status.png?direct&400  |}}
 ===== Virtual MIDI (Inter App Connections) ===== ===== Virtual MIDI (Inter App Connections) =====
  
 "Virtual" connections provide MIDI between applications internal to a computer.  The connections can be initiated by the programs exchanging MIDI, a separate MIDI routing program, or by the OS. "Virtual" connections provide MIDI between applications internal to a computer.  The connections can be initiated by the programs exchanging MIDI, a separate MIDI routing program, or by the OS.
  
-{{  :playground:virtual_routes.png?direct&400  |}}+{{  manual:virtual_routes.png?direct&400  |}}
  
 MD virtual ports should be preferred, as MD keep alive functionality should keep these ports active when the app is in background.  There may be cases where this is not possible, such as an app that only recognizes its own ports, or more flexibility in routing is desired.  If virtual connections are being dropped, shift back to MD virtual ports. MD virtual ports should be preferred, as MD keep alive functionality should keep these ports active when the app is in background.  There may be cases where this is not possible, such as an app that only recognizes its own ports, or more flexibility in routing is desired.  If virtual connections are being dropped, shift back to MD virtual ports.
Line 88: Line 87:
 Do not enable more than one path between two apps to prevent message duplication. Do not enable more than one path between two apps to prevent message duplication.
  
-{{ :playground:virtual_connections.png?direct&600 |}}+{{ manual:virtual_connections.png?direct&600 |}}
  
 Apps may have different titles for their virtual connections.  DM1 (above) uses generic "Network."  In MD, we see it labeled DM1. Apps may have different titles for their virtual connections.  DM1 (above) uses generic "Network."  In MD, we see it labeled DM1.
Line 102: Line 101:
  
 <WRAP center round important 90%> <WRAP center round important 90%>
-This is my experience doing WiFi testing between MD running on multiple devices.  Do not have a network MIDI hardware device to test against, just iPad, iPhone, and Mac.  Appreciate feedback on user network experiences to update these instructions+These instructions focus on iPhone, iPad and Mac. If you have another Wi-Fi MIDI device, we would appreciate feedback to update these instructions.
 </WRAP> </WRAP>
  
Line 134: Line 133:
 [[https://support.apple.com/guide/audio-midi-setup/share-midi-information-over-a-network-ams1012/mac|Apple reference for Network MIDI configuration]], or press ? in the //MIDI Network Setup// window. [[https://support.apple.com/guide/audio-midi-setup/share-midi-information-over-a-network-ams1012/mac|Apple reference for Network MIDI configuration]], or press ? in the //MIDI Network Setup// window.
  
-{{  :playground:midi_network.png?direct&600  |}}+{{  manual:midi_network.png?direct&600  |}}
  
 ==== Network Notes ==== ==== Network Notes ====
Line 142: Line 141:
     - The initiating Mac can be shut down without impact.       - The initiating Mac can be shut down without impact.  
     - Once stable, it seems as solid as BT connections, but it can make you crazy trying to get it initially established     - Once stable, it seems as solid as BT connections, but it can make you crazy trying to get it initially established
-  * The WIFI connections panel may show an entry for the current device.  If this is selected, then you are echoing MIDI data back to that instance of MD, a MIDI feedback loop.  In most cases, this is not an issue, but occasional setups could have a problem.  I don't have a reliable way to replicate this "self" entry. +  * The WIFI connections panel may show an entry for the current device (self).  If this is selected, then you are echoing MIDI data back to that instance of MD, a MIDI feedback loop.  In most cases, this is not an issue, but occasional setups could have a problem.  I don't have a reliable way to replicate this "self" entry. 
-  * Theory - as long as a single device retains knowledge of the MIDI network, it remains available, and you do not have to restart the network on the Mac.  I have powered down all devices, restarted, and reconnected just by tapping the device names in the //WIFI Connections// box.  At some point, the network is lost, and you have to start at the beginning.+  * Theory - as long as a single device retains knowledge of the MIDI network, it remains available, and you do not have to restart the network on the Mac.  I have powered down all devices, restarted, and reconnected just by tapping the device names in the //WIFI Connections// box.  At some point, the network is lost, and you have to start at the beginning.  iDevices are more robust than Macs at retaining the network.
   * Network MIDI does not have separate options for input and output, joining a network enables both channels   * Network MIDI does not have separate options for input and output, joining a network enables both channels
   * Network MIDI does not have Thru option (unneeded, since you can connect directly to any device on the network, not like DIN MIDI days where you would have a serial string)   * Network MIDI does not have Thru option (unneeded, since you can connect directly to any device on the network, not like DIN MIDI days where you would have a serial string)
Line 179: Line 178:
 ===== Connection Troubleshooting ====== ===== Connection Troubleshooting ======
  
-If MD Connections menu shows a connection, but the target is not responding, use the MD log to verify the inbound and outbound messages.  A stand alone MIDI log can also help - are messages getting to the computer, but not to MD.+If MD Connections menu shows a connection, but the target is not responding, use the MD log to verify the inbound and outbound messages.  A stand alone MIDI log can also help - are messages getting to the computer, but not to MD (see some logger program recommendations below). 
 + 
 +Some thoughts: 
 +  * Configure the target device to transmit MIDI 
 +  * Move a control that transmits, or play a note 
 +  * Does MD log show a received message? 
 +  * If not, try a stand alone MIDI monitor program?  Does it show a message received? 
 +  * Do you have another device in your rig that indicates successful transmission?  Another sound module to sound a note? Etc?
  
 If you are having connection difficulty with a specific target, we recommend starting with the target device forums or support to see if other users have a similar issue and have found a solution.  MD MIDI connections have proven robust over more than a decade of maturation.  With the large number of unique MIDI devices available, it is difficult for us to troubleshoot individual unique configurations. If you are having connection difficulty with a specific target, we recommend starting with the target device forums or support to see if other users have a similar issue and have found a solution.  MD MIDI connections have proven robust over more than a decade of maturation.  With the large number of unique MIDI devices available, it is difficult for us to troubleshoot individual unique configurations.
Line 215: Line 221:
 //Snoise// [[https://www.snoize.com| MIDI Monitor]] - MacOS MIDI Log, a good SysE Librarian is also available //Snoise// [[https://www.snoize.com| MIDI Monitor]] - MacOS MIDI Log, a good SysE Librarian is also available
  
-{{:playground:rip-1817982047.png?direct&100|}}+//Protokol// [[https://hexler.net/protokol| MIDI/OSC Monitor]] - free monitor for MIDI, OSC, and more 
 + 
 +{{manual:rip-1817982047.png?direct&100|}}
  
 MusicIO MusicIO
manual/03_connections_redux.1703902557.txt.gz · Last modified: (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki