.forgejo/workflows | ||
crates | ||
.dockerignore | ||
.gitignore | ||
.gitmodules | ||
Cargo.lock | ||
Cargo.toml | ||
Justfile | ||
LICENSE | ||
README.md | ||
shell.nix |
tek
a music making program for your terminal
project status
for roadmap, see https://codeberg.org/unspeaker/tek/milestones
Warning
As of 2024-10-25, I'm on track to release
tek 0.2.0
sometime in December 2024. I plan to tag the previous working prototype (as seen in the demos published in the tek channel at basspistol's peertube) as0.1.0
— once I've identified the appropriate commit!I've been dreaming of this project for a decade, and finally had the experience and peace of mind to start building it in late May 2024. I quickly reached the limit of how much of the UI I can write imperatively, so I started refactoring it in a more declarative style. The new interface logic is holding out pretty well, though it's not presently without its warts.
Your moral support means a lot to me. Feel free to contact me on Mastodon! (Especially if you know how to host LV2 plugin UIs in
winit
; or how to relink abandoned Win32 VST2s into LV2 or CLAP monoliths 😁)Love,
(a rogue knowledge worker in a cyberpunk dystopia)
what it does
Tek is a MIDI sequencer, sampler, and plugin host for the Linux terminal. It's written in Rust, and targets JACK (or Pipewire's JACK implementation).
design goals
lightweight
My goal is to have a pop-up scratchpad for musical ideas that doesn't get in the way of building upon them. Kind of like Ableton — but for free systems, and without all the bloat!
flexible
Besides Ableton, I'm also inspired by the workflow of trackers and various old-school hardware sequencers (of which I've broken several). I've found that every existing music-making tool takes me about 80% of the way to the music I want to make. And so, after a decade of fucking around, I've decided it's finally time to make good on my old dream to build the instrument that will take me 100% there.
programmable
A secondary goal is to make my music making environment extensible, programmable, and interoperable; the intended project format is an S-expression-based notation (EDN, Steel, or similar... though I've also been looking for an excuse to embed a Forth 😏)
getting started
requirements
- Linux
- JACK or Pipewire
- a terminal supporting 24-bit colors (I use
kitty
)
recommended
- MIDI controller
- Samples
- LV2 plugins
downloads
Warning
Binaries are currently unavailable. Right now your only option is to build from source. In the future I plan to integrate Forgejo Actions / Codeberg CI.
building from source
You need a Rust toolchain and various system libraries. You can obtain the former
using rustup
and the latter using nix-shell
. From there, use the commands in the
Justfile
, e.g.:
just arranger
usage
Warning
The following applies to
tek 0.1.0
. I will update it as part of the0.2.0
release.
Overview
Tek is inspired by "clip launching" workflows as exemplified by Ableton Live, Bitwig Studio, Ardour, and probably others. The main view consists of three sections:
- The arranger view corresponds to Ableton's Session and Arrangement views. It allows you to put together a musical composition as a sequence of phrases, playing simultaneously across multiple tracks.
- The sequencer view allows you to edit phrases, which consist of MIDI events.
- The chain view allows you to add devices to each track. Devices determine how a given phrase will sound. Currently, there are two devices implemented: sampler and plugin.
Note
Use
Tab
to switch focus between views. UseEnter
to exclusively focus the highlighted view, andEsc
to unfocus it. When a view is focused, use theArrow Keys
andEnter
to navigate. Use;
(semicolon) to open the command palette, which will list the remaining keybindings.