NOTE: addons are enabled for Linux/Mac but not windows [yet]
Addons allow for interfacing with the operating system ♥.
This prevents milkytracker to become a monolyth DAW, stay small, and
promote personal computing across all OS'es.
Addons can be accessed via the sample-editor rightclick context-menu.
Because samples ARE key-ingredients for sample-trackers, so an unexplored territory is to integrate external tools with the sampler (not filebrowsers):
- procedural SAMPLERS: sample ANY synth/app/input into milkytracker
- DIY 'plugin grabber' by sampling desktop audio
- generate samples using puredata/csound etc
- apply a complex effect to a sample
- source samples from an online API
- source samples from an local AI agent
- Extend the sampler with your favorite SCRIPTING LANGUAGE(s)
- Create script-pipelines between different tools
- automate tedious tasks
- FUTURE: export/import
.xp
[processable] patterns in a similar fashion
Also async workflows are possible via the sample editor:
- right-click: Addon > select your addon (
audacity %s &
e.g.) - import later: Addon > import from addon
MilkyTracker aims to be a small & portable musicproduction app.
Becoming a multi-plugin-host is simply not on the table, as it would burden its
mission with maintenance of various plugin-format (and break lowspec devices).
Having that said, parametric cli dialogs combined with powerful cli-backends are a perfect match for addons♥.
Developing addons is much easier compared to developing VST C++ plugins.
You are encouraged to use scriptable DSP-backends instead:
- ffmpeg (effect-filters, aeval for processing, aevalsrc for synthesis)
- SoX (effect-filters, synth for synthesis)
- csound (insane DSP powerhouse for fx/synths with huge ecosystem)
Milkytracker addons are parametric cli dialogs. Basically, it present a UI dialog, before executing the final cli-cmd:
sox %s -D %s speed %~(speed:1:20:1)
produces:
which produces:
sox /tmp/in.wav -D /tmp/out.wav speed 1
for more info see https://github.com/milkytracker/MilkyTracker/tree/master/src/tools/addons.txt
please contribute and do a pullrequest, minimum contribution guidelines:
- create a (topic/author-based) folder in this repo
- put your scripts in there
- and a
README.md
- and a
screenshot.jpg
- and a
addons.txt
- done!