Difference between revisions of "Timidity"

From ArchWiki
Jump to: navigation, search
m (Fluidr3)
(9 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[Category: Audio/Video (English)]]
+
[[Category:Audio/Video]]
{{i18n|Timidity}}
+
Timidity++ is a [[Wikipedia:software synthesizer|software synthesizer]] that can play MIDI files without a hardware synthesizer. It can either render to the sound card in real time, or it can save the result to a file, such as a PCM .wav file.
timidity++ is a MIDI to WAVE converter and player which is basically used to play MIDI files if your sound card does not support the MIDI protocol natively.
+
  
==Installing timidity++==
+
== Installation ==
The first step is to install timidity++ itself. It can be installed via pacman from the [[Pacman#Repositories|extra repository]]:
+
[[Pacman|Install]] the {{Pkg|timidity++}} package from the [[Official repositories]].
# pacman -S timidity++
+
  
'''However, timidity++ will not produce any sound yet'''. This is because timidity++ does not include any instrument samples. To produce sound, instrument patches and/or soundfonts need to be installed and timidity++ configured so it knows where to find them. This guide shows two ways of getting sound samples: [[Timidity#Freepats|Freepats]] and [[Timidity#Soundfonts|soundfonts]].
+
You should also install a [[Wikipedia:Soundfont|soundfont]] to be able to produce sound. Here is a list of soundfonts:
 +
* {{Pkg|timidity-freepats}} from the [[Official repositories]].
 +
* {{AUR|fluidr3}} from the [[AUR]]
  
==Setting up the sound samples==
+
== Configuration ==
 +
=== Soundfonts ===
 +
Configure your choosed soundfont:
 +
==== Freepats ====
 +
The [http://freepats.zenvoid.org/ Freepats] project provides a set of instrument samples which are compatible with timidity++.
  
===Freepats===
+
To use Freepats with timidity, add the following lines to {{ic|timidity.cfg}}:
The [http://freepats.zenvoid.org/ Freepats] project provides a set of instrument samples which are compatible with timidity++. It can be installed from the [[Pacman#Repositories|community repository]]:
+
# pacman -S timidity-freepats
+
  
To use Freepats with timidity, add the following lines to /etc/timidity++/timidity.cfg:
+
{{hc|/etc/timidity++/timidity.cfg|
 
+
<pre>
+
 
dir /usr/share/timidity/freepats
 
dir /usr/share/timidity/freepats
 
source /etc/timidity++/freepats/freepats.cfg
 
source /etc/timidity++/freepats/freepats.cfg
</pre>
+
}}
  
Then timidity++ is ready for use.
+
==== Fluidr3 ====
 +
There are other soundfonts available. This will show how to install the {{AUR|fluidr3}} soundfont.
  
===Soundfonts===
+
Now we have to add its path to the timidity++ configuration file. Just add this line:
There are many soundfonts available. This example will show how to install the fluidr3 soundfont, which is accessible via the [[AUR]].
+
:'''Note:''' It will be assumed that you know how to build packages from the AUR. If you have never used the AUR before, please take a look at the [[AUR_User_Guidelines|AUR User Guidelines]].
+
  
As sfarkxtc, a decompressor for soundfonts, is a make dependency of fluidr3, we install it first. Notice that it is accessible via the [[AUR]].
+
{{hc|/etc/timidity++/timidity.cfg|
 +
soundfont /usr/share/soundfonts/fluidr3/FluidR3GM.SF2
 +
}}
  
After sfarkxtc has been installed, we will be able to build fluidr3 which may take some time.
+
=== Daemon ===
 +
Start and configure to autostart the {{ic|timidity.service}}. Read [[Daemons]] for more details.
  
If fluidr3 has been installed properly, we have to add its path to the timidity++ configuration file. Just add this line to /etc/timidity++/timidity.cfg:
+
If you are using [[PulseAudio]], that may not work. You may want to add the following command as an auto start program in your desktop environment. Or, if you just want to start timidity in daemon mode once, you can use the following command which will make console output viewable:
soundfont /usr/share/soundfonts/fluidr3/FluidR3GM.SF2
+
  
Then timidity++ is ready for use.
+
{{bc|$ timidity -iA}}
 
+
==How to use timidity++==
+
 
+
===Convert files===
+
timidity++ can also convert MIDI files into other formats. The following command converts a MIDI file into a WAV file:
+
$ timidity input.mid -Ow -o out.wav
+
  
 +
== Usage ==
 
===Play files===
 
===Play files===
 
There are two ways to use timidity++. Either as MIDI player or as daemon adding MIDI support to [[ALSA]].
 
There are two ways to use timidity++. Either as MIDI player or as daemon adding MIDI support to [[ALSA]].
Line 48: Line 44:
 
====Standalone mode====
 
====Standalone mode====
 
You can simply use timidity++ to play MIDI files:
 
You can simply use timidity++ to play MIDI files:
$ timidity example.midi
+
{{bc|$ timidity example.midi}}
  
Add option -in or -ig for a text mode/gtk+ interface. E.g. as a Xfce/GNOME user you may want to set MIDI files to open with the custom command `timidity -ig'. There are many other options to timidity; see manpage or use -h to get help.
+
Add option {{ic|-in}} or {{ic|-ig}} for a text-based/gtk+ interface. E.g. as a Xfce/GNOME user you may want to set MIDI files to open with the custom command {{ic|timidity -ig}}. There are many other options to timidity; see {{ic|man timidity}} or use {{ic|-h}} to get help.
  
 
====Daemon mode====
 
====Daemon mode====
Timidity can run as a daemon (ALSA sequencer client) providing MIDI output support for other programs such as rosegarden, aplaymidi, vkeybd, etc.
+
If you are runing timidity as a [[#Daemon]] (ALSA sequencer client), it will provide MIDI output support for other programs such as rosegarden, aplaymidi, vkeybd, etc.
 
+
To do this (if you are not using PulseAudio):
+
 
+
# rc.d start timidity++
+
 
+
Add timidity++ to your daemon list in /etc/rc.conf to have permanent MIDI support:
+
 
+
DAEMONS=(... timidity++ ...)
+
 
+
If you are using PulseAudio, above methods may not work, you may want to add following command as an auto start program in your desktop environment. Or if you just want to start timidity in daemon mode once, you can use the following command which will make console output viewable:
+
 
+
$ timidity -iA
+
  
 
This will give you four output software MIDI ports (in addition of hardware MIDI ports on your system, if any):
 
This will give you four output software MIDI ports (in addition of hardware MIDI ports on your system, if any):
 
+
{{hc|$  aconnect -o|<nowiki>
$  aconnect -o
+
client 128: 'TiMidity' [type=user]
client 128: 'TiMidity' [type=user]
+
    0 'TiMidity port 0 '
    0 'TiMidity port 0 '
+
    1 'TiMidity port 1 '
    1 'TiMidity port 1 '
+
    2 'TiMidity port 2 '
    2 'TiMidity port 2 '
+
    3 'TiMidity port 3 '
    3 'TiMidity port 3 '
+
</nowiki>}}
  
 
You can now play MIDI files using aplaymidi:
 
You can now play MIDI files using aplaymidi:
  
$ aplaymidi filename.mid --port 128:0
+
{{bc|$ aplaymidi filename.mid --port 128:0}}
  
Another example is vkeybd, a virtual MIDI keyboard for X.
+
Another example is '''vkeybd''', a virtual MIDI keyboard for X.
  
You can install [https://aur.archlinux.org/packages.php?ID=19775 vkeybd] from the [[AUR]].
+
You can [[Pacman|install]] {{AUR|vkeybd}} from the [[AUR]].
  
$ vkeybd --addr 128:0
+
{{bc|$ vkeybd --addr 128:0}}
  
Option --addr 128:0 connects the input (readable) software MIDI port provided by vkeybd to the first output (writable) ALSA port provided by Timidity. Alternatively you can use aconnect(1), community/aconnectgui or AUR packages [https://aur.archlinux.org/packages.php?do_Details=1&ID=9668 patchage], [https://aur.archlinux.org/packages.php?ID=13818 kaconnect]. As a result when you play around with the keys on the vkeybd timidity plays the appropriate notes. See also [[USB_Midi_Keyboards|USB Midi Keyboards]].
+
Option {{ic|--addr 128:0}} connects the input (readable) software MIDI port provided by vkeybd to the first output (writable) ALSA port provided by Timidity. Alternatively you can use   aconnect(1), community/aconnectgui or AUR packages [https://aur.archlinux.org/packages.php?do_Details=1&ID=9668 patchage], {{AUR|kaconnect}}. As a result when you play around with the keys on the vkeybd timidity plays the appropriate notes.
  
===Connect to virtual MIDI device===
+
====Connect to virtual MIDI device====
  
 
Once you have the timidity++ daemon running and it is working with aplaymidi, you can connect it to a virtual MIDI device that will work in programs such as rosegarden or scala.
 
Once you have the timidity++ daemon running and it is working with aplaymidi, you can connect it to a virtual MIDI device that will work in programs such as rosegarden or scala.
  
# modprobe snd-virmidi
+
Load the {{ic|snd-virmidi}} '''kernel module''' and (optionally) configure it to be loaded at boot. Read [[Kernel modules]] for more information.
  
 
Use aconnect to verify the port numbers:
 
Use aconnect to verify the port numbers:
  
$ aconnect -o
+
{{hc|$ aconnect -o|<nowiki>
 
+
 
  client 14: 'Midi Through' [type=kernel]
 
  client 14: 'Midi Through' [type=kernel]
 
     0 'Midi Through Port-0'
 
     0 'Midi Through Port-0'
Line 113: Line 96:
 
     2 'TiMidity port 2 '
 
     2 'TiMidity port 2 '
 
     3 'TiMidity port 3 '
 
     3 'TiMidity port 3 '
 
+
</nowiki>}}
 
Now create the connection:
 
Now create the connection:
$ aconnect 20:0 128:0
+
{{bc|$ aconnect 20:0 128:0}}
  
You should now have a working MIDI output device on your system (/dev/snd/midiC1D0).
+
You should now have a working MIDI output device on your system ({{ic|/dev/snd/midiC1D0}}).
  
  
Line 123: Line 106:
 
===timidity++ does not play MIDI files===
 
===timidity++ does not play MIDI files===
 
It may be that your soundfile is not set up correctly. Just run:
 
It may be that your soundfile is not set up correctly. Just run:
$ timidity example.midi
+
{{bc|$ timidity example.midi}}
  
 
If you find a line like this in the terminal output, your soundfile is not set up properly.
 
If you find a line like this in the terminal output, your soundfile is not set up properly.
No instrument mapped to tone bank 0, program XX - \
+
{{bc|
this instrument will not be heard
+
No instrument mapped to tone bank 0, program XX - \
 +
this instrument will not be heard
 +
}}
  
Make sure you've installed some samples and your soundfile is added to /etc/timidity++/timidity.cfg. See [[Timidity#Setting up the sound samples|Setting up the sound samples]] above for more details.
+
Make sure you've installed some samples and your soundfile is added to {{ic|/etc/timidity++/timidity.cfg}}. See [[#Soundfonts]] above for more details.
  
===timidity++ daemon mode won't start===
+
===Daemon mode won't start===
First, make sure you are in audio group. If not, add yourself to audio group:
+
First, make sure you are in the '''audio''' group. If not, add yourself to it:
  
# gpasswd audio -a yourusername
+
{{bc|# gpasswd audio -a yourusername}}
  
 
After group change, you should re-login.
 
After group change, you should re-login.
  
If you are using PulseAudio, instead of
+
If you are using [[PulseAudio]], instead of [[Daemons|enabling]] the {{ic|timidity.service}}, start timidity++ as an user:
  
# rc.d start timidity++
+
{{bc|$ timidity -iA -OO}}
  
Start timidity++ in your Desktop Environment:
+
If you want to run timidity++ in background, do not use timidity++'s daemonize option, append {{ic|&}} instead.
  
$ timidity -iA -OO
+
===Daemon mode plays sound out of pace===
 +
timidity++'s ALSA output module (default) may cause this issue in ALSA server mode. Try another output option, for example, '''libao''':
  
If you want to run timidity++ in background, do not use timidity++'s daemonize option, use & instead.
+
{{bc|$ timidity -iA -OO}}
 
+
===timidity++ daemon mode plays sound out of pace===
+
timidity++'s ALSA output module (default) may cause this issue in ALSA server mode. Try another output option, for example, libao:
+
 
+
$ timidity -iA -OO
+
  
 
And test it using aplaymidi. If this does not work, you may want to configure [[JACK]] and set timidity++'s output to jack.
 
And test it using aplaymidi. If this does not work, you may want to configure [[JACK]] and set timidity++'s output to jack.
 +
== Tips and tricks ==
 +
===Convert files===
 +
timidity++ can also convert MIDI files into other formats. The following command saves the resulting sound to a WAV file:
 +
{{bc|$ timidity ''input.mid'' -Ow -o ''out.wav''}}
 +
To convert to another formats, you can use [[FFmpeg]]. This will convert it to mp3:
 +
{{bc|$ timidity ''input.mid'' -Ow -o - <nowiki>|</nowiki> ffmpeg -i - -acodec libmp3lame -ab 256k ''out.mp3''}}
  
 
===How to make DOSBox use Timidity++===
 
===How to make DOSBox use Timidity++===
The following method is tested in version DOSBox 0.72 (don't know if this works for OLDER or NEWER!).
+
{{Note|The following method is tested in version DOSBox 0.72}}
  
 
First of all, you need to write a config file. Input the following in DOSBox to create a configuration file:
 
First of all, you need to write a config file. Input the following in DOSBox to create a configuration file:
config -writeconf dosbox.conf
+
{{bc|config -writeconf dosbox.conf}}
you can replace ''dosbox.conf'' by anyname that you want, add a dot in front of it if you want to hide it.
+
you can replace {{ic|dosbox.conf}} by any name that you want, add a dot in front of it if you want to hide it.
  
Make sure you statred Timidity++ as DAEMON as the instructions above, use the ''aconnect'' command.
+
Make sure you statred Timidity++ as [[#Daemon]] as the instructions above, use the ''aconnect'' command.
  
 
Edit this configuration file with any editor, go to the section:
 
Edit this configuration file with any editor, go to the section:
[midi]
+
{{hc|dosbox.conf|<nowiki>
mpu401=intelligent
+
[midi]
device=default
+
mpu401=intelligent
config=
+
device=default
 +
config=
 +
</nowiki>}}
 
put the ALSA connection port into the back of ''config='', in default:
 
put the ALSA connection port into the back of ''config='', in default:
config=128:0
+
{{bc|1=config=128:0}}
  
 
Restart DOSBox within a terminal so you can see its debug messages, by no accident you should see a successful initiation on port 128:0.
 
Restart DOSBox within a terminal so you can see its debug messages, by no accident you should see a successful initiation on port 128:0.
 +
== See also ==
 +
* [[USB Midi Keyboards]]

Revision as of 09:31, 27 January 2013

Timidity++ is a software synthesizer that can play MIDI files without a hardware synthesizer. It can either render to the sound card in real time, or it can save the result to a file, such as a PCM .wav file.

Installation

Install the timidity++ package from the Official repositories.

You should also install a soundfont to be able to produce sound. Here is a list of soundfonts:

Configuration

Soundfonts

Configure your choosed soundfont:

Freepats

The Freepats project provides a set of instrument samples which are compatible with timidity++.

To use Freepats with timidity, add the following lines to timidity.cfg:

/etc/timidity++/timidity.cfg
dir /usr/share/timidity/freepats
source /etc/timidity++/freepats/freepats.cfg

Fluidr3

There are other soundfonts available. This will show how to install the fluidr3AUR soundfont.

Now we have to add its path to the timidity++ configuration file. Just add this line:

/etc/timidity++/timidity.cfg
soundfont /usr/share/soundfonts/fluidr3/FluidR3GM.SF2

Daemon

Start and configure to autostart the timidity.service. Read Daemons for more details.

If you are using PulseAudio, that may not work. You may want to add the following command as an auto start program in your desktop environment. Or, if you just want to start timidity in daemon mode once, you can use the following command which will make console output viewable:

$ timidity -iA

Usage

Play files

There are two ways to use timidity++. Either as MIDI player or as daemon adding MIDI support to ALSA.

Standalone mode

You can simply use timidity++ to play MIDI files:

$ timidity example.midi

Add option -in or -ig for a text-based/gtk+ interface. E.g. as a Xfce/GNOME user you may want to set MIDI files to open with the custom command timidity -ig. There are many other options to timidity; see man timidity or use -h to get help.

Daemon mode

If you are runing timidity as a #Daemon (ALSA sequencer client), it will provide MIDI output support for other programs such as rosegarden, aplaymidi, vkeybd, etc.

This will give you four output software MIDI ports (in addition of hardware MIDI ports on your system, if any):

$  aconnect -o
client 128: 'TiMidity' [type=user]
    0 'TiMidity port 0 '
    1 'TiMidity port 1 '
    2 'TiMidity port 2 '
    3 'TiMidity port 3 '

You can now play MIDI files using aplaymidi:

$ aplaymidi filename.mid --port 128:0

Another example is vkeybd, a virtual MIDI keyboard for X.

You can install vkeybdAUR from the AUR.

$ vkeybd --addr 128:0

Option --addr 128:0 connects the input (readable) software MIDI port provided by vkeybd to the first output (writable) ALSA port provided by Timidity. Alternatively you can use aconnect(1), community/aconnectgui or AUR packages patchage, kaconnectAUR. As a result when you play around with the keys on the vkeybd timidity plays the appropriate notes.

Connect to virtual MIDI device

Once you have the timidity++ daemon running and it is working with aplaymidi, you can connect it to a virtual MIDI device that will work in programs such as rosegarden or scala.

Load the snd-virmidi kernel module and (optionally) configure it to be loaded at boot. Read Kernel modules for more information.

Use aconnect to verify the port numbers:

$ aconnect -o
 client 14: 'Midi Through' [type=kernel]
     0 'Midi Through Port-0'
 client 20: 'Virtual Raw MIDI 1-0' [type=kernel]
     0 'VirMIDI 1-0     '
 client 21: 'Virtual Raw MIDI 1-1' [type=kernel]
     0 'VirMIDI 1-1     '
 client 22: 'Virtual Raw MIDI 1-2' [type=kernel]
     0 'VirMIDI 1-2     '
 client 23: 'Virtual Raw MIDI 1-3' [type=kernel]
     0 'VirMIDI 1-3     '
 client 128: 'TiMidity' [type=user]
     0 'TiMidity port 0 '
     1 'TiMidity port 1 '
     2 'TiMidity port 2 '
     3 'TiMidity port 3 '

Now create the connection:

$ aconnect 20:0 128:0

You should now have a working MIDI output device on your system (/dev/snd/midiC1D0).


Troubleshooting

timidity++ does not play MIDI files

It may be that your soundfile is not set up correctly. Just run:

$ timidity example.midi

If you find a line like this in the terminal output, your soundfile is not set up properly.

No instrument mapped to tone bank 0, program XX - \
this instrument will not be heard

Make sure you've installed some samples and your soundfile is added to /etc/timidity++/timidity.cfg. See #Soundfonts above for more details.

Daemon mode won't start

First, make sure you are in the audio group. If not, add yourself to it:

# gpasswd audio -a yourusername

After group change, you should re-login.

If you are using PulseAudio, instead of enabling the timidity.service, start timidity++ as an user:

$ timidity -iA -OO

If you want to run timidity++ in background, do not use timidity++'s daemonize option, append & instead.

Daemon mode plays sound out of pace

timidity++'s ALSA output module (default) may cause this issue in ALSA server mode. Try another output option, for example, libao:

$ timidity -iA -OO

And test it using aplaymidi. If this does not work, you may want to configure JACK and set timidity++'s output to jack.

Tips and tricks

Convert files

timidity++ can also convert MIDI files into other formats. The following command saves the resulting sound to a WAV file:

$ timidity input.mid -Ow -o out.wav

To convert to another formats, you can use FFmpeg. This will convert it to mp3:

$ timidity input.mid -Ow -o - | ffmpeg -i - -acodec libmp3lame -ab 256k out.mp3

How to make DOSBox use Timidity++

Note: The following method is tested in version DOSBox 0.72

First of all, you need to write a config file. Input the following in DOSBox to create a configuration file:

config -writeconf dosbox.conf

you can replace dosbox.conf by any name that you want, add a dot in front of it if you want to hide it.

Make sure you statred Timidity++ as #Daemon as the instructions above, use the aconnect command.

Edit this configuration file with any editor, go to the section:

dosbox.conf
[midi]
mpu401=intelligent
device=default
config=

put the ALSA connection port into the back of config=, in default:

config=128:0

Restart DOSBox within a terminal so you can see its debug messages, by no accident you should see a successful initiation on port 128:0.

See also