MIDI

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

MIDI itself, which stands for "Musical Instrument Digital Interface", is just a protocol and standard for communication between musical instruments and any device that understands the language. It can be used to control an array of synthesizers, make a tin can sound like a drum, or even operate industrial equipments.

The scope of this article, however, will mainly focus on the usage of MIDI in computer systems for playback of files that contain MIDI data. These files usually come with the .mid extension, and were hugely popular in the golden days of multimedia computing to share music. In professional music composition/arrangement, it still plays a vital role.

MIDI file

Without going into the details of what the format is composed of, you just need to understand that a MIDI file eg. foobar.mid does not contain any digital audio data, hence no "PCM stream". It is a common misconception that MIDI is a sound file format, and as such you usually see people complaining that music players like Amarok cannot play the file. Here is a very newbie-friendly outline of what a MIDI/MID file contains:

# FOOBAR.MID
Note ON
  Use Instrument #1
  Play Note C1
  Set Volume at 100
  Set Pitch at 50

In order for such a file to be useful, there needs to be an "engine" that can translate the data to music. This engine will have a "tone generator", and this is what we call a "synthesizer". So any player that can play back a MIDI file without MIDI-capable hardware (your computer's sound device), has a synthesizer built-in or uses an external one. A typical keyboard (not the thing you are typing on) is actually made up of two components - a MIDI "controller" (the keys) and a synthesizer (tone generator/module; the thing that makes sound).

So up to this point, you should be able to understand that:

There needs to be a synthesizer to play a MIDI file.
A synthesizer can be hardware or software.
Most computer soundcards/chipsets do NOT have synthesizers.
You need a synthesizer with a proper "bank" (collection of sounds) to be able to enjoy all the glory of MIDI files.
If a certain instrument is not in the bank, your synthesizer will not play anything for notes using that instrument.
If a certain instrument in the file corresponds to a different one in the bank, your synthesizer will play a different sound (obviously).

GM Bank

General MIDI (GM) is a specification to standardise numerous MIDI-related matters, particularly that of instruments layout in a collection of sounds. A "soundbank" which is GM-compatible means that it meets the criteria of General MIDI, and as long as the MIDI file is also GM-compatible (as in nothing extraordinary is defined - such as introducing a new instrument or having one in a different location of the bank), the playback will be as intended since the bank has the correct instrument/handler for the MIDI message/event. One of the most popular soundbank formats is that of SoundFont, particularly SF2.

If you have a soundcard which can make use of soundfonts, you can load a .sf2 file onto it.

If you do not have a soundcard which can make use of soundfonts (basically no hardware synthesizer), you can use a software synthesizer and load the SF2 file. In turn, you can find some way to globally make use of this synthesizer.

Playback

"Why can I play MIDI with Windows Media Player, then?"

Well, because Windows has a default software synthesizer which acts globally. Even then, it lacks the quality which should be expected of modern computers. If there were a way to do it on Linux, you would be able to play back MIDI from any player too. Perhaps a MIDI server (which will hold a synthesizer of choice like timidity++ or fluidsynth) that sits within the sound server, like Phonon or PulseAudio. Nevertheless, nothing of this sort has been implemented and you can only play MIDI with a player, or sound server, that has a plug-in to source a synthesizer, or has a synthesizer itself. For example audacious.

Hardware

(More details on soundcards and MIDI, possibly links to SBLive MIDI here...)

If you simply need to play a MIDI file on a MIDI-capable hardware device (e.g. a hardware synthesizer), you can use the aplaymidi command. To get the list of the available MIDI ports use the command

$ aplaymidi -l

Then to play a MIDI file specify it along with an available port of the preferred MIDI device that you got from the output of the previous command, for example like this:

$ aplaymidi -p 24:0 midi_file.mid

SB Audigy 1 - Emu10k1 WaveTable

First, make sure that the Synth mixer control is not muted and that Audigy Analog/Digital output Jack is set to [Off].

To check and adjust them, use alsamixer or your mixer of choice.

Next, build and install the awesfx^AUR package from the AUR. Then, load a SoundFont file on the Emux WaveTable, like so:

$ asfxload /path/to/any/file.sf2

The .SF2 file can be any SoundFont. If you have access to 2GMGSMT.SF2 on Windows, you can use that one.

You should be all set now. To play your .mid files with aplaymidi, you will have to do as follows:

Get a list of the available MIDI ports by running

$ aplaymidi -l

Sample output:

Port    Client name                      Port name
14:0    Midi Through                     Midi Through Port-0
28:0    SB Live! 5.1 [SB0060]            EMU10K1 MPU-401 (UART)
29:0    Emu10k1 WaveTable                Emu10k1 Port 0
29:1    Emu10k1 WaveTable                Emu10k1 Port 1
29:2    Emu10k1 WaveTable                Emu10k1 Port 2
29:3    Emu10k1 WaveTable                Emu10k1 Port 3

Then, pick an available "Emu10k1 WaveTable" MIDI port, in this case 29:0, and specify it as such:

$ aplaymidi -p 29:0 midi_file.mid

Software

DeaDBeeF

You can play MIDI files in deadbeef^AUR player after installing and configuring freepats.cfg which is provided by freepats-general-midi. See Timidity#Freepats. You can also change the freepats.cfg file location in DeaDBeeF by going to Edit > Preferences > Plugins > WildMidi Player > Configure.

GStreamer-based players

You can play MIDI files on GNOME Videos and all other players using GStreamer as backend after having installed gst-plugins-bad and fluidsynth, and installed a soundfont (soundfont-fluid for example). See FluidSynth for more info.

If you choose to use soundfont-fluid, the default search strategy will probably select FluidR3_GS.sf2 rather than FluidR3_GM.sf2. There can be no audio if that's the case. To prevent this, you can use a symlink:

# mkdir -p /usr/share/sounds/sf2/
# ln -s ../../soundfonts/FluidR3_GM.sf2 /usr/share/sounds/sf2/FluidR3_GM.sf2

VLC

You can play MIDI files on VLC if you configure the location of the Sound Font file. Previously you need to install a sound sample, as well as the fluidsynth and vlc-plugin-fluidsynth-bin^AUR package (without the latter, the audio codec will not appear in the preferences).

In VLC choose Tools > Preferences: you have to show all settings. Then, go to Input/Codecs > Audio codecs > FluidSynth.

And, if you installed e.g. fluidr3 as wiki says, set the location to:

/usr/share/soundfonts/FluidR3_GM.sf2

Note:

Read the mailing list thread about merging fluidr3 with soundfont-fluid.
Fluidsynth support is not included in the vlc package, however it is included in vlc-git^AUR, or can be added with vlc-plugin-fluidsynth-bin^AUR

Audacious

audacious has a built-in MIDI synthesizer which makes it essentially the easiest way to play a MIDI file with no extra setup. You can specify the soundfont to use for playback in the settings of its MIDI output plugin (File > Preferences > Plugins > Input > AMIDI-Plug > Preferences). As such the only prerequisites you need is the player and a soundfont file.

TiMidity++

MIDI to WAVE converter and player. See TiMidity++.

FluidSynth

MIDI player and a daemon adding MIDI support to ALSA. See FluidSynth.

Drumstick

Drumstick MIDI File Player is capable to play MIDI files. Install dmidiplayer^AUR.