Subversion Repositories svn.mios


Blame | Last modification | View Log | RSS feed

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
<TITLE>MIDI Device Routing</TITLE>
<LINK REL="stylesheet" TYPE="text/css" HREF="standard.css">
<BODY bgcolor="#ffffff" text="#000000" link="#0000ff" vlink="#000066" alink="#0000ff">
<CENTER><H1>MIDI Device Routing</H1></CENTER>
<p>The MIDI Device Routing window allows you to forward and filter MIDI streams to any MIDI port. At the top of the list you will always find the virtual 'In' and 'Out' ports. These are the ports to which MIDI data has to be routed when you want to send messages, monitor ports, etc.</p>

<p><img src="images/routing.png"></p>

<p>On the left hand side the 'readable' MIDI ports are listed. Readable ports are MIDI devices that data can be read from such as physical MIDI In ports, virtual software MIDI In ports and the virtual Out port that is used by all components of the program to send MIDI data.

<p>On the right hand side the 'writeable' MIDI ports are listed. Writeable ports are MIDI devices that data can be sent to such as physical MIDI Out ports, virtual software MIDI Out ports and the virtual In port that is used by all components of the program to receive MIDI data.

<p>Multiple connections can be routed between ports, and all connection can be seperately <a href="midi_filter.html">filtered</a>. Selecting two connected MIDI ports and clicking the Filter button will bring up the MIDI Filter dialog.

<p>Ports can be connected/disconnected/filtered by either: 'dragging and dropping' one port on to another; right-clicking on a port and selecting another port on the pop-up menu; highlighting a port from either list and using the buttons below.

<ul class="cl">
    <li><b>Connect: </b>Connects the two selected ports if they are not already connected<br><br></li>
    <li><b>Disconnect: </b>Disconnects the two selected ports if they are connected<br><br></li>
    <li><b>Disconnect All: </b>Disconnects all ports<br><br></li>
    <li><b>Rescan Devices: </b>Checks for any hardware changes (eg: A USB MIDI device has just been plugged in)<br><br></li>
    <li><b>MIDI-Thru: </b>Enables MIDI-Thru. Any messages received by the virtual In port are automatically forwarded to the virtual Out port<br><br>
            <li><b>Filter: </b>Filters the MIDI-Thru connection<br><br></li>
            <li><b>Map: </b><br><br></li>
    <li><b>Release Ports: </b>Allows the program to release it's access to the system's MIDI ports. Many MIDI devices are not multi-client capable which means that only one program can access the ports at a time. Releasing the ports will allow another program to be opened and have access to the system's MIDI devices.<br><br>

    Note: Connections between MIDI ports can still be routed, filtered and mapped while the ports are released. When the 'Release Ports' button is disengaged, the MIDI ports will be opened and connected, mapped and filtered.<br><br><img src="images/routing_released.png"></li>