elekloader

by elekloader·Tool

A mod loader for Elektron firmware. You pick mods and supply the stock OS file Elektron publishes for your device. elekloader builds a custom OS file on your own machine, and you flash it the way you flash any OS update.

Version v0.9.0·released 3 weeks ago·4.3k downloads
elekloader

About

A mod loader for Elektron firmware. You pick mods, add the stock OS file that Elektron publishes for your device, and elekloader builds a custom OS file on your own machine. You install it like any OS update. Many Digitakt and Digitone mods in this list are elekloader mods (.elemod files).

Highlights
  • Runs in the browser with nothing to install, or as an app for Windows and macOS
  • Checks the chosen mods against each other before building: overlapping bytes, memory, resources and requirements
  • Never touches the bootloader and verifies every output file, so the stock OS always brings the device back
  • A core mod with an event bus lets several mods hook the same code

What you need
Your own stock OS file: Digitakt MKI 1.53 or 1.54, Digitone MKI / Digitone Keys 1.43 or 1.44, or Octatrack MKI / MKII 1.40C.

Good to know
On the Octatrack it builds whole images; linkable mods with their own core have booted on an MKII so far. More devices are planned. Nothing from Elektron is distributed: every build starts from your own file.

README

elekloader

A mod loader for Elektron firmware. You pick mods and supply the stock OS file Elektron publishes for your device. elekloader builds a custom OS file on your own machine, and you flash it the way you flash any OS update.

  • Nothing from Elektron is distributed. A mod (.elemod) carries only its author's bytes, the short instruction fragments needed to hook the OS, and hashes of the stock bytes it expects. Every build starts from your own stock file, recognised by its hash.
  • The bootloader is never touched. Mods change the main OS, and on the Digitone II a SHARC mod may also change the DSP's section 7, inside fixed limits. Each output file is re-read and verified before it is written. So the stock OS file always recovers the device.
  • Mods are checked against each other before anything is built. Two mods may not touch the same bytes, claim the same memory or the same named resource, or leave a requirement unmet.
Device OS Status
Digitakt (mk1) 1.53, 1.54 supported
Digitakt II 1.17 experimental: whole builds (format-1 mods) and linkable mods with its own core (the hook bus's tick, draw, key and encoder events), sealed as the unit checks them; boots in digikit's emulator; core with a key-swap mod works on a unit (Transfer over USB)
Digitone (mk1) and Digitone Keys 1.43, 1.44 supported
Digitone II 1.12 experimental: whole builds, linkable mods, SHARC mods (one mod's code on the DSP, at the master output, in mono) and selectable synth and filter mods through the mk2 machine interface; UI events and remote input checked on a unit, and sine variants with the same DSP bridge and layout ran ten-minute note sweeps and limited project/effects checks there (device evidence, DSP evidence and limits)
Octatrack (MKI and MKII) 1.40C supported: whole builds (format-1 mods); linkable mods with its own core: boots on an MKII, not yet run on an MKI
Model:Cycles, Model:Samples 1.13 supported: linkable mods with their own core (the hook bus's tick, draw, key and encoder events); builds work on both units (Transfer over USB)
Analog Rytm MKII 1.74 supported: linkable mods with its own core (the hook bus's tick, draw, key, encoder, SETTINGS and render events); builds with the core work on a unit (Transfer over USB)
Analog Four MKII 1.56 experimental: linkable mods with its own core, a proof of concept (core-a4: the Analog Rytm MKII's hook bus and mod storage); the hook bus, mod storage, the unused DDR and recovery checked on a unit (hooks-check-a4, store-check-a4, ddr-canary-a4)
other Elektron devices planned: see docs/DEVICES.md

Get started

  • In your browser, nothing to install: https://elekloader.github.io/elekloader/. Drop in your stock OS file, add mods from its shop or your own, build, and download the result. Your files are never uploaded.
  • Windows or macOS: the apps on Releases, with the core mods built in.
  • From source, on any system: Python 3.9 or newer and nothing else: python -m elekloader.

Each way needs the stock OS file for your device, exactly as Elektron publishes it; the .zip from Elektron's site works as it is. docs/INSTALL.md says which file each device needs and how each way starts.

Then tick your mods and build. Send the .syx to the unit with Elektron Transfer, as for any OS update; the Octatrack takes its .bin from the card. See docs/BUILDING.md.

If a custom OS will not start: the bootloader is never changed, so the stock OS file always restores the unit. On a Digitakt mk1, a Digitakt II, a Digitone mk1 or a Digitone II, hold FUNC while powering on for the startup menu, press TRIG 4 for OS UPGRADE, and send the stock .syx with Transfer's legacy OS upgrade mode (on the Digitakt II and the Digitone II, over its MIDI ports: not USB; the Digitone II's recovery was checked with stock 1.12 on a unit). On the Octatrack, hold FUNC while powering on, press TRIG 3 for MIDI UPGRADE, and send the stock .syx over 5-pin DIN MIDI (USB MIDI does not work for this). On a Model:Cycles or Model:Samples, hold FUNC while powering on, press TRIG 4 for OS UPGRADE, and send the stock .syx over 5-pin DIN MIDI. On an Analog Rytm MKII, hold FUNC while powering on for the STARTUP menu, press TRIG 4 for OS UPGRADE, and send the stock .syx over 5-pin DIN MIDI (not USB). The Analog Four MKII's is the Rytm's: FUNC at power-on, TRIG 4, the stock .syx over 5-pin DIN MIDI.

Mods

Mods are .elemod files: a whole build in one file, or linkable mods that combine, on top of the core mod for your device. Cores add things of their own. On the Digitone, for example, holding a track key opens the Mod Menu, where you pick what your mods add (docs/CORES.md):

The Digitone's Mod Menu: four tiles, each an icon over a label with its trig key's number, TABLES selected, and a scroll bar

Find mods in the web page's shop, or write your own: docs/ADAPTING.md takes you from the first build to done.

Contributions are welcome and encouraged. The core grows from what mods need: when yours needs an event, a table or a firmware address the core lacks, a pull request that adds it is the intended path (Growing the core). So are new devices, OS versions, fixes and docs (CONTRIBUTING.md). For something to start on, Contribute to elekloader! has the community's to-do list for the core.

Documentation

The docs are elekloader's wiki:

for pages
Using it Install · Build, flash and recover · Cores · The web page
Writing mods Adapting your mod · Growing the core · Contribute · The file format · Adding a device · coding agents: AGENTS.md
On your own site The kit · The engine in TypeScript
Maintaining it Releasing · The apps · Tests

Licence

GPL-2.0-or-later. See LICENSE, and NOTICE for the code that comes from digikit and for the credits. elekloader is not affiliated with Elektron. Flashing custom firmware is at your own risk.

Pictures in the README load from GitHub.

What's New v0.9.0released 3 weeks ago
elekloader 0.9.0

elekloader 0.9.0

The first full release since 0.4.0. It carries the cores built from the 0.9.0 commit and, as ever, no Elektron firmware: only cores, the apps, the kit and checksums.

0.8.0 was only ever a draft kit, so "what's new" below is everything since the 0.7 kit (kit-v0.7.0, 2026-10-22): 53 changes, mostly the Octatrack's mod stack, the Analog Rytm MKII and Analog Four MKII cores, the Model:Cycles and Model:Samples, and an experimental Digitone II.

The cores in this release

core version for since the 0.7 kit
core-4.1, core-4.1-os1.54 4.1 Digitakt mk1 (OS 1.53, 1.54) unchanged
core-dn1-4.1.1, core-dn1-4.1.1-os1.44 4.1.1 Digitone mk1 (OS 1.43, 1.44) unchanged
core-ar2-0.8 0.8 Analog Rytm MKII (OS 1.74) from 0.4: mod machines, page functions, write-through to the stored project, lockable mod parameters
core-ot-0.8 0.8 Octatrack (OS 1.40C) from 0.3.1: the hook bus grows from the frame to the voice (see below)
core-mc-0.3 0.3 Model:Cycles (OS 1.13) from 0.1: firmware locations as exports, a bulk area, ev_boot
core-ms-0.1 0.1 Model:Samples (OS 1.13) first core release

Every core was built from this release's commit, linted against its stock file, and the build is the one docs/CORES.md describes. (The core-ar2 toolchain was checked by rebuilding the published core-ar2-0.7 and comparing its SHA-256: identical.)

What's new since 0.7

Octatrack

  • core-ot 0.4 to 0.8 (#163, #169, #173, #175, #177, #184): the frame's end and MIDI out; the transport, a 120 Hz tick, a frame meter and exports; the project's lifecycle, the engine task, project and card data and battery RAM; the voice events (start, release, kill, bind, seek, trig apply, DSP flags, record); a run hash that halts the boot on a mismatch, with a boot gate in ot_emu; the edits mods' data, the voice's reset, a boot before the OS, the track icons and the SETUP knobs.
  • USB for the Octatrack (#164, #165, #176, #190, #217): usb-ot (the companion, USB MIDI first), usb-audio (USB audio out, five layouts, the layout an early setting), usb-audio-in (USB audio in on usb-ot's DSP feed). ot_dsp_feed now refuses a block that is not 16-byte aligned.
  • Events: seq-events-ot (step fire as events, the same API as the Digitone and the Digitakt; 0.2 adds ev_step_built), trig-events-ot (the trig dispatch as ev_track_trig, which may veto; 0.2 adds ev_tail_kill), intercepts-ot 0.2 (ev_midi_note_key).
  • machines-ot 0.1/0.2: source machines for the Octatrack, several in one build; the machines' tick and page in the UI tick, the chooser's level, the slot assigner's commit, ev_machine_set.
  • settings-ot 0.1: every Octatrack mod's settings in a MODS category of the MAIN MENU.
  • Safer linking (#167, #178): the 16 bytes the stock DELAY reads stay stock, and the linker checks the finished image against the stock one; every refusal has a fixture.
  • octabam (#160, #162, #170): sdk.octabam --machines (OCTA303 as a machine), --sites, bounties --upstream, and caves pinned on kept bytes.

Analog Rytm MKII (OS 1.74)

  • core-ar2 0.5 to 0.8 (#157, #179, #187, #188): mod machines through core, page functions (core_page_fns), mod fields written through to the stored project, and lockable mod parameters. 0.7 is also in the shop.

Analog Four MKII (OS 1.56)

  • A new device (#154, #180, #183, #205): core-a4 0.1 (hook bus and mod storage), parameter pages and views through core (0.2), page functions (0.3), and an OS-upgrade restart that cannot hang (0.4).

Model:Cycles and Model:Samples

  • core-mc 0.2 and 0.3, core-ms 0.1 (#192, #193, #194): the Model:Cycles' firmware locations as exports, the bulk area for mods' large buffers, and ev_boot after invalidating the caches the bootstrap leaves on.

Digitone II (experimental)

  • OS 1.12 support (#166), SHARC mods (#182, #185), synth and filter mods with their pages (#206), core-dn2 0.2 and its machine follow-up (#207). A missing filter's graph is drawn as MULTI-MODE's (#210).

Digitakt mk1

  • machine-pages 1.5 (#159): graphics that read the page's other values.
  • The extra SRC values have MIDI CCs (#158).

Shop, web page, CI and docs

  • The shop has core-ar2 0.7 (#209) and leaves octabam SYNTH v1.0 out until a rebuilt file has run on a unit (#202).
  • The web page is at elekloader.github.io/elekloader now (#213); the DN2 machine tests get their files under Pyodide (#208).
  • CI runs the firmware-free tests on pull requests, and macos-build runs in a protected environment (#212).
  • Docs: CORES.md as it is now and a doc-hygiene skill (#191); where Modwerk's Octatrack event names differ from ours, with the MIT credit for framer.s (#218).

Files

core-*.elemod plus SHA256SUMS.txt; the Windows app (elekloader-0.9.0-windows.exe), elekloader-kit-0.9.0.zip and elekloader-catalog.json are attached by the workflows afterwards. There is no macOS app in 0.9.0: its signing secrets need renewing first, so it comes with a later release. Mac users can run elekloader from source (docs/INSTALL.md).

Discussion

From the forum. Replies you write here are posted in the thread.
#1
Hello, I have been working on a project that centralizes where and how people flash their Elektron devices to make it easier for End Users to get CFW on their devices! Its called Elekloader and it works both inbrowser and locally: https://github.com/irpina/elekloader

Features: 
  • Supports various Elektron devices
  • Allows for disorganized development of Mods that would otherwise cause memory conflicts
  • Automatic conflict detection
  • A core mod that features an event bus allowing two mods to address the same code. 


Now featuring in browser support, flash your firmware without having to download Elekloader: https://irpina.github.io/elekloader/
Screenshot 2026-10-03 210907.png


If you'd like your mod to be featured in the mod shop please let me know, I don't want to steal eyes from anyones repos so I won't be posting anything to the shop without explicit permission unless I port the mod to elemod format myself (which I am working through for Octabam).
#2
I 'm facing this issue with the builder!
Does anyone have the same issue?

Finally find a way to make it work, by reloading the original 1.40C Fmw
Screenshot 2026-10-19 at 12.10.53.png
Log in or register to reply.
Language
Python
License
GNU General Public License v2.0
Stars
109
Forks
22
Created
09-26-2026
Last commit
2 weeks ago

Added by Neutron on 10-03-2026 · Last edited by Neutron, 1 month ago · History (2 versions)




User Profile Send Private Message E-mail Find all posts Find all threads Mod Tools Admin Tools