MIDICAT(1)

πŸ’– MIDICAT(1) πŸ’–

okay bestie, welcome to midicat β€” she's a General Commands Manual girlie and she's here to send to or receive from MIDI ports 🎹✨


✨ NAME ✨

midicat β€” send to or receive from MIDI ports πŸŽ€


🌸 SYNOPSIS 🌸

midicat [-d] [-i file] [-o file] [-q port]

πŸ¦‹ DESCRIPTION πŸ¦‹

The midicat utility receives MIDI data from the given input MIDI port and/or sends it to the given output MIDI port. no cap, that's literally the whole job and she does it flawlessly πŸ’…

The options are as follows:

  • -d β€” Dump transferred data in hex on stderr. it's giving forensic scientist πŸ”πŸ’€
  • -i file β€” Read MIDI data from this file instead of receiving it from the MIDI port. If the option argument is '-' then standard input will be used. πŸ‘‘
  • -o file β€” Write MIDI data to this file instead of sending it to the MIDI port. If the option argument is '-' then standard output will be used. 🫢
  • -q port β€” Use this sndio(7) MIDI port for input/output. If the option is used twice, the first one specifies the input port and the second one the output port. two moods, one flag, main character energy fr fr 🌈

If no files are specified, then midicat transfers data from the MIDI input port to the MIDI output port. yes she just does that, iconic behaviour ⭐


πŸ”₯ EXAMPLES πŸ”₯

Send the given file to rmidi/0:

$ midicat -i file.syx -q rmidi/0

Dump data received from rmidi/0 to stderr:

$ midicat -d -q rmidi/0 -o /dev/null

Send data from rmidi/0 to midithru/0:

$ midicat -q rmidi/0 -q midithru/0
notice how -q shows up twice in that last one? that's the input port then the output port, bestie. she said "two ports, one command" and honestly? ate. πŸ“

πŸ’œ SEE ALSO πŸ’œ

midi(4), sndio(7), sndiod(8)

iykyk, go read those next, they're the extended universe 🌸


this lil manual page came from the Debian crew, version $Mdocdate$, and it's filed under MIDICAT(1) πŸ’– mwah, stan, bye bestie πŸ‘‘βœ¨