ELEKTROID-CLI(1)

πŸŽ›οΈ ELEKTROID-CLI β€” the General Commands Manual, but make it cute

okay bestie, so this is elektroid-cli, live from the General Commands Manual section of the library πŸ’… it's the command-line version of Elektroid, and she's literally the backstage pass to all your sample and MIDI device drama. no GUI, just vibes and flags.


✨ NAME ✨

elektroid-cli β€” Sample and MIDI device manager (CLI) πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

elektroid-cli [options] command

that's it. that's the whole entrance exam. [options] then a command. iconic behavior.


πŸ’– DESCRIPTION πŸ’–

so elektroid-cli is part of Elektroid, a sample and MIDI device manager. if you want the fancy windowed version, go see man elektroid for the GUI app β€” she's the main character, this one's the cool older sister who lives in your terminal 🫢

with Elektroid you can easily upload and download audio files and manage all sorts of different types of data on all sorts of different MIDI devices β€” think presets, projects, tunings, the whole aesthetic ✨ it can also send and receive SysEx MIDI files, because of course it can. versatile queen.


πŸ‘‘ SUPPORTED DEVICES πŸ‘‘

the roster. the lineup. the guest list πŸ”₯

  • Arturia MicroBrute
  • Arturia MicroFreak
  • Casio CZ-101
  • Elektron Analog Four MKI, MKII and Keys
  • Elektron Analog Heat MKI, MKII and +FX
  • Elektron Analog Rytm MKI and MKII
  • Elektron Digitakt I and II
  • Elektron Digitone I and II and Digitone Keys
  • Elektron Model:Cycles
  • Elektron Model:Samples
  • Elektron Syntakt
  • Eventide ModFactor, PitchFactor, TimeFactor, Space and H9
  • KORG padKONTROL
  • KORG Volca Sample and Volca Sample 2
  • Moog Little Phatty and Slim Phatty
  • Novation Summit and Peak
  • Samplers implementing MIDI SDS

no cap, that's a stacked list πŸ’€


🌈 DEVICE COMMANDS 🌈

these ones operate over the device itself, like, directly. for the commands that operate over the different types of data a device provides, scroll on down to the filesystem commands section, bestie πŸ‘‡

  • [ ld | list-devices ] β€” List devices
  • info device_number β€” Show device info
  • [ df | info-storage ] device_number β€” Show size and use of the available storages
  • send file device_number β€” Send MIDI data file to device
  • receive device_number file β€” Receive MIDI data file from device
  • upgrade firmware device_number β€” Upgrade the device
  • play file β€” Play audio file
  • record file β€” Record into file

🌸 FILESYSTEM COMMANDS 🌸

different filesystem operations are implemented on different connectors, so a command has one of these two forms. pay attention, this part matters 🧚

  • connector, colon (':'), filesystem name, colon (':'), and the operation itself. this is the preferred way ✨
  • connector, hyphen ('-'), filesystem name, hyphen ('-'), and the operation itself. this should be avoided πŸ™ˆ like, please. just use the colon one.

provided paths must always be prepended with the device id and a colon (':'), e.g. 0:/samples. paths pointing to a data, sound or project file use the index of a file instead of its name. important!! don't come crying to me when it doesn't work because you forgot the device id πŸ’€

these are the available operations:

  • [ ls | list ] device_number:path_to_directory β€” List directory
  • mkdir device_number:path_to_directory β€” Create directory and its parent directories as needed
  • [ rmdir | rm ] device_number:path_to_directory β€” Delete directory recursively
⚠️ heads up bestie, rmdir / rm on a directory is recursive. she takes the whole folder with her. no undo. be so serious about this one 😭
  • [ ul | upload ] file device_number:path_to_file_or_directory β€” Upload file. If the path does not exist it will be created.
  • [ dl | download | rdownload | rdl | backup ] β€” Download file into the destination directory or the current directory if not provided.
[ dl | download | rdownload | rdl | backup ] device_number:path_to_file_or_directory [ destination ]
  • mv device_number:path_to_file_or_directory β€” Move file. If the destination path does not exist, it will be created.
mv device_number:path_to_file_or_directory device_number:path_to_file_or_directory
  • rm device_number:path_to_file β€” Delete file
  • cl device_number:path_to_file β€” Clear file
  • cp device_number:path_to_file device_number:path_to_file β€” Copy file
  • sw device_number:path_to_file device_number:path_to_file β€” Swap files

πŸ’… OPTIONS πŸ’…

  • -v β€” give verbose output. use it more than once for more verbosity. yes, more than once. stack 'em. she loves that πŸ“š

πŸ“ EXAMPLES πŸ“

this is the part where it all clicks, i promise 🫢

elektroid-cli ld lists the available devices.

elektroid-cli info 0 shows information about the device, including the connector and the available filesystems.

elektroid-cli elektron:sample:ul square.wav 0:/waveforms uploads a sample to an Elektron device. look at that colon-colon action, she ate πŸ’…

elektroid-cli sds:mono-16b:dl 0:/1 downloads a mono 16 bits sample from an SDS sampler.

elektroid-cli summit:single:ls 0:/A lists Novation Summit single patches in bank A.


πŸ”₯ SEE ALSO πŸ”₯

the GitHub page provides some examples, and honestly? go look, iykyk:

<https://dagargo.github.io/elektroid/>


πŸ’œ AUTHOR πŸ’œ

elektroid-cli was written by David GarcΓ­a GoΓ±i <dagargo@gmail.com>. king behavior πŸ‘‘

this manual page was written by Dennis Braun <snd@debian.org> for the Debian project (but may be used by others). generous icon 🌈


okay that's the whole page, bestie, you're officially educated πŸ’– this was the elektroid-cli(1) manual, dated Jan 2023 β€” go forth and manage those samples, periodt πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from