Differences

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

--- midi [2015/06/24 02:57]
slackermedia
+++ midi [2021/06/03 19:48] (current)
@@ Line 1: / Line 1: @@
-n[[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}slackbuilds|]]
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}jack|]]
 ====== MIDI ======
@@ Line 26: / Line 24: @@
 Simple as that.
+==== Three Types of MIDI Ports ====
+There are three types of MIDI ports: In, Out, and Through (sometime abbreviated to "Thru"). They each have specific functions. On any given MIDI-capable unit (where a "unit" might be a synth, or sequencer, or sampler, or FX box, MIDI USB interface, MIDI patchbay, and so on):
+  * **MIDI Out** sends MIDI data //generated by that unit//. This is an important distinction; the MIDI Out port **never** sends "left-over" data that the unit has received in its MIDI In port.
+  * **MIDI In** accepts MIDI data generated by something else. Whether or not the unit //listens// to that data, and which channel the unit listens on, is up to the user.
+  * **MIDI Thru** indiscriminately echoes everything received from the MIDI In port.
+As an example, a likely MIDI setup might have an Emu sequencer programmed with the parts for several different instruments. Each instrument is defined by a MIDI channel. A cable is connected to the sequencer's **Out** port, to a Korg's **In** port. The Korg listens in on channel 1 and plays the part found there. A cable connected to the Korg's **Thru** port takes all the MIDI data (channel 1 inclusive) and sends it to a Roland, the next synth in line. The Roland listens for channel 2 and plays whatever it finds there. A cable connected from the Roland's **Thru** port sends all data (channels 1 and 2 inclusive) to an Alesis drum machine, which listens to channel 3 and plays that.
+Notice that **MIDI Out** was only used once in this example, and the bulk of the transport layer consists of **In** and **Thru**.
 ===== Computer Implementations of MIDI =====
-This worked out so well for the synth world that when computers started taking over the world of electronic music, MIDI was actually reimplemented internally rather than replaced with something new. So anything you know from your experience with hardware synths (or from what you have read about it) applies directly to computer music. The only difference is that the synths are now just applications, and the cables are made of pixels.
+MIDI worked out so well for the synth world that when computers started taking over the workload of electronic music, MIDI was reimplemented internally rather than replaced with something new. Anything you know from your experience with hardware synths, or from what you have read about it, applies directly to computer music. The only difference is that the synths are now applications, and the cables are virtualised and made of pixels.
-For example, if you have a sequencer software (such as [Qtractor] or [Muse] or [[http://www.filter24.org/seq24/download.html|seq24]), then you can create tracks in your workspace and assign each track an individual MIDI channel. When you press **Play**, all MIDI data gets sent from your sequencer to anything listening. Using the [[jack|JACK]] routing system, connect soft synths set to //listen// on some MIDI channel, and, just that quickly, you're making music!
+For example, if you have a sequencer software (such as [[Qtractor]] or [[Muse]] or [[seq24]), then you can create tracks in your workspace and assign each track an individual MIDI channel. When you press **Play**, all MIDI data gets sent from your sequencer to anything listening. Using the [[jack|JACK]] routing system, connect soft synths set to //listen// on some MIDI channel, and, just that quickly, you're making music!
 If you want to combine computerised MIDI with traditional MIDI, you can do so with a MIDI interface. These plug in to a computer (usually via USB, but sometimes with IEEE 1394 or "Firewire") and send and receive MIDI data so that you can use hardware synths with a software sequencer, or a hardware sequencer with soft synths, and so on.
-===== MIDI Driver =====
+===== MIDI Driver for JACK =====
 Normally, the internal computer MIDI data is handled by a driver provided by ALSA (the same project responsible for driving sound). This makes some logical sense, since when using MIDI you are probably using MIDI for sound. But with the rise of JACK, MIDI as an ALSA technology became, for most people, a technology ripe for deprecation.
-There are use-cases for ALSA's MIDI driver (for instance, if you are just listening to MIDI files for fun, you would not have any good reason to start JACK) but if you are using DAWs and soft synths and effects, then the MIDI driver you probably want to use is not the ALSA driver because, just as with ALSA sound, ALSA MIDI cannot connect to JACK devices. The two are separate systems; JACK itself uses ALSA, but not interactively. If you are using JACK to make your music, then you should drive MIDI with the ''seq'' driver.
+There are use-cases for ALSA's MIDI driver (for instance, if you are just listening to MIDI files for fun, you would not have any good reason to start JACK, or if you are using [[LMMS]] or [[Ardour]] version 4 or above without JACK) but if you are using DAWs and soft synths and effects, then the MIDI driver you probably want to use is //not// the ALSA driver because, just as with ALSA sound, ALSA MIDI cannot connect to JACK devices.
-The ''seq'' driver is a dynamic bridge that sends and receives MIDI signals with JACK.
+The two are, from the musician's perspective, two separate systems.
+If you are using JACK to make your music, then you should drive MIDI with the ''seq'' driver. The ''seq'' driver is a dynamic bridge that sends and receives MIDI signals with JACK.
 <code>
-$ jackd -X seq
+$ /usr/bin/jackd -R -d alsa -X seq
 </code>
-Launching ''jackd'' with ''seq'' defined as the MIDI driver retains all ALSA MIDI ports (which you probably will not use, but they'll be there just in case) and causes any JACK-aware application that you launch to create a MIDI port for itself within the JACK environment.
+Launching ''jackd'' with ''seq'' defined as the MIDI driver, ''alsa'' as the audio driver, and, as always, the ''--realtime'' (or ''-R'' in shorthand) flag set, retains all ALSA MIDI ports and causes any JACK-aware application that you launch to create a JACK-aware MIDI port for itself.
+When integrating MIDI from the physical world, remember the different types of MIDI ports. If you plug in a USB Midi controller (a piano keyboard with a USB port which sends MIDI signals) to your computer and you want to use it to play a software synth, then in most setups you will connect the MIDI controller to a systemwide Midi Thru port.
+{{ midi2midi.jpg | When using the ''seq'' driver, connect the MIDI Out of your controller to the MIDI Thru of your computer system. }}
-{{ seqmidi.jpg?666 }}
+The MIDI Thru port transports your MIDI signals from the physical world into the MIDI Thru of the virtual studio so that all MIDI data you are generating, regardless of what channel it is destined for, gets passed on to all applications connected. In practise, this means that the ''seq'' bridge takes the MIDI data from your controller (coming in through the ALSA interface), and pipes it into the JACK environment via the **System Capture** MIDI interface (in other words, JACK sees your keypresses as a sort of MIDI-microphone; it captures the input data and makes it available to all JACK applications).
+{{ seqmidi.jpg | An example of routing MIDI and sound with [[patchage]]. }}
+That's your MIDI setup, in a nutshell.
+This has only covered the //network design// of MIDI. The individual clients (your synths, samplers, sequencers, and so on) still must be configured on a per-project basis so that they know what MIDI channel they should be responding to. The **MIDI Thru** is built in, because unlike hardware, you have infinite **MIDI Out** ports on your controller and sequencer.
+<WRAP tip>
+Individual sections of Slackermedia always explain how to route MIDI on a per-application basis.
+</WRAP>
+===== MIDI Driver for ALSA =====
+If you are using a MIDI controller without JACK (ie, [[LMMS]] or [[Ardour]] in ALSA modes), then there is no configuration or routing required on a system level. Your MIDI signal is received by the ALSA MIDI driver, just by nature of how Linux accepts MIDI signals, and it is distributed to all MIDI-capable applications as a, more or less, universal MIDI Thru. As with JACK, it's up to you to set what channel each application responds to from within each application.
+<WRAP centeralign>
+<wrap fa>[[multilib|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[timecode|Q]]</wrap>
+</WRAP>
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}jack|]][[{arrowp.png|border:0;background:none;width:0;float:right;}slackbuilds|]]