The Digitone II has three LFOs per track and an empty fourth page under
[MOD]. This fills it with a fourth LFO that behaves like the other
three. Select your firmware file. Then download a signed image.
Make sure that you can go back to stock before you flash a modified file.
The Early Start-up Menu flashes the stock firmware over MIDI. Do this one time with the stock
file, before you flash a modified file. Back up your +Drive. No tool here can recover it.
Go to 1.11 from 1.10E. If your unit has OS 1.10D, install the stock OS 1.10E
first. Then install OS 1.11, stock or modified. Do not go from 1.10D directly to 1.11.
Apply LFO4 last. LFO4 copies the parameter table of the instrument to a
new place with room for ten more records. From then on, the firmware reads the copy. A mod that
edits that table must be in the image before LFO4 makes the copy. If not, the edit
goes into a table that nothing reads.
Combines withFX Modulation,
Modulation Destinations, the
MIDI Arpeggiator and Arpeggiator p-locks (command line). Build those
first. Then load their download here. LFO4 also combines with LFO Waves,
which must also come first, and with the Boot Screen, in either order.
All of them share one start-up loader and one appended area. This page adds LFO4 to the data
that the area already holds.
Version and changes
This mod is at v1.0.7.
What changed in each version, newest first.
v1.0.7
On a busy pattern at a fast tempo, a short sound on one track could stop sounding while other tracks played. 1.0.5 added a check that held back a late update to the sound engine, and that check caused it. 1.0.7 removes the check.
v1.0.6
A sound with LFO4 settings that are out of range now loads without an LFO4. Before, LFO4 used such settings as they were. A sound saved by another firmware, or a damaged project, can hold such settings.
When you open the LFO4 page and a track has such a sound, a box names the track: "T3: LFO4 AREA HOLDS DATA LFO4 DIDN'T WRITE :)". Press YES or NO to close it. The box shows until you save the project and load it again.
v1.0.5
A busy pattern with LFO4 could drop a beat, and a note could then keep sounding after STOP. LFO4 now uses much less processor time during playback, and a beat is no longer dropped.
LFO4 now runs on a voice only while the voice can be heard: until its AMP envelope has ended. A voice with REL or DEC at INF keeps LFO4. An LFO4 aimed at an FX parameter always runs.
LFO4 keeps its phase while a voice is silent, so a note without an LFO trig carries on from where the LFO would be.
v1.0.4
A parameter the firmware does not know now gets stock's fallback settings again. Two more places in the firmware now read LFO4's settings from its own records. LFO4 operates as before.
v1.0.3
With the COMB+ filter, the FILTER page now shows the correct LPF value. Before, it showed 1 after you changed LPF, while the sound used the value you set.
On a MIDI track, an LFO now modulates the CC values with that track's own LFOs. Before, a MIDI track after track 1 could take its LFO values from another track.
v1.0.2
You can now combine this mod with Waverider, in either order. LFO4 operates as before.
v1.0.1
Projects you save or load with LFO4 no longer have LFO data written into them.
v1.0.0
First numbered version.
Unavailable for now: song data can be damaged in projects used with it.
Combines with
The table below is the row of this mod in the
compatibility table. dnfw mods matrix generates it.
✓: you can combine the two mods in either order. ✓*: you can combine them in one order
only. ✗: you cannot combine them. To see the reason, put the pointer on a cell.
One combination with this mod passed on an instrument: lfowaves, bootscreen and lfo4
(2026-09-30).
arpmodes
arpplocks
arpscale
bootscreen
degreetranspose
directjump
fxmod
layermidi
lfo4
lfolength
lfowaves
midiarp
moddest
reloadconfirm
sendloop
songguard
transients
usbprobe
waverider
A fourth LFO lfo4
✓
✓
✓
✓
✓
✓
✓*
✓
—
✓
✓*
✓
✓*
✓
✓
✓
✓
✓
✓
This mod combines with Arpeggiator SHUF and RAND, Arpeggiator p-locks, Arp offsets in scale, Boot screen, Degree transpose, Direct jump, Layering onto MIDI tracks, LFO ONE/HALF fix, Arpeggiator on MIDI tracks, Reload confirm, Send loop, Song guard, FM drum transients, USB SysEx probe (diagnostic) and Waverider, a sixth machine. This mod combines in one order only with LFO modulation of the FX (fxmod must be applied first), New LFO waveforms (lfowaves must be applied first) and More modulation destinations (moddest must be applied first). See the compatibility table.
1
Your firmware
Use a Digitone II OS 1.11 .syx file from Elektron. You can also use an image
that FX Modulation, Modulation Destinations or the MIDI Arpeggiator built.
or drag it here
2
What it adds
A fourth page under [MOD], with the controls of LFO1-3. Before it writes, the
page checks that each address this mod changes holds its stock bytes. If an image is different
anywhere, the page refuses it. It does not write the change in a place that only looks correct.
Where
On a synth track: [MOD], the fourth page. Its DEST browser works like LFO1-3's
Plays
Modulates on every voice, so polyphonic tracks and tracks that move between voices are modulated too
Keeps
Its settings are stored with the sound by SAVE PROJECT, and survive a power-cycle even without a save, like any stock parameter
Not included
MIDI: LFO4 has no NRPN numbers, so it cannot be set or recorded over MIDI.
P-locks: you can't lock an LFO4 parameter to a trig yet. When you try, the firmware shows
Lock mem full!. P-locks are planned for 1.1.0 (issue #350).
Writes
—
Confirmed on a Digitone II. The page opens with the stock LFO
controls, and its DEST browser works. LFO4 modulates on every voice. An explicit
SAVE PROJECT keeps its settings, and the settings stay after a power-cycle without a save.
This page applies exactly the bytes of that build. A byte-for-byte check runs when we package
the page.
None of Elektron's data ships with it. The copied parameter table has the
320 stock records and the ten records of LFO4, which are the LFO3 records with five fields
changed. The page builds this table from your file when you push Build.
3
Build it
The image is rebuilt, re-signed with the key derived from your own file, and
every integrity field is checked again. Nothing downloads unless all of them pass.
Combining with other mods
Each page applies one mod. To combine them, build on the other page first, then load
its download here: this one goes last. It writes 204 places in
section 3 and appends 23.7 KB to it.
FX Modulation: combines, applied first. LFO4 carries its ten Chorus record masks into the copy of the table. In the emulator, every LFO page, LFO4 included, lists the 24 FX destinations. Nobody has aimed LFO4 at one yet. The FX page refuses an image that this page built.
Modulation Destinations: combines, applied first. Its thirteen opened destinations are carried into the copy. That page refuses an image this page has built.
LFO Waves: combines. Build LFO Waves first. Then load its download here. LFO Waves edits three records of the parameter table, and LFO4 copies that table. So the order matters, and the LFO Waves page refuses an image this page has built.
Boot Screen: combines, in either order. Both add to the one appended area.
Waverider: combines, in either order. The platform writes the bounds both mods widen: the parameter count for LFO4, the machine count for Waverider.
What "combines" means here. A check makes sure that the bytes of the two
mods do not overlap. A test compares the output of this page with the output of the command line,
byte for byte, alone and after FX Modulation. LFO4 passed on hardware alone. It also passed on
2026-09-30 in one combination: LFO Waves, Boot Screen and LFO4.