.TH APLAYMIDI2 1 "4 July 2024" .SH NAME aplaymidi2 \- play MIDI Clip Files .SH SYNOPSIS .B aplaymidi2 \-p client:port[,...] midi2file ... .SH DESCRIPTION .B aplaymidi2 is a command-line utility that plays the specified MIDI Clip file(s) to one or more ALSA sequencer ports. .SH OPTIONS .TP .I \-h, \-\-help Prints a list of options. .TP .I \-V, \-\-version Prints the current version. .TP .I \-p, \-\-port=client:port,... Sets the sequencer port(s) to which the events in the MIDI Clip file(s) are sent. A client can be specified by its number, its name, or a prefix of its name. A port is specified by its number; for port 0 of a client, the ":0" part of the port specification can be omitted. Multiple ports can be specified to allow playback of MIDI Clip file(s) that contain events for multiple devices (ports) corresponding to the multiple UMP Groups. For compatibility with .B pmidi(1), the port specification is taken from the .I ALSA_OUTPUT_PORTS environment variable if none is given on the command line. .B aplaymidi2 supports only basic UMP events: in addition to the standard MIDI1 and MIDI2 CVMs and 7bit SysEx, only the following are supported: DCTPQ, DC, Set Tempo, Start Clip, End Clip. Lyrics and other meta data in Flex Data are printed, too, unless \fI\-s\fP option is given. The multiple output ports are useful when the given MIDI Clip file contains the UMP packets for multiple Groups. When the destination port is a UMP MIDI 2.0 port, the single connection should suffice, though, since a MIDI 2.0 port can process the inputs for multiple Groups. For other cases (e.g. connecting to a legacy MIDI port), you would need to specify the destination port per Group. If undefined, it's sent to the first destination port as default. .TP .I \-d, \-\-delay=seconds Specifies how long to wait after the end of each MIDI Clip file, to allow the last notes to die away. Default is 2 seconds. .TP .I \-s, \-\-silent Don't show message texts. .SH SEE ALSO pmidi(1) .br aplaymidi(1) .SH AUTHOR Takashi Iwai