digislicer 2.2

A new SRC machine for the Digitakt (mk1), DIGISLICER: the SLICE machine with a slice editor, for OS 1.53 and 1.54, as an elekloader mod.

What's new in 2.2

It takes 15 KB of the RAM elekloader's mods share, where 2.1 took 92 KB. That leaves room for other mods: with core, digihealth and digineighbor, the four now take 49,232 of the 131,072 bytes instead of 125,976.

digislicer	code	data	in all
2.1	16,414 bytes	75,756 bytes	92,170 bytes
2.2	12,522 bytes	2,904 bytes	15,426 bytes

• Its big tables live on the Digitakt's own heap (16 MB, with megabytes free). These are the slice tables and its copy of your slices on the +Drive, 70 KB in all. They are set up the first time a DIGISLICER track plays or the editor opens, and the heap then has about 0.1 MB less free.
• Its code is compiled for size.

What it does is unchanged:

• the DIGISLICER machine and its slice editor (press SRC again on its SRC page);
• GRID = AUTO and PLAY = PIPO;
• the keyboard's trig slice mode.

Your slices are kept in the same files on the +Drive (/cfw/slices.a, .b), in the same format, with the same room: 128 samples of up to 64 slices each.

The README has every control.

Files

file	sha256
digislicer-2.2.elemod	20cfd79492c40289653c62667003e4a60eda7cc4ceed7abdb7fbde9e051a3527
digislicer-2.2-os1.54.elemod	c660a7232a5986a677696d61a18688256cfe208510d146c3ea876df50c738c27
core-2.1.elemod	f38b0c193677a060b3fdb28fe71b9332be8a5e7d36ecaf91a3c86a61bab558eb
core-2.1-os1.54.elemod	8c1fe78ccd1427d6a93f181eaad9f064efb65cf6dd683192dbcc33e83dc548b9

digislicer-2.2.elemod is for OS 1.53 and digislicer-2.2-os1.54.elemod for OS 1.54. Pick the file for the OS your unit runs; elekloader refuses the other one.

digislicer 2.2 needs core 2.1, the same core as 2.0 and 2.1. core-2.1.elemod (OS 1.53) and core-2.1-os1.54.elemod (OS 1.54) are elekloader 0.4.0's, built from its mods/core. The Windows and macOS apps bundle both from 0.4.0 on. From source, install the core for your OS with the mod.

Install

1. Get elekloader 0.4.0 or later, and the stock OS file your unit runs, Digitakt_OS1.54.syx or Digitakt_OS1.53.syx, from Elektron.

2. In elekloader's window, Install from file the digislicer file for that OS (from source, its core too). Tick digislicer, choose your stock file and Build firmware. Or:

   python -m elekloader.patch --stock Digitakt_OS1.53.syx \
       --mod core-2.1.elemod --mod digislicer-2.2.elemod \
       --out Digitakt_OS1.53-slicer.syx --version DS22

3. Send the .syx to the unit as you would any OS update.

Recovery: hold FUNC while powering on for the startup menu, then send the stock OS file. elekloader never changes the bootloader.

It combines with digihealth and with digineighbor 0.6.

Checked

In digikit's emulator, against 2.1:

• The editor tests:
  • the arrow, cursor and vertical zoom tests give exactly 2.1's results, frame for frame;
  • the editor and menu tests give the same slices, splits, deletions and stored records;
  • they differ only where the emulator groups knob notches by the UI's timing, which happens on stock's own SRC page too.
• Your slices on the +Drive: an edit is saved, and loads back the same after the copy in RAM is wiped.
• The keyboard's trig slice mode and PIPO: the same results as 2.1.
• A DIGISLICER script, on OS 1.53 and on 1.54. It picks DIGISLICER, sets GRID to AUTO and PLAY to PIPO, opens the editor, uses the keyboard's trig slice mode and plays the pattern. Every screen and the audio are identical to 2.1's.
• The heap: after the tables are set up, every free list is intact.
• Cold boots against stock, on OS 1.53 and 1.54, with and without digihealth and digineighbor: every screen is identical, and the audio is identical or 1 ms longer at its silent end.

Not yet tried on a unit. On one, digihealth's SYSTEM INFO should show about 0.1 MB less RAM free once a DIGISLICER track has played, and no further drop after that.

Custom firmware is at your own risk. Not affiliated with Elektron.