Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mididings(1) [debian man page]

MIDIDINGS(1)						      General Commands Manual						      MIDIDINGS(1)

NAME
mididings - MIDI router and processor SYNOPSIS
mididings [options] "patch" mididings [options] -f filename DESCRIPTION
mididings is a MIDI router and processor based on Python, supporting ALSA and JACK MIDI. Many features are provided: MIDI routing and filtering Filter events depending on their event type, channel, note number, velocity, etc., and freely route them between an arbitrary number of input and output ports. Modifying and converting MIDI events Transpose notes, apply velocity curves, change controller values and ranges, or convert events to any other MIDI event type. midid- ings also includes more complex functions like a diatonic harmonizer, floating split points, latched notes, and more. Seamless switching between patches Set up different "scenes", each with its own MIDI routing and processing, and switch between them at any time, even while playing. Switching scenes does not affect notes already held, and does not result in dropouts or stuck notes! MIDI event monitoring, running external commands Print MIDI event data to the console to help debugging your patches and configuring your MIDI controllers. In addition to its MIDI output, mididings can also execute shell commands and send OSC or DBUS messages. OPTIONS
-h, --help show this help message and exit -b BACKEND name of backend to use -c CLIENT_NAME ALSA or JACK client name -i IN_PORTS number of input ports -o OUT_PORTS number of output ports -d START_DELAY delay (in seconds) before starting MIDI processing -f FILENAME filename of script to run SEE ALSO
livedings(1) AUTHOR
mididings was written by Dominic Sacre <dominic.sacre@gmx.de>. This manual page was written by Alessio Treglia <alessio@debian.org>, for the Debian project (and may be used by others). November 2010 MIDIDINGS(1)

Check Out this Related Man Page

MIDIPLAY(1)						    BSD General Commands Manual 					       MIDIPLAY(1)

NAME
midiplay -- play MIDI and RMID files SYNOPSIS
midiplay [-d devno] [-f file] [-l] [-m] [-p pgm] [-q] [-t tempo] [-v] [-x] [file ...] DESCRIPTION
The midiplay command plays MIDI and RMID files using the sequencer device. If no file name is given it will play from standard input, other- wise it will play the named files. RMID files are Standard MIDI Files embedded in a RIFF container and can usually be found with the 'rmi' extension. They contain some addi- tional information in other chunks which are not parsed by midiplay yet. The program accepts the following options: -d devno specifies the number of the MIDI device used for output (as listed by the -l flag). There is no way at present to have midiplay map playback to more than one device. The default is device is given by environment variable MIDIUNIT. -f file specifies the name of the sequencer device. -l list the possible devices without playing anything. -m show MIDI file meta events (copyright, lyrics, etc). -p pgm force all channels to play with the single specified program (or instrument patch, range 1-128). Program change events in the file will be suppressed. There is no way at present to have midiplay selectively map channels or instruments. -q specifies that the MIDI file should not be played, just parsed. -t tempo-adjust specifies an adjustment (in percent) to the tempi recorded in the file. The default of 100 plays as specified in the file, 50 halves every tempo, and so on. -v be verbose. If the flag is repeated the verbosity increases. -x play a small sample sound instead of a file. A file containing no tempo indication will be played as if it specified 150 beats per minute. You have been warned. ENVIRONMENT
MIDIUNIT the default number of the MIDI device used for output. The default is 0. FILES
/dev/music MIDI sequencer device SEE ALSO
midi(4) HISTORY
The midiplay command first appeared in NetBSD 1.4. BUGS
It may take a long while before playing stops when midiplay is interrupted, as the data already buffered in the sequencer will contain timing events. BSD
January 16, 2010 BSD
Man Page