QMIDIROUTE(1)

πŸ‘‘ QMIDIROUTE(1) β€” the manual page, but make it fashion

okay bestie, pull up a chair, we're reading the qmidiroute man page together and honestly? it's giving main character energy πŸ’… this is section 1 of the General Commands Manual, so it's a user command, not some dusty kernel thing. no cap.


✨ NAME ✨

qmidiroute β€” a 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. Periodt.

So here's the tea: qmidiroute lets you set up an unlimited number of MIDI maps, and in each one, incoming events get selected, modified, or even changed in type before being directed to a dedicated ALSA output port. The maps work in parallel, and they're organized in tabs. With qmidiroute you can, for example, change or invert the scale of a keyboard, transform keyboard strokes into program changes, or turn controller data into notes. literally iconic behavior πŸ”₯

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. iykyk.

πŸŽ€ 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. Logging can also be disabled generally, or for MIDI Clock events only. the way she organizes everything?? obsessed 🫢

πŸ¦‹ 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. bump it up bestie, go wild πŸ‘‘
  • --help β€” print possible command-line options and exit. your little helper πŸ₯Ί
  • --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. cute and readable, we love her πŸ’œ

🌈 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). yeah she yells into the void, that's just how it is πŸ™ˆ


🫢 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>.


and that's the whole page bestie, no skips, no crumbs left behind 🧚✨ this was dated 2009-09-13 and it lives in section 1 of the General Commands Manual β€” the QMIDIROUTE(1) of it all. slay, bye πŸ’…πŸ’–