APLAYMIDI2(1)
β¨ APLAYMIDI2(1) β General Commands Manual β¨
Okay bestie, this is the manual page for aplaymidi2 π and honestly it's giving main character energy π
β¨ NAME β¨
aplaymidi2 is a command-line utility that plays MIDI Clip Files πΆ Literally that's the whole job, no cap π¦
β¨ SYNOPSIS β¨
aplaymidi2 -p client:port[,...] midi2file ...
β¨ DESCRIPTION β¨
So aplaymidi2 is the CLI tool you reach for when you want to play the MIDI Clip file(s) you've got out to one or more ALSA sequencer ports π₯ It's iconic, ngl πΈ
β¨ OPTIONS β¨
-h,--helpβ Prints a list of options π-V,--versionβ Prints the current version β¨-p,--port=client:port,...β This is the big one π It sets the sequencer port(s) that the events in your MIDI Clip file(s) get sent to π¦
A client can be given by its number, its name, or just a prefix of its name π
A port is given by its number, and for port 0 of a client you can skip the :0 part, because it's lowkey redundant π
You can list multiple ports so you can play MIDI Clip file(s) that have events for multiple devices (ports) matching up with multiple UMP Groups π
For compatibility with pmidi(1), if you don't put a port on the command line, the port spec gets pulled from the ALSA_OUTPUT_PORTS environment variable π§
Real talk: aplaymidi2 only supports basic UMP events π Besides the standard MIDI1 and MIDI2 CVMs and 7bit SysEx, the only ones it handles are DCTPQ, DC, Set Tempo, Start Clip, and End Clip π«Ά Lyrics and other meta data in Flex Data get printed too, unless you use the -s option π
Multiple output ports are useful when your MIDI Clip file has UMP packets for multiple Groups π¦ If the destination is a UMP MIDI 2.0 port, one connection should be enough, since a MIDI 2.0 port can handle inputs for multiple Groups all by itself π For other stuff, like connecting to a legacy MIDI port, you'd need to specify the destination port per Group π If it's undefined, it gets sent to the first destination port by default β¨
-d,--delay=secondsβ Tells it how long to wait after the end of each MIDI Clip file, so the last notes have time to die away π The default is 2 seconds β-s,--silentβ Don't show message texts π€«-a,--passallβ Passes all UMP packets as is πΈ
By default, aplaymidi2 only passes MIDI1 and MIDI2 channel voice messages and handles other UMP packets internally π§ With this option, it passes all UMP packets to the target instead π₯
β¨ SEE ALSO β¨
β¨ AUTHOR β¨
Takashi Iwai <tiwai@suse.de> π«Ά
Bestie, that's the whole page π Written by Takashi Iwai, dated 4 July 2024, from APLAYMIDI2(1) πβ¨
π¦ where this page comes from
- alpine 3.22: alsa-utils-doc 1.2.14-r0 Β· GPL-2.0-or-later
- alpine 3.23: alsa-utils-doc 1.2.14-r4 Β· GPL-2.0-or-later
- alpine 3.24: alsa-utils-doc 1.2.15.2-r1 Β· GPL-2.0-or-later
- arch rolling: alsa-utils 1.2.16-1 Β· GPL-2.0-or-later
- centos-stream 10: alsa-utils 1.2.16-1.el10 Β· GPL-2.0-or-later
- centos-stream 9: alsa-utils 1.2.16-1.el9 Β· GPLv2+
- debian trixie: alsa-utils 1.2.14-1 Β· GPL-2.0-only
- fedora 43: alsa-utils 1.2.14-2.fc43 Β· GPL-2.0-or-later
- fedora 43: alsa-utils 1.2.16-1.fc43 Β· GPL-2.0-or-later
- fedora 44: alsa-utils 1.2.15.2-3.fc44 Β· GPL-2.0-or-later
- fedora 44: alsa-utils 1.2.16-1.fc44 Β· GPL-2.0-or-later
- nixos 26.05: alsa-utils 1.2.14
- nixpkgs unstable: alsa-utils 1.2.16
- opensuse-leap 16.0: alsa-utils 1.2.14-160000.2.2 Β· GPL-2.0-or-later
- opensuse-leap 16.0: alsa-utils 1.2.14-160000.2.2 Β· GPL-2.0-or-later
- opensuse-leap 16.0: alsa-utils 1.2.14-160000.2.2 Β· GPL-2.0-or-later
- opensuse-leap 16.0: alsa-utils 1.2.14-160000.2.2 Β· GPL-2.0-or-later
- ubuntu questing: alsa-utils 1.2.14-1ubuntu1
- ubuntu resolute: alsa-utils 1.2.15.2-1ubuntu1 Β· GPL-2.0-only
- ubuntu stonking: alsa-utils 1.2.15.2-1ubuntu2 Β· GPL-2.0-only
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms