Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

qmidiroute(1) [debian man page]

QMIDIROUTE(1)						      General Commands Manual						     QMIDIROUTE(1)

NAME
qmidiroute - MIDI event processor and router SYNOPSIS
qmidiroute [OPTION] [file] qmidiroute { --help | --version } DESCRIPTION
qmidiroute is a versatile MIDI event processor and router for the ALSA sequencer. The graphical interface is based on the Qt4 toolkit. qmidiroute permits setting up an unlimited number of MIDI maps in which incoming events are selected, modified or even changed in type before being directed to a dedicated ALSA output port. The maps work in parallel, and they are organized in tabs. With qmidiroute it is for example possible to change or invert the scale of a keyboard, to transform keyboard strokes into program changes or controller data into notes. Incoming MIDI events can be logged in a list and are displayed in different colors according to their MIDI type. qmidiroute provides one ALSA input port and as default two ALSA output ports. The numerical ALSA client id is displayed as part of the window title. General Usage After starting the application, the Unmatched tab is presented (see below). To start MIDI routing setup, the New map... button can be clicked, which will create a new MIDI map appearing as a tab in the map area. The entire setup can be saved to and loaded from a QMidiRoute file (.qmr). Several maps can be created to work in parallel. The maps can be organized using the Map Rename, Remove and Clone buttons. The Event Log is displayed in the bottom area by default, but can be hidden if not needed or floated as a top-level window on the desktop. Log- ging can also be disabled generally or for MIDI Clock events only. MIDI Input The Input field represents the incoming event filter of each map. Handled event types are Note, Controller, Pitchbend and Program Change. The events can be filtered by their respective values or by MIDI channel. Events matching the conditions specified in the Input field are directed to the Output field. MIDI Output The Output field sets terms into which event type the matching events are transformed, how their channel and values are transformed, and to which ALSA port they are directed. Channels and Values can be set Fixed, Offset or Reverse Offset with respect to the input event. As an example, Reverse Offset will take the value specified and subtract the incoming event value from it to produce the output event value. If the output range for a value is different from its input counterpart, the input range will be smoothly scaled to the output range. Events will be sent to the ALSA port specified. The number of available ALSA ports can be set using the corresponding command-line option. Unmatched MIDI events In the Unmatched tab, the handling of events not matching any input filter of the defined maps is specified. These events can be discarded or sent to a specified ALSA port. OPTIONS
--portCount <num> Set the number of available ALSA output ports to <num>. The default is 2. --help Print possible command-line options and exit. --version Print version information and exit. file Name of a valid QMidiRoute (.qmr) file to be loaded on start. FILES
*.qmr QMidiRoute files containing MIDI routing data in plain text format. EXAMPLES
An example MIDI map file can be found in /usr/share/qmidiroute or in /usr/local/share/qmidiroute NOTES
Errors and warnings are written to stderr(3). SUPPORT
alsamodular-devel@lists.sourceforge.net AUTHORS
Matthias Nagorni, Frank Kober and Guido Scholz. This manual page was written by Frank Kober <emuse@users.sourceforge.net>. 2009-09-13 QMIDIROUTE(1)

Check Out this Related Man Page

aseqnet(1)						      General Commands Manual							aseqnet(1)

NAME
aseqnet - ALSA sequencer connectors over network SYNOPSIS
aseqnet [remotehost] DESCRIPTION
aseqnet is an ALSA sequencer client which sends and receives event packets over network. Suppose two hosts connected by network, hostA as a server and hostB as a client. The ALSA sequencer system must be running on both hosts. For creating the server port, run the following on hostA: hostA% aseqnet sequencer opened: 128:0 Then a user client 128 with port 0 was opened on hostA. (The client number may vary.) For creating the (network-)client port, run aseqnet with the hostname of the server: hostB% aseqnet hostA sequencer opened: 132:0 Now all events sent to hostA:128:0 are transferred to hostB:132:0, and vice versa. The ports created by aseqnet can be connected arbitrary to other sequencer ports via aconnect(1). For example, to connect hostB:132:0 to a MIDI output device 65:0: hostB% aconnect 132:0 65:0 Then events to hostA:128:0 will be delivered to hostB:65:0. The following command plays MIDI on hostB. hostA% pmidi -p 128:0 foo.mid The multiple clients may exist simultaneously. If hostC is connected as a client to hostA, events from from hostA are sent to all con- nected network clients, i.e. hostB and hostC. However, only one connection is allowed from a client to a server. To disconnect network, stop all clients before server by ctrl-C or sending signal to them. The server will automatically quit. OPTIONS
-p port Specify the TCP port number or TCP service name. -s addr Subscribe to the given address for read automatically. -d addr Subscribe to the given address for write automatically. -v Verbose mode. SEE ALSO
aconnect(1), pmidi(1) AUTHOR
Takashi Iwai <tiwai@suse.de>. January 1, 2000 aseqnet(1)
Man Page