elekloader

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).

The core for the Analog Rytm MKII, version 0.7, built from mods/core-ar2 at fb58292 (#155, #157, #179, #187, #205; mods/core-ar2 is unchanged since a621062). This is a pre-release. Once the mod shop lists it, the web page and the kit take it from here.

file	OS	sha256
core-ar2-0.7.elemod	1.74	f1e9cb2c39eb52af15e7cf8ad25596e46f550e4f748bc9dd60d63a44da2dd9c1

OS 1.74 only, as from 0.3.

New since 0.3:

• Parameter pages (0.4): pages that several mods share behind the stock page keys, with the page-key lists. The SDK header is analog-rytm-mk2/pages.h, and ADAPTING.md has "Parameter pages (core-ar2 0.4)".
• Machines (0.5): mods' own machines in the hidden machine slots. See ADAPTING.md, "Machines (core-ar2 0.5)".
• Page functions (0.6): core_page_fns, a page's own info function, asked before the stock one.
• Write-through (0.7): a field a mod sets from its page reaches the stored project at once, so it survives a power cycle without SAVE PROJECT. SAVE PROJECT AS keeps the mods' data too.
• The OS upgrade's restart (0.7): after a new OS is written, the restart can no longer hang on SUCCESS! REBOOTING.

Mods built for 0.3 with their own page sites don't link with it. These are rytm2_mods v1.2's lfo-rnd, voice-dac, euclid-accents, velocity-humanise and comp-preview: their sites overlap core's page sites. Use their versions built for 0.4 or later (rytm2_mods v1.3).

See mods/core-ar2 for every site and byte. On its own, it changes nothing the unit does except make the OS upgrade's restart safe.

Checked:

• On units, OS 1.74, as reported in mods/core-ar2's README:
  • parameter pages, the page key's step and the audio load (21 Oct);
  • machines (22 Oct);
  • write-through, SAVE PROJECT AS and the OS upgrade's restart (25 Oct, Iced-Cream, #187).
• Page functions (0.6) were checked in an emulator: 59 screens, pixel-identical to 0.4. Modwerk reports page-key builds from 0.6 working on a unit (#199).
• tests/test_rytm_mk2.py (9) and tests/test_store.py pass. It lints clean against stock 1.74. Every site and symbol of 0.3 is still there.
• Two builds from clean copies of the source give the same bytes.

The kit is elekloader's builder for websites: the TypeScript engine, a builder worker, a client for the page and a catalog format. A site serves the kit and a catalog, and its visitors build custom OS files in their own browser. Their stock OS file never leaves it.

This is a pre-release for websites, not an app release. The Windows and macOS apps, their cores and the web page stay on v0.4.0.

Files

File	sha256
elekloader-kit-0.7.0.zip	50c581b15bea8df121dc3a1ca34181681e7a135e85a8c3dbcf634dcee194a002
elekloader-catalog.json	f73bab2cd8815966201d94eb699dab1c85f111d482650471b3d5c940fdcb217b

• The kit, from commit 3b31ef3 (#156), built by the kit-build workflow with Node 24.19: python packaging/build_kit.py --out build/kit at that commit gives the same zip. The layout is the same as 0.6.0's: src/, dist/, tools/kit.ts (feed, sync, verify, lock), examples/minimal/, LICENSE (GPL-3.0-or-later), NOTICE, README.md and kit.json (version 0.7.0, protocol 1, every file's sha256). It still speaks protocol 1, so a site written for 0.4.0 to 0.6.0 can use it.
• The catalog is the mod shop's list in the kit's format (schema 1, revision 3b31ef3): 19 cores and 88 mods, for the Analog Rytm MKII (1 core), the Digitakt mk1 (6 cores, 33 mods), the Digitone mk1 (10, 21) and the Octatrack (2, 34). Each file is pinned by sha256 to its author's release or commit, and every one was read by the engine and downloaded again from its source.

New since kit-v0.6.0

The engine and the kit (main's at 3b31ef3, everything merged since 7b5b5b8):

• Mod storage on the Analog Rytm MKII (#140, #143, #147, #153). Mods declare fields in their mod.json, and the engine places them from a lockfile, the same way the Python does, byte for byte.
  • A build's store argument takes the lockfile from the build before. The reply's store is the new one: keep it with the selection, so fields keep their places when the mods change. Both are new optional fields, so the protocol stays 1.
  • Without a lockfile, the same mods always get the same layout.
• A new device in the engine: the Analog Four MKII 1.56 (#154). The catalog has no core or mods for it yet.

The catalog has 19 cores (was 18) and 88 mods, the same count:

• Analog Rytm MKII: its first core, core-ar2 0.3 for OS 1.74 (core-ar2-v0.3): the hook bus and mod storage.
• Digitakt mk1: DIGISLICER 2.5, with STRETCH; OB-1 0.5. machine-pages stays at 1.2. 1.3 is on its own pre-release (machine-pages-v1.3) and joins the catalog with an OB-1 that links beside it.

Checked:

• The kit's 48 tests pass.
• The zip was rebuilt from 3b31ef3 off CI and came out byte-identical.
• The run downloaded every pinned file again from its source, with no warnings.
• The release's two files match its SHA256SUMS.txt.

Use it

1. Check the zip against its sha256 above.
2. Follow its README.md (docs/INTEGRATING.md): serve dist/ or bundle src/, then copy the devices you offer from the catalog:

   node tools/kit.ts sync elekloader-catalog.json public/elekloader-catalog --device digitakt-mk1 --device digitone-mk1 --device analog-rytm-mk2
   

3. Pin both with tools/kit.ts lock, and check what you deploy with tools/kit.ts verify --lock.

A site written for protocol 1 should refuse any other protocol. init's reply says which one the kit speaks. Nothing from Elektron is in either file.

The core for the Analog Rytm MKII, version 0.3, built from mods/core-ar2 at 769d9aa (#140, #143, #145, #147, #153). This is a pre-release. Once the mod shop lists it, the web page and the kit take it from here.

file	OS	sha256
core-ar2-0.3.elemod	1.74	6b97dfb3d65ca7d9d292e4ed61dd845e43b2d4f6dc71e7e7d235f27abc4b3e58

OS 1.74 only. For 1.73, core 0.2 is the last core; build it from commit 92a99c9 (CORES.md). It is not attached here.

What it is:

• The hook bus: tick, draw, keys, encoders, SETTINGS rows and the render's input and output events.
• Mod storage: fields mods declare in their mod.json, kept in bytes the stock OS never uses or always holds at 0. Each field is stored per sound (56 bits), kit, global slot, pattern track, pattern or project. elekloader places the fields from the build's lockfile, so they keep their place from one build to the next.
• Track and pattern fields are written on the stock per-part saves too, so they survive a power-off without a SAVE PROJECT.

See mods/core-ar2 for every site and byte, and ADAPTING.md, "Mod storage". On its own it changes nothing the unit does.

Checked:

• On a unit, OS 1.74, as Iced-Cream reports in #147: eleven mods' fields kept through a power cycle with no save, kit save and reload, the +Drive sound library, SysEx and Overbridge kit transfers, and the VELOCITY MOD and AFTERTOUCH menus as on stock.
• tests/test_rytm_mk2.py (8), tests/test_store.py (16), and the TypeScript engine's tests (48) pass.
• Lint against stock 1.74, and store-check 1.1 links beside it.

machine-pages 1.3 for the Digitakt mk1, built from mods/machine-pages at 769d9aa (1.2.1 and 1.3 since #148, #149 and #150). This is a pre-release. It is a mod, not a core: it needs core 3.0 or newer (core-v3.0, core-v4.0), and the web page and the kit pick a core for it.

file	OS	sha256
machine-pages-1.3.elemod	1.53	de8406791685234fd179575483382e304ba0d31b1560ab0241bc328dbafcbd7b
machine-pages-1.3-os1.54.elemod	1.54	2ff4528fd7eed6b7c6839574ad1fe8f20c971a31c3975fb344463fa292b9659f

What it is: machine-pages owns, once, the firmware places every machine mod used to hook itself, and draws each machine's SRC and LFO pages from what the machine describes, so machine mods built for it combine. See the README and ADAPTING.md, "Machine pages". On its own it changes nothing the unit does.

New since 1.2:

• Version-4 sounds stay packed when a parameter changes (1.2.1, #148 by Simon Johansson; #150). When a parameter changes, the firmware writes it into the kit's stored copy of the sound as a plain word, which landed in the middle of a version-4 record's bit stream: a sound using the extra values could come back as a different sound after a reload. machine-pages now hooks the firmware's two in-place stores and packs the value into its own field. A record damaged before this is not repaired; saving the sound again writes a clean one.
• MIDI CC and NRPN take a page's knob range (#149 by gdeo607). An incoming CC or NRPN on a track's channel is clamped with the range of the track's machine's page, not the stock range of the parameter id: knob B on a page that gives it 0-127 now takes 0-127 from CC 17, not PLAY's 0-3.
• SRC keeps a sampleless machine's page (#150). On a one-page machine whose knob D is CM_NOT_SAMPLE, SRC no longer steps to ONESHOT's empty waveform view.

Beside the shop's mods: the same as 1.2, on 1.53 and 1.54, except OB-1 0.5.

• OB-1 0.5 is refused beside 1.3. It hooks the CC range lookup (0x40010d50) itself, pointing it at machine-pages, and 1.3 now owns that site, with the same result and NRPN as well. An OB-1 built without that site works with 1.3. The shop stays on machine-pages 1.2 until it lists such an OB-1.
• Everything else matches 1.2: it links with DIGISLICER 2.5, DT-FM 1.2.1, digi1_mods' machines, Digi EQ, Digi Matrix, Digi utilities, Tone+FX, digihealth and digistring, and NEIGHBOR 0.6 and SOPHIE 1.1.13 are refused beside it, as with 1.2.

Checked:

• tests/probe_digitakt_src.py --storage (digikit's emulator) on OS 1.53 and 1.54: 39 checks pass on each, among them the in-place sync and the sampleless SRC page.
• Lint: links with the released core 4.0 on both OS versions.
• On a unit, as their authors report: the sync fix (Simon, OS 1.54, a ModelDigi track edited over MIDI CC, the stored record matching the live sound in all 53 slots) and the MIDI ranges (gdeo607, OS 1.54, with Digi Mono and Digi Macro).

The kit is elekloader's builder for websites: the TypeScript engine, a builder worker, a client for the page and a catalog format. A site serves the kit and a catalog, and its visitors build custom OS files in their own browser. Their stock OS file never leaves it.

This is a pre-release for websites, not an app release. The Windows and macOS apps, their cores and the web page stay on v0.4.0.

Files

File	sha256
elekloader-kit-0.6.0.zip	1317770d150f409d137da46dc00fec47718cf9ec0c10723c43c0c29c7635673d
elekloader-catalog.json	42f18781f3eea29643842d1ce0988d3e3605398d32aab6527008872b215ffb6e

• The kit, from commit 7b5b5b8 (#138), built by the kit-build workflow with Node 24.19: python packaging/build_kit.py --out build/kit at that commit gives the same zip. The layout is the same as 0.5.0's: src/, dist/, tools/kit.ts (feed, sync, verify, lock), examples/minimal/, LICENSE (GPL-3.0-or-later), NOTICE, README.md and kit.json (version 0.6.0, protocol 1, every file's sha256). It still speaks protocol 1, so a site written for 0.4.0 or 0.5.0 can use it.
• The catalog is the mod shop's list in the kit's format (schema 1, revision 7b5b5b8): 18 cores and 88 mods, for the Digitakt mk1 (6 cores, 33 mods), the Digitone mk1 (10, 21) and the Octatrack (2, 34). Each file is pinned by sha256 to its author's release or commit, and every one was read by the engine and downloaded again from its source.

New since kit-v0.5.0

The engine and the kit (main's at 7b5b5b8, everything merged since 3acac10):

• Each build gets the newest core, as long as that core's RAM holds the mods (#93, #100). planBuild takes an optional holds test, and prepare makes its plan again once the mods are loaded. Mods report ram_bound and cores report ram_area. Both are new optional fields on Mod, so the protocol stays 1.
• The 4.0 cores' bigger RAM areas: 256 KB on the Digitakt mk1 (#95) and 1.25 MB on the Digitone mk1 (#91). If a build runs out of RAM, the linker's error now says which core would fit it.
• Sound-slot claims on the Digitone: two mods whose parameters store in the same sound slot can no longer be linked together (#114).
• New devices in the engine: Model:Cycles and Model:Samples 1.13 (#89), and the Analog Rytm MKII on 1.73 and 1.74 (#105). The catalog has no mods for them yet.

The catalog went from 11 cores and 65 mods to 18 and 88:

• Digitakt mk1: core 4.0 beside 2.1 and 3.0; machine-pages 1.2 (#107, #108); DT-FM 1.2.1; OB-1 0.4; digi1_mods on machine-pages 1.2.
• Digitone mk1: core-dn1 4.0 and 4.1; fxkit 0.1; machines 0.1; DigiCosm 0.1.1; DigiChroma; the effects 0.2 under their new names (DigiSwarm, DigiPrism, DigiTide, DigiTriad, DigiReel, DigiHoard, DigiHalo); digihealth 1.1.1.
• Octatrack: core-ot 0.3.1, which fixes the PURGE SAMPLES freeze.

Checked: the kit's 44 tests pass. The zip was rebuilt from 7b5b5b8 off CI and came out byte-identical. Every one of the 26 releases the catalog pins is published, none a draft. The release's two files match its SHA256SUMS.txt.

Use it

1. Check the zip against its sha256 above.
2. Follow its README.md (docs/INTEGRATING.md): serve dist/ or bundle src/, then copy the devices you offer from the catalog:

   node tools/kit.ts sync elekloader-catalog.json public/elekloader-catalog --device digitakt-mk1 --device digitone-mk1
   

3. Pin both with tools/kit.ts lock, and check what you deploy with tools/kit.ts verify --lock.

A site written for protocol 1 should refuse any other protocol. init's reply says which one the kit speaks. Nothing from Elektron is in either file.

fxkit 0.1 for the Digitone mk1 and Digitone Keys, built from mods/fxkit-dn1 at a60e3ba (#117). This is a pre-release. It is a mod, not a core: it needs core-dn1 4.1 or newer (core-dn1-v4.1), which the web page and the kit take for it.

file	OS
fxkit-0.1.elemod	1.43
fxkit-0.1-os1.44.elemod	1.44

What it is: what the Digitone's effect mods share (DigiSwarm, DigiPrism, DigiTide, DigiTriad, DigiReel, DigiHoard and DigiHalo from their 0.2). One effect at a time owns the audio, the synths muted, and fxkit gives each:

• A mixer (the effect's AMP page): IN L, IN R, L PAN, R PAN, MIX, BAL, VOL, WDTH. The input levels follow the Digitone mixer's own law, so 32 is unity and 127 is +24 dB, as loud as the Digitone's own input.
• Two LFOs with the stock LFO's rates, waves, fades and modes, aimed only at the effect's controls and the mixer's. Their pages are the stock LFO page: the stock's knob graphics, WAVE and SPH as one wave, DEST's list (YES picks), SPD and DEP in fine steps.
• P-locks kept in the pattern (LOCK mode on RECORD: hold a trig, turn a control), in one track's lock table, so the stock saves, copies and plays them; core-dn1 4.1's ev_note_queue times them.
• The MIDI hand-off (the stock UI for the MIDI tracks while the effect plays), saving in the effect's project data and a CPU guard.

On its own it adds nothing to the screen (README, ADAPTING.md, "Effects"). examples/dn-fx-gain (GAIN) is the smallest effect on it.

In the shop: beside the cores, as a framework piece. An effect that requires it ("requires": ["core", "fxkit"]) shows Needs fxkit, and its + ticks it.

Checked: the tests and the JS suite pass; in digikit's emulator, with core-dn1 4.1 and the seven 0.2 effects on 1.43 and 1.44, every stage of the firmware check passes and all ten screens are identical, the inputs come out at the stock's level at IN 32 and 127, and the LFO pages, DEST's list and the modulation were stepped through. Tested on a Digitone mk1 by its author with the 0.2 effects; still a beta.

The core for the Digitone mk1 and Digitone Keys, version 4.1, built from mods/core-dn1 at ced8e89 (#116). This is a pre-release. Once the mod shop lists these two files, the web page and the kit take them from here.

file	OS
core-dn1-4.1.elemod	1.43
core-dn1-4.1-os1.44.elemod	1.44

What 4.1 is: everything 4.0 has (1.25 MB for the mods, exclusive and insert audio, MIDI CCs and program changes, key LEDs, block parameters, the firmware exports), and ev_note_queue: each note event the Digitone queues for the render (the sequencer's trig fires, the keyboard, MIDI in, the arpeggiator), with the time it will play, before it is queued. A mod that plays a track's p-locks itself takes the step's locks there and applies them on time; fxkit plays the effects' p-locks this way. The first step's event as PLAY starts carries no p-lock list (and a lock trig on step 1 makes no event), so a mod reads that step's locks from the lock table when the transport starts (ADAPTING.md).

Which core a build takes: the newest the shop lists, so once these files are in the shop, Digitone builds take 4.1. A mod that needs the note queue says "core": "4.1".

Checked:

• Tests: test_sdk (4.1 is 4.0 and more by one site and one event), test_units, test_digitone, and the JS suite pass; the TypeScript engine builds the same firmware byte for byte.
• digikit's emulator, against stock 1.43 and 1.44: 4.1 with fxkit and the seven 0.2 effects passes every stage of the firmware check, and all ten screens are identical.
• On a Digitone mk1: 4.1 ran under the 0.2 effects on its author's unit.

core-ot 0.3.1 for the Octatrack MKI and MKII (OS 1.40C), built from mods/core-ot at 05d571c (#113). This is a pre-release.

file	sha256
core-ot-0.3.1.elemod	bd466e036022e78f22ad786906edce457f9ebb4934dde6a9775c483141032c06

PURGE SAMPLES no longer freezes the Octatrack. Every earlier core-ot has this bug, including 0.1, the one in v0.4.0.

• Cause: the arena base's literal has a 23rd use that isn't the arena: cmpa.l #0x40a955e0,a2 at 0x400254f8, which ends PURGE's walk over the 16 banks. The cores moved it with the base, and the walk stops only on an exact match, so it never ended.
• Fix: 0.3.1 leaves that compare stock (27 arena writes, was 28).
• Credit: found and fixed upstream in sambanks/octabam#753 (MIT).

What else it has: everything 0.3 has, which was never released on its own:

• the hook bus (from 0.2): tick, draw, keys, encoders, MIDI in and the audio frame;
• a RAM reserve sized to the mods, at most 10 MB (from 0.3).

Checked:

• In the Octatrack emulator (ot_emu, after a load), PURGE SAMPLES' routine is called:
  • with 0.3.1 it returns, as on stock;
  • with the released 0.1 and 0.3 it runs on and never returns.
• Shop mods: all 34 Octatrack mods in the shop link with it, and none has a site on that compare.
• Tests: test_octatrack 25/25 and test_octabam 20/20.

machine-pages 1.2 for the Digitakt mk1, built from mods/machine-pages at 6e1e099 (1.2 since #107 and #108). This is a pre-release. It is a mod, not a core: it needs core 3.0 or newer (core-v3.0, core-v4.0), and the web page and the kit pick a core for it.

file	OS	sha256
machine-pages-1.2.elemod	1.53	8526d61694c798bc765ae07b48ff613126d071813e887df516281c17a56c6c94
machine-pages-1.2-os1.54.elemod	1.54	d716bbeb70c8f7c9e8acc8bdb81681217eb8eb25ce700fe9a6ab786fed02d1f0

What it is: machine-pages owns, once, the firmware places every machine mod used to hook itself, and draws each machine's SRC and LFO pages from what the machine describes, so machine mods built for it combine. See the README and ADAPTING.md, "Machine pages". On its own it changes nothing the unit does.

New in 1.2:

• Seven extra SRC values per sound, for machines that need more than the eight stock knobs (#107, which follows #103).
  • They're stored in slots 46-52 (ids 164-170), and the mod claims them as soundslot:46-52.
  • Slot 0 stays the machine's id.
  • They save with the sound, lock, randomize, and appear in the LFO's DEST list.
  • The page marker is cm_ui_v32.
• A page knob may be a stock sound parameter, such as VOL on page 2 (CM_SRC_STOCK, #108).
• digistring 0.8.0 keeps working beside it. An earlier draft of the extra values broke the SRC view's knob getter, which digistring hooks.

Beside the shop's mods: the same as 1.1, checked with core 4.0 on 1.53 and 1.54 for all 31 Digitakt shop files.

• It links with Digi EQ, Digi Matrix, Digi utilities, Tone+FX, digihealth, digistring, DT-FM 1.2.1 and OB-1 0.4.
• The machine mods that draw their own pages (DIGISLICER 2.2, NEIGHBOR 0.6, SOPHIE 1.1.13, and digichain with Digi Mono, Digi Poly and Digi Macro) patch the same places, so the loader refuses them beside it.

Checked in digikit's emulator, with core 4.0, against stock 1.53 and 1.54:

• every stage passes;
• all nine screens are identical, and the audio is identical;
• with a test machine using the extra values, the same.

On a unit: 1.2 ran on a Digitakt mk1, tested by the author with no problems, as did 1.0 (OS 1.54, core 3.0 and six machine mods built for it).

The core for the Digitakt mk1, version 4.0, built from mods/core at a31fc89 (#95). This is a pre-release. The page and the apps keep taking their built-in cores from the latest release (v0.4.0) until the next one. Once the mod shop lists these two files, the web page and the kit take them from here.

file	OS
core-4.0.elemod	1.53
core-4.0-os1.54.elemod	1.54

What 4.0 is: core 3.0 with twice the RAM for the mods. It has the same code, sites, events, tables and exports as 3.0, and the linker lays the mods' code, tables and variables out from 0x47BC0000 to 0x47C00000: 256 KB in place of 128 KB.

• The space it uses: the whole gap between the sample pool's end and the audio input ring. Nothing else in the Digitakt's DDR is free, so 256 KB is as far as it goes.
• Machine mods built for 3.0 (machine-pages 1.1, DT-FM 1.2) link with it unchanged.

Which core a build takes: the newest core of the oldest major line that is new enough for the selection and whose RAM holds its mods.

• A selection over 128 KB takes 4.0, though its mods would take 2.1 or 3.0.
• A selection that fits keeps 2.1 or 3.0, and its bytes.

Checked in digikit's emulator with 4.0, digihealth 1.0 and a 200 KB test mod (207 KB in all), against stock 1.53 and 1.54:

• Every stage of the firmware check passes, and all nine screens are identical.
• The test mod's 200 KB, at 0x47BC1248–0x47BF1F88, are filled and read back right through thousands of UI ticks while the pattern plays.
• The same set is refused beside the released 2.1 or 3.0, and the message names 4.0.

The emulator doesn't model the sampler's audio input, which writes the ring just above the area: sampling is the thing to try on a unit.

The core for the Digitone mk1 and Digitone Keys, version 4.0, built from mods/core-dn1 at c490897 (4.0 since #91, picked by RAM since #93). This is a pre-release. The page and the apps keep taking their built-in cores from the latest release (v0.4.0) until the next one. Once the mod shop lists these two files, the web page and the kit take them from here.

file	OS
core-dn1-4.0.elemod	1.43
core-dn1-4.0-os1.44.elemod	1.44

What 4.0 is: everything 3.3 has (3.2's exclusive audio and MIDI CCs, 3.3's key LEDs, block parameters and firmware exports), and:

• 1.25 MB for the mods: the linker lays the mods' code, tables and variables out from 0x43EC0000 to 0x44000000, in place of the 128 KB at 0x47BE0000.
  • The OS's DDR operands end at a 384 KB ring (0x43E472C0-0x43EA72C0), and nothing of the OS's points above it in 1.43 or 1.44.
  • Five effects pedals, DigiCosm and DigiChroma fit one build, 243 KB in all.
• Insert audio (CORE_AUDIO_INSERT): an owner may take what the master stage made, an effect on everything the Digitone plays, with the synths on. A mod checks core_audio_caps before it offers an insert.
• ev_midi_pc: the program changes the unit receives, before the stock applies them.

Which core a build takes: the newest core of the oldest major line that is new enough for the selection and whose RAM holds its mods.

• A selection over 128 KB takes 4.0, though its mods would take 2.3 or 3.2.
• A selection that fits keeps 2.3 or 3.2, and its bytes.
• A mod that needs insert audio or program changes says "core": "4.0".

Checked in digikit's emulator, against stock:

• 4.0 alone, the program-change example, and 4.0 with five effects pedals plus DigiCosm and DigiChroma (243 KB), on 1.43 and 1.44: every stage of the firmware check passes, and all ten screens are identical.
• The seven effects: each owns the audio alone when opened from the Mod Menu.
• Program changes: taken ones stop at core's site.
• Tests: test_sdk (4.0 keeps all of 2.3 and 3.2, plus its one site, table and export), test_units, test_digitone, and the JS suite pass.

machines 0.1 for the Digitone mk1 and Digitone Keys, built from mods/machines-dn1 at f824cd8 (0.1 since #66). This is a pre-release. It is a mod, not a core: it needs core-dn1 3.1 or newer (core-dn1-v3.2), which the web page and the kit take for it.

file	OS
machines-0.1.elemod	1.43
machines-0.1-os1.44.elemod	1.44

What it is: sounds that play a machine mod's voice in place of FM, through the Digitone's own multimode filter, mixer and effects, with the AMP page's envelope. MACHINES in core-dn1's Mod Menu (hold a track key) picks the held track's machine, and a machine track's SYN1 and SYN2 knobs become the machine's parameters (README, ADAPTING.md, "Machines on the Digitone"). On its own it adds the menu and nothing else: machines come in mods of their own; examples/dn-sine-machine is one.

In the shop: with the cores, as a framework piece. A machine mod that requires it ("requires": ["core", "machines"]) ticks it there.

Checked in digikit's emulator: with the released core-dn1 3.2 and the example SINE machine, against stock 1.43 and 1.44: every stage of the firmware check passes and all ten screens are identical.

The kit is elekloader's builder for websites: the TypeScript engine, a builder worker, a client for the page and a catalog format. A site serves the kit and a catalog, and its visitors build custom OS files in their own browser. Their stock OS file never leaves it.

This is a pre-release for websites, not an app release. The Windows and macOS apps, their cores and the web page stay on v0.4.0.

Files

File	sha256
elekloader-kit-0.5.0.zip	f630b0fc9e03fb3a8fc729937e8aafa4849492d438359451d89515bb1e2344ad
elekloader-catalog.json	9aadff3bbc5586835776765364fe1fdf3b14b71a3fc97925c2e8e2c16084838e

• The kit, from commit 3acac10 (#74), built by the kit-build workflow with Node 24.19: python packaging/build_kit.py --out build/kit at that commit gives the same zip. As in 0.4.0: src/ (the engine and the kit in TypeScript), dist/ (the same as plain JavaScript), tools/kit.ts (feed, sync, verify, lock), examples/minimal/, LICENSE (GPL-3.0-or-later), NOTICE, README.md (the integration guide) and kit.json (version 0.5.0, protocol 1, every file's sha256). Protocol 1, as 0.4.0's: a site written for 0.4.0 takes it.
• The catalog is the mod shop's list in the kit's format (schema 1, revision 3acac10): 11 cores and 65 mods, for the Digitakt mk1 (27), the Digitone mk1 (4) and the Octatrack (34). Each file is pinned by sha256 to its author's release or commit, and every one was read by the engine and downloaded again from its source.

New since kit-v0.4.0

The catalog went from 6 cores and 55 mods to 11 and 65:

• Digitakt mk1: core 3.0 (core-v3.0) beside 2.1; machine-pages 1.1 (machine-pages-v1.1), which lets machine mods share a build; DT-FM 1.2.0, built for it: planBuild brings machine-pages with it and takes core 3.0 for both, and a selection that needs nothing from 3.0 keeps 2.1, as before; DIGISLICER 2.2 in place of 2.1; STRING and STRING-fast 0.8.0.
• Digitone mk1: core-dn1 2.3 in place of 2.2, and 3.2 for mods that need the 3.x line; DigiCosm 0.1.

The engine and the kit are main's at 3acac10: everything merged since a1be3ce.

Checked: the kit from this commit, with its own planBuild and engine on this catalog, built DT-FM 1.2.0 on OS 1.53 and 1.54 (core 3.0, machine-pages 1.1, DT-FM) and digihealth on 1.54 (core 2.1) byte for byte as the Python CLI does (#74).

Use it

1. Check the zip against its sha256 above.
2. Follow its README.md (docs/INTEGRATING.md): serve dist/ or bundle src/, then copy the devices you offer from the catalog:

   node tools/kit.ts sync elekloader-catalog.json public/elekloader-catalog --device digitakt-mk1 --device digitone-mk1
   

3. Pin both with tools/kit.ts lock, and check what you deploy with tools/kit.ts verify --lock.

A site written for protocol 1 should refuse another: init's reply carries it. Nothing from Elektron is in either file.

machine-pages 1.1 for the Digitakt mk1, built from mods/machine-pages at 33d80f7 (1.1 since #64 and #67). This is a pre-release. It is a mod, not a core: it needs core 3.0 (core-v3.0), which the web page and the kit take for it.

file	OS
machine-pages-1.1.elemod	1.53
machine-pages-1.1-os1.54.elemod	1.54

What it is: every machine mod used to hook the same firmware places itself (the SRC page's layout, labels, values, graphics and ranges, the LFO page's names, the render point after playback), so no two could share a build. machine-pages owns those places once and draws each machine's pages from what the machine describes, so machine mods built for it combine (README, ADAPTING.md, "Machine pages"). On its own it changes nothing the unit does.

New in 1.1: knobs that draw themselves (CM_DRAW, on a cm_ui_v31 page), which DT-FM 1.2.0 uses; a CM_DRAW knob on a cm_ui_v3 page gets the stock graphic.

Beside the shop's mods: it links with Digi EQ, Digi Matrix, Digi utilities, digihealth and digistring. The shop's machine mods that draw their own pages (DIGISLICER 2.2, NEIGHBOR 0.6, SOPHIE 1.1.13, DT-FM 1.1.0, and digichain with Digi Mono and Digi Poly) patch the same places, so the loader refuses them beside it. DT-FM 1.2.0, built for it, links.

Checked in digikit's emulator:

• With core 3.0, against stock 1.53 and 1.54: every stage passes and all nine screens are identical. The audio, on 1.53, too, but for the recording's silent end, a millisecond longer, as with core alone.
• The example SINE machine on it, against the same build with machine-pages 1.0: its menu, page, SHAPE turned, a trig, the pattern playing and the LFO page's DEST list: all seven screens identical.

On a unit: 1.0 ran on a Digitakt mk1 on OS 1.54 with core 3.0 and six machine mods built for it, and everything worked.

The core for the Digitakt mk1, version 3.0, built from mods/core at 7e69dc0 (3.0 since #57). This is a pre-release. The page and the apps keep taking their built-in cores from the latest release (v0.4.0) until the next one.

file	OS
core-3.0.elemod	1.53
core-3.0-os1.54.elemod	1.54

What 3.0 is:

• Core 2.1 and more. The same 39 sites with the same bytes, the same events and tables (the machines list included), and every 2.1 symbol where 2.1 has it. A mod built for 2.1 links with 3.0 unchanged.
• Firmware locations as exports (fw_track_blocks, fw_voice_params, fw_kit, fw_blit and the rest): a mod that names these instead of addresses builds for 1.53 and 1.54 from one source, with an empty 1.54 port (ADAPTING.md, "Firmware locations").
• Machines that describe their own SRC page (core_machine_ui). With the machine-pages mod drawing those pages, machine mods no longer hook the same firmware places, so several of them go in one build (ADAPTING.md, "Machine pages"). machine-pages is a mod, not a core, and is not attached here; examples/sine-machine is a whole machine to start from.

Using it:

• Which core a build takes: 3.0 only for a mod that needs it ("resources": {"core": "3.0"}, or needs_core in the shop's list). Every other Digitakt mk1 selection keeps 2.1, so today's builds keep their bytes: every selection of the shop's Digitakt mods links with 3.0 as it does with 2.1 (78 on 1.53, 66 on 1.54).
• Desktop apps (v0.4.0): add the file like a mod and tick it in place of the built-in 2.1.

Checked in digikit's emulator, against stock: core 3.0 alone, cold booted on 1.53 and on 1.54: every stage passes and all nine screens are identical. So is the audio, but for the recording's silent end, a millisecond longer, as with core 2.1.

On a unit: this exact core-3.0-os1.54.elemod ran on a Digitakt mk1 on OS 1.54, with machine-pages, NEIGHBOR, DIGISLICER, SOPHIE, Digi Mono, Digi Poly and digihealth in one build, and everything worked.

The core for the Digitone mk1 and Digitone Keys, version 3.2, built from mods/core-dn1 at 180bb77 (#68). This is a pre-release. The page and the apps keep taking their built-in cores from the latest release (v0.4.0) until the next one. The mod shop lists these two files through web/catalog.json, so the web page and the kit take them from here.

file	OS
core-dn1-3.2.elemod	1.43
core-dn1-3.2-os1.44.elemod	1.44

What 3.2 is:

• Everything 2.3 has: the hook bus, the voice note-on event, parameter slots, mod pages, project data and the Mod Menu grid. With 3.0's firmware locations as exports, so one mod source builds for 1.43 and 1.44, and 3.1's hooks for machines.
• Exclusive audio (core_audio): one mod may take the whole output from the render's master stage, with the synths muted if it likes, and keep large buffers in the Digitone profile's bulk area.
• ev_midi_cc: the MIDI CCs the unit receives, before the stock applies them. Its site sits beside Tone+FX's, and the two link together.
• fw_tempo, and the stock parameter pages' fonts (fw_font_label, fw_font_title).

DigiCosm is built on it.

Using it:

• Which core a build takes: a build takes 3.2 only for a mod that needs core-dn1 3.x. Every other Digitone selection keeps 2.3, the newest of the 2.x line, so today's builds keep their bytes (checked with digitables 1.3, digihealth 1.1 and DigiCosm 0.1: alone and together, each selection takes the core it should and links).
• Web page and kit: from the shop. The bulk area is in elekloader's package on main, which the web page runs.
• Desktop apps (v0.4.0): add the file like a mod and tick it in place of the built-in 2.0a. The 0.4.0 apps have no bulk area, so they refuse a mod with buffers there (DigiCosm).

Checked in digikit's emulator, against stock:

• Core alone, 1.43 and 1.44: every stage passes and all ten screens are identical. The audio after PLAY is the same sound slightly shifted in time, as with every core so far.
• Exclusive audio: with THRU and DigiCosm owning the output, the synths are silent and back at once after NO, also with PLAY pressed meanwhile.
• MIDI CCs: sent into the emulator's MIDI input, with DigiCosm's handler: taken CCs stop at core's site, every other one reaches the stock router (40 checks on each OS version).

On a unit: 3.2 runs on a Digitone mk1, with DigiCosm.

The core for the Digitone mk1 and Digitone Keys, version 2.3, built from mods/core-dn1 at d4aadf5. This is a pre-release. The page and the apps keep taking their built-in cores from the latest release (v0.4.0) until the next one. The mod shop lists these two files through web/catalog.json, so the web page and the kit take them from here.

file	OS
core-dn1-2.3.elemod	1.43
core-dn1-2.3-os1.44.elemod	1.44

What 2.3 is:

• It is core-dn1 2.2: the hook bus, the voice note-on event, parameter slots, mod pages, project data, and the Mod Menu that opens when you hold a track key on its own.
• In 2.3 the menu is drawn as a grid of tiles (#43). Tiles are two across and two down, each a mod's 16 x 16 icon over its label, with a scroll bar on the right.
• The menu lists what mods add to it; digitables 1.3 adds TABLES. With no such mod, holding a track key does nothing, as on the stock OS.

Using it:

• Web page and kit: every Digitone build takes 2.3, in place of 2.2 and of the release's 2.0a. A build takes the newest core of the oldest major line that is new enough.
• Desktop apps (v0.4.0): add the file like a mod, and tick it in place of the built-in 2.0a.

Checked in digikit's emulator, against stock:

• Core alone, 1.43 and 1.44: every stage passes and all ten screens are identical. The audio after PLAY is the same sound slightly shifted in time, as with every core so far.
• With digitables 1.3 and digihealth 1.1 (1.43): the same, except the AMP page's title reads 1/3, for digitables' TBL page.
• The grid itself: the arrows, a knob, scrolling, YES and the trig keys pick the right entry; TABLES opens the TBL page.

Not yet checked: the grid has not been run on a unit. 2.2's list menu has been.

The kit is elekloader's builder for websites: the TypeScript engine, a builder worker, a client for the page and a catalog format. A site serves the kit and a catalog, and its visitors build custom OS files in their own browser. Their stock OS file never leaves it.

This is a pre-release for websites, not an app release. The Windows and macOS apps, their cores and the web page stay on v0.4.0.

Files

File	sha256
elekloader-kit-0.4.0.zip	576b7d44639d4abeb1351a7771b4e3a1ef91f0b7cbcc69f64db9bb5255bf70ad
elekloader-catalog.json	06d8308f029bdc5e50f6f030e62b4e0be55c5da8d85f0f5fb8d3fe39957491e5

• The kit, from commit a1be3ce (#48):
  • src/: the engine and the kit in TypeScript, for a site with a bundler;
  • dist/: the same as plain JavaScript, for a site without one;
  • tools/kit.ts: feed, sync, verify and lock;
  • examples/minimal/: the smallest site;
  • LICENSE (GPL-3.0-or-later), NOTICE, README.md (the integration guide) and kit.json (version 0.4.0, protocol 1, every file's sha256).
• Reproducible. python packaging/build_kit.py --out build/kit at a1be3ce, with Node 24.19, gives the same zip, byte for byte.
• The catalog is the mod shop's list in the kit's format (schema 1, revision a1be3ce). It has 6 cores and 55 mods, for the Digitakt (19), the Digitone (2) and the Octatrack (34). Each file is pinned by sha256 to its author's release or commit, and feed read every one with the engine.

Use it

1. Check the zip against its sha256 above.
2. Follow its README.md (docs/INTEGRATING.md): serve dist/ or bundle src/, then copy the devices you offer from the catalog:

   node tools/kit.ts sync elekloader-catalog.json public/elekloader-catalog --device digitakt-mk1 --device digitone-mk1
   

3. Pin both with tools/kit.ts lock, and check what you deploy with tools/kit.ts verify --lock.

A site written for protocol 1 should refuse another: init's reply carries it. Nothing from Elektron is in either file.

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, plus hashes of the stock bytes it expects.
• The bootloader is never touched. Every output 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: overlapping bytes, memory, named resources and requirements.

Install

In your browser, nothing to install: https://irpina.github.io/elekloader/. Drop in your stock OS file, add mods or browse the mod shop, build, and download the result. Your files never leave your machine.

Windows: download elekloader-0.4.0-windows.exe below and run it. There is nothing to install and no Python needed. The exe is not signed, so Windows may say it protected your PC: choose More info, then Run anyway.

macOS: download elekloader-0.4.0-macos.dmg below, open it, and drag elekloader to Applications. It runs on Apple silicon and Intel Macs, and it is signed and notarized by Apple.

The first time, the app asks for your stock OS file, exactly as Elektron publishes it (the .zip works as it is). Add mods with + Install from file..., tick them, and BUILD FIRMWARE. Every device's core is built in and ticked for you with any mod that needs it. On Linux, run from source (Python 3.9 or newer): see the README.

Supported

Device	OS
Digitakt (mk1)	1.53, 1.54	linkable mods and whole builds
Digitone (mk1) and Digitone Keys	1.43, 1.44	new: linkable mods and whole builds
Octatrack (MKI and MKII)	1.40C	whole builds; new: linkable mods with its own core (checked in an emulator, not yet on a unit)

A mod is made for one OS version: one built for 1.53 is refused with a 1.54 stock file. Use the file its author made for your OS.

New in 0.4.0

• Digitakt OS 1.54 and Digitone OS 1.44, Elektron's releases of 2026-09-30 (Outbox 8 routing). Each has its own core.
  • The Digitakt's core 2.1 on 1.54 was checked in digikit's emulator against stock 1.54: every screen identical.
  • The Digitone's 1.44 core is the same code with 1.44's addresses. It lints, links and verifies, but the emulator does not boot stock 1.44 yet.
• The Digitone mk1 and Digitone Keys: whole builds, and linkable mods with the Digitone's core. digihealth 1.1 brings SYSTEM INFO to it.
• Core 2.1 (Digitakt): SRC machine slots. Mods add SRC machines past the stock four: digislicer's DIGISLICER and digineighbor's NEIGHBOR, together.
• The Octatrack's core reserves RAM for mods and copies their code there at boot. octabam's ColdFire modules convert to linkable mods (elekloader.sdk.octabam).
• elekloader in the browser, on GitHub Pages, with a mod shop of curated mods from their authors' releases.
• The macOS app, signed and notarized.
• For mod authors:
  • mod.json's ports builds one mod for several OS versions from one folder (ADAPTING.md, 3.10).
  • Code can be placed at a fixed address (fixed).
• Licence: GPL-2.0-or-later.
• The window opens at a size that shows everything, and it says "for other firmware" for mods made for another device or OS version.

Files

file	sha256
elekloader-0.4.0-windows.exe	d19d0656b0b6965c88f9fecf873c4fd9535f73a767ea6d0a9e51760a5d11a3a4 (built from v0.4.0 by the windows-build workflow)
elekloader-0.4.0-macos.dmg	385241d88723ecfb551a67455ae0bc50de8ea96699fe1e84f7217a2f3ecd403e (built from v0.4.0, signed and notarized by the macos-build workflow)
core-2.1.elemod	f38b0c193677a060b3fdb28fe71b9332be8a5e7d36ecaf91a3c86a61bab558eb: Digitakt mk1 1.53
core-2.1-os1.54.elemod	8c1fe78ccd1427d6a93f181eaad9f064efb65cf6dd683192dbcc33e83dc548b9: Digitakt mk1 1.54
core-dn1-2.0a.elemod	c6d9dbed28965bce4a827c292f499c8f5309187bf136ffb52e237bd01186b54f: Digitone mk1 1.43
core-dn1-2.0a-os1.44.elemod	5707a38e98047854eb12e5870430fb323126224f25b2a10b725badb93b97a41a: Digitone mk1 1.44
core-ot-0.1.elemod	e7b3054fba52bbd5fc88fe6c766d08bcc825fcb7e9ca968fd37c714225d8942f: Octatrack 1.40C

The cores are built into both apps, and built from v0.4.0's mods/ with the SDK. core-2.1.elemod is the same code as the core 2.1 that digislicer 2.0 shipped; only its build record differs.

Mods

• digislicer 2.1: DIGISLICER, the SLICE machine with a slice editor, AUTO, PIPO and trig slice mode (Digitakt 1.53, 1.54).
• digihealth 1.1: FAST AUDIO and SYSTEM INFO (Digitakt 1.53, 1.54), SYSTEM INFO (Digitone 1.43).
• digineighbor 0.6: a NEIGHBOR machine, a prototype (Digitakt 1.53, 1.54).

Custom firmware is at your own risk. elekloader is not affiliated with Elektron.