[jonathanwardle1992-beep]

Summary

• CREATE THRESHOLD SLICES sits on the AED SLICE menu, under DELETE ALL SLICES and above CREATE SLICE GRID (above CREATE BEAT GRID when Beat Slicer is installed).
• The base copies short absolute peaks into the module. The module finds rises through a threshold you set and proposes slice starts. The stock CREATE SLICES? / REPLACE SLICES? question still writes the markers. NO writes nothing. More than 64 slices is refused and the old slices stay.
• This is a draft. It is not in the catalogue, so the site cannot install it yet. An older base shows NO READ and writes nothing. Slicing needs a base built from this branch.

Guides: docs/module-guides/system.md and sdk/machines/octatrack/SAMPLE_EDITOR.md now say a waveform edit reads peaks through the base, a few frames at a time, and proposes starts only.

Test plan

• Host scan test: python -m unittest sdk.tests.test_threshold_slices (PASS)
• Sample-editor host fixtures for the peak read, menu and publication (PASS)
• Build a base from this branch and the module package (m68k-elf-gcc). This machine has no ColdFire gcc and no Docker, so that build was not run.
• Load both over USB. Open AED, AMP (SLICE), YES, CREATE THRESHOLD SLICES. Confirm a loop chops on its hits, NO leaves the old slices, and OVER64 refuses a result past 64.
• With Beat Slicer installed, confirm this row sits above CREATE BEAT GRID and both can be chosen.

Made with Cursor

[repeat98]

Hi, thanks for Threshold Slices. It's a good idea, and it hooks in the right way: one row in ot_sample_editor_actions, the base's confirmation question, and no stock site of its own. It doesn't overlap Beat Slicer either, since CREATE BEAT GRID makes an even grid and never reads the audio.

Which one goes first. I'll review this one now and make it your first module. Track Mutes (#931) and Play Start (#947) are both waiting on base work (#1023, and hooks for the TRACK key and the trig keys), so please leave them as they are until that's in. I'll come back to them there.

Here's everything I need, in one go:

1. Move the base part into its own pull request. The peak read changes the base every tester gets, and until now the sample-editor API has kept audio out of modules, so it needs its own Improvement: pull request that I review. That's also why the checks are red. module-contract fails because six base sources changed but the committed base wasn't rebuilt (octatrack-base.test.ts: "The committed Octatrack base is stale"), and module-pr-ok only reports that failure. Main is fine. Once the base files, their tests and the guide lines move out, this pull request is just the draft folder and its test.

2. Build the read on top of Improvement: add SNAP alignment to Octatrack sample editor #1165. twwwy's SNAP pull request goes in first (it waits only on my run of its base update), and it reads the same stock pair readers. The two clash in three places:

   • Both add the first member after the ABI-1 struct, so both structs have the same size. On a base with Improvement: add SNAP alignment to Octatrack sample editor #1165, your bytes check (device_module.c:85) passes, and reader->read is really SNAP's replace_options. Please put read after replace_options.
   • Improvement: add SNAP alignment to Octatrack sample editor #1165 already has a read_pair backend (it takes the capture) and mw_sample_editor_public_api(). Please reuse them instead of adding a second version of each.
   • Improvement: add SNAP alignment to Octatrack sample editor #1165 calls the pair readers only from engine work ("Engine task only" in sample_editor_service.h). Yours calls them from the UI task with the machine lock held (sample_editor_board.c:224-243), and Static reads come from the card. Please go through the same engine path, or show in the base pull request why the UI task is safe for Static files and recorder buffers.

   The base pull request also needs its own changelog/ file, the committed base rebuilt with npm run octatrack:base -- --stock OS.bin --beta --write (it needs the toolchain, the Docker image from Module/track mutes (MPC style)  #931), and that exact base tried on your unit over USB.

3. The detector re-arms on every waveform cycle. armed comes back whenever a single sample falls below half the threshold (threshold.c:57), and real audio does that at every zero crossing. So a loud held note gets a new slice every GAP: a one-second note at 50 ms comes out as about 20 slices. I worked that out from the code; the host tests don't catch it because they only feed flat blocks. Please follow an envelope instead (the peak with a short release) and re-arm when the envelope drops. Add a host test with a real tone burst that expects one slice.

4. "order": 40 in runtime.json. This table takes 50 to 90 for independent editor actions (HOOKS.md). Beat Slicer sits at 50, so any value in that range puts your row under CREATE BEAT GRID. Please update the README, the manifest overview and the description to match.

5. LICENSE. The font comes from Beat Slicer under MIT, and MIT needs twwwy's copyright line kept. Please add "Copyright (c) 2026 twwwy and contributors" to the LICENSE for device_font.c.

6. Rescanning. Every turn of an encoder starts both passes again, but the first pass (the peak) only depends on CH. Keeping the peak when THR or GAP changes makes adjusting much quicker on long samples.

7. The USB package. This module runs only over USB, so the package is the module. Add a verify.py gate like Beat Slicer's and build a private package ("A private USB package of a draft" in ADD_A_MODULE.md). Then try install, self-test, Keep/Undo and removal on your unit with the base from point 2. Add the scan time for a long sample and the CPU load while the popup is open to TESTING.md.

The order is #1165, then your base pull request, then this one with main merged in. Keep it in sdk/drafts/threshold-slices/ until the package and the unit results are done.

---

Generated by Claude Code

[jonathanwardle1992-beep]

The module side of the review is on this branch.

• A held tone stays one slice. The host scan passes, including a rectified tone burst that expects the trim start plus one hit.
• The row is order 60, so with Beat Slicer it sits under CREATE BEAT GRID.
• The peak from the first pass is kept when the threshold or the gap changes. Changing the channel scans again.
• LICENSE names the Beat Slicer font.
• Private package a020a947 was loaded for 12 seconds on OCTATRACK 1.40C, base 671f0afd406290cb, then rolled back. The slot ran, refusals stayed 0, and the tick value stayed 0x54530000. The editor was not opened, so the menu, the LEVEL insert, scan time and CPU were not observed. After rollback the unit was normal, generation 2, the same base, and no slot running.

The base waveform read still waits for its own change after #1165. This pull request does not open that. Guides: nothing.