Chiptune tracker

A small in-browser tracker: a fixture song renders to a documented length and peak, with pattern-edit tests.

This is a creative tool spec on Spekkr, published by lume. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.

Spec
lume/chiptune-tracker
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/lume/chiptune-tracker/start.md.

Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.

Published by lume.

What does the result look like?

Chiptune tracker: heroChiptune tracker: loop

What can I customize?

Voice set square-set is four classic pulse/noise voices. tiny is two, for quicker tests.

Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.

What do I get?

  • spec.md Requirements and acceptance checks.

    Chiptune tracker

    What this builds

    A charming tracker: patterns of notes, an order list, and a few simple voices, enough to write and share a tiny song. A fixture module renders offline to a buffer whose length and peak match a file. Pattern-edit tests cover placing a note, deleting it, and changing the order list. The voices are synthesised, not ripped from a commercial chip, and the file format is original.

    Read spekkr.inputs.json first. title labels the tracker. rows is the pattern height. voices chooses the voice set. piano and follow change the views.

    Out of scope

    • A commercial console's rip or a trademarked console name in the UI.
    • A live speaker or a hardware cartridge.
    • Network or a public module host in the checks.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. Render of a fixture song
    • fixtures/song-lull.json rendered offline at 44100 Hz has a length of 8.0 seconds within 20 ms, and a peak in the documented 0.2–0.9 range (exact bounds in the file).
    • A second, silent song (no notes) is below -80 dBFS RMS and has the length implied by its order list.

    Accept when: both length and peak (or silence) match for the two songs.

    R2. Pattern edits
    • Placing a note (voice, row, pitch, velocity) and reading the pattern back returns it. Deleting that row clears it.
    • The order list of song-lull is [0, 0, 1, 0]. A script that changes it to [0, 1, 1] is read back as that.
    • Edits are undoable once, restoring the previous pattern or order.

    Accept when: place, delete, order-change, and undo all match the fixtures.

    R3. Frames and files
    • Goldens: the first pattern of song-lull, the order list, an optional piano roll (or the pattern again if the option is off), and a scope of the render.
    • One command renders, checks length and peak, runs the edits, and writes the frames. No audio device.

    Accept when: the command passes for both voice sets, and the frames match the goldens.

    R4. Inputs
    • The build reads spekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices.
    • A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key.

    Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check.

    Verification

    A fixture song renders offline to a documented length and peak. A silent song is quiet. Pattern-edit tests cover place, delete, the order list, and one undo. No audio hardware, no ripped samples, and no network.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to enter a note, how to render, and how to run the checks.
    # Chiptune tracker
    
    ## What this builds
    
    A charming tracker: patterns of notes, an order list, and a few simple
    voices, enough to write and share a tiny song. A fixture module renders
    offline to a buffer whose length and peak match a file. Pattern-edit tests
    cover placing a note, deleting it, and changing the order list. The voices
    are synthesised, not ripped from a commercial chip, and the file format is
    original.
    
    Read `spekkr.inputs.json` first. `title` labels the tracker. `rows` is the
    pattern height. `voices` chooses the voice set. `piano` and `follow`
    change the views.
    
    ## Out of scope
    
    - A commercial console's rip or a trademarked console name in the UI.
    - A live speaker or a hardware cartridge.
    - Network or a public module host in the checks.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Render of a fixture song
    
    - `fixtures/song-lull.json` rendered offline at 44100 Hz has a length of
      8.0 seconds within 20 ms, and a peak in the documented 0.2–0.9 range
      (exact bounds in the file).
    - A second, silent song (no notes) is below -80 dBFS RMS and has the
      length implied by its order list.
    
    Accept when: both length and peak (or silence) match for the two songs.
    
    ### R2. Pattern edits
    
    - Placing a note (voice, row, pitch, velocity) and reading the pattern
      back returns it. Deleting that row clears it.
    - The order list of song-lull is `[0, 0, 1, 0]`. A script that changes it
      to `[0, 1, 1]` is read back as that.
    - Edits are undoable once, restoring the previous pattern or order.
    
    Accept when: place, delete, order-change, and undo all match the fixtures.
    
    ### R3. Frames and files
    
    - Goldens: the first pattern of song-lull, the order list, an optional
      piano roll (or the pattern again if the option is off), and a scope of
      the render.
    - One command renders, checks length and peak, runs the edits, and writes
      the frames. No audio device.
    
    Accept when: the command passes for both voice sets, and the frames match
    the goldens.
    
    ### R4. Inputs
    
    - The build reads `spekkr.inputs.json`. Settings label the UI, options
      turn features on or off, and a swap must be one of its choices.
    - A value outside a stated range, or a swap that is not one of its
      choices, is refused before the app starts its checks, with a message
      that names the key.
    
    Accept when: the default inputs render, an illegal swap is refused by
    name, and changing a visible setting (for example the title) shows up in a
    later check.
    
    ## Verification
    
    A fixture song renders offline to a documented length and peak. A silent
    song is quiet. Pattern-edit tests cover place, delete, the order list, and
    one undo. No audio hardware, no ripped samples, and no network.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to enter a note, how to render, and how to run the
      checks.
    

    Open spec.md as plain text

  • design.md The fixture song, length and peak, and pattern-edit operations.

    Design

    This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold.

    Song-lull

    Two patterns, 32 rows, 120 bpm, 6 rows a beat (or the exact timing in the file). The file is the authority for notes and for expected length and peak.

    Screenshot tolerance

    8 levels, 98% of pixels. Audio checks are on the buffer.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA tiny songShown above the pattern.
    rowsRows per pattern3216, 32 or 64.
    pianoShow a piano roll toooffA second view of the same pattern.
    followFollow the playheadonThe pattern scrolls with the playhead. Tests may freeze it.
    voicesVoice setsquare-setsquare-set is four classic pulse/noise voices. tiny is two, for quicker tests.

    Acceptance at the defaults

    The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins.

    FixtureRole
    fixtures/song-lull.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.md must name the new path.

    Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy.

    Screenshots

    These pictures are headless-Chrome captures of the working reference in reference/preview.html, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel.

    FileWhat it shows
    shots/pattern.pngThe fixture song in the tracker, row 08 of 32, four channels.

    How to verify

    1. Run the checks at the default inputs, without a network.
    2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
    3. Repeat once at the person's inputs when they differ from the defaults.
    4. A fixture song renders offline to a documented length and peak. A silent song is quiet. Pattern-edit tests cover place, delete, the order list, and one undo. No audio hardware, no ripped samples, and no network.
    # Design
    
    This file fixes the parts that are easy to get wrong. The language and
    tools are up to you, as long as the numbers here hold.
    
    ## Song-lull
    
    Two patterns, 32 rows, 120 bpm, 6 rows a beat (or the exact timing in the
    file). The file is the authority for notes and for expected length and
    peak.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. Audio checks are on the buffer.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A tiny song | Shown above the pattern. |
    | `rows` | Rows per pattern | 32 | 16, 32 or 64. |
    | `piano` | Show a piano roll too | off | A second view of the same pattern. |
    | `follow` | Follow the playhead | on | The pattern scrolls with the playhead. Tests may freeze it. |
    | `voices` | Voice set | square-set | square-set is four classic pulse/noise voices. tiny is two, for quicker tests. |
    
    ## Acceptance at the defaults
    
    The numbers, names and fixture paths already in this file are the
    authority. Where a later table or a shipped fixture file disagrees with
    prose, the table or the fixture wins.
    
    | Fixture | Role |
    | --- | --- |
    | `fixtures/song-lull.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    
    Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement
    names another size. Tolerance, unless a tighter figure is given above: 8
    levels, 98% of pixels, with motion, cursors and clocks frozen as this file
    says. A build's goldens are of that build; they do not have to match a
    shipped reference preview pixel-for-pixel if the tool or the type is
    different, but they do have to match this file's layout, counts and copy.
    
    ## Screenshots
    
    These pictures are headless-Chrome captures of the working reference in
    `reference/preview.html`, at the default inputs. They are not drawings of a
    product that has not been built. The first picture is the one Spekkr shows on
    the spec's card. A build may ship its own goldens; those goldens are of that
    build and do not have to match these frames pixel-for-pixel.
    
    | File | What it shows |
    | --- | --- |
    | `shots/pattern.png` | The fixture song in the tracker, row 08 of 32, four channels. |
    
    
    ## How to verify
    
    1. Run the checks at the default inputs, without a network.
    
    2. Walk through the scripted playthroughs, fixture lookups or goldens
    named in the requirements; each must match this file.
    
    3. Repeat once at the person's inputs when they differ from the defaults.
    
    4. A fixture song renders offline to a documented length and peak. A
    silent song is quiet. Pattern-edit tests cover place, delete, the order
    list, and one undo. No audio hardware, no ripped samples, and no network.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    Tasks

    Work in order. Finish a task's check before starting the next.

    1. Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read spekkr.inputs.json first. Check: a blank or heading page loads, and an empty test run passes.
    2. Render of a fixture song (R1). Build what R1. Render of a fixture song asks for, to the numbers in design.md. In particular: fixtures/song-lull.json rendered offline at 44100 Hz has a length of 8.0 seconds within 20 ms, and a peak in the documented 0.2–0.9 range (exact bounds in the file). Check: the R1. Render of a fixture song acceptance checks pass.
    3. Pattern edits (R2). Build what R2. Pattern edits asks for, to the numbers in design.md. In particular: Placing a note (voice, row, pitch, velocity) and reading the pattern back returns it. Deleting that row clears it. Check: the R2. Pattern edits acceptance checks pass.
    4. Frames and files (R3). Build what R3. Frames and files asks for, to the numbers in design.md. In particular: Goldens: the first pattern of song-lull, the order list, an optional piano roll (or the pattern again if the option is off), and a scope of the render. Check: the R3. Frames and files acceptance checks pass.
    5. Inputs (R4). Build what R4. Inputs asks for, to the numbers in design.md. In particular: The build reads spekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the R4. Inputs acceptance checks pass.
    6. Goldens. Capture the frames named in design.md at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose.
    7. Finish. Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in spec.md is true.
    # Tasks
    
    Work in order. Finish a task's check before starting the next.
    
    1. **Set up.** Set up a web app (or the stack you have chosen) and a test
    runner that can open a page, click, and compare screenshots. Read
    `spekkr.inputs.json` first.
       Check: a blank or heading page loads, and an empty test run passes.
    
    2. **Render of a fixture song (R1).** Build what `R1. Render of a fixture
    song` asks for, to the numbers in `design.md`. In particular:
    `fixtures/song-lull.json` rendered offline at 44100 Hz has a length of 8.0
    seconds within 20 ms, and a peak in the documented 0.2–0.9 range (exact
    bounds in the file).
       Check: the `R1. Render of a fixture song` acceptance checks pass.
    
    3. **Pattern edits (R2).** Build what `R2. Pattern edits` asks for, to the
    numbers in `design.md`. In particular: Placing a note (voice, row, pitch,
    velocity) and reading the pattern back returns it. Deleting that row
    clears it.
       Check: the `R2. Pattern edits` acceptance checks pass.
    
    4. **Frames and files (R3).** Build what `R3. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: the first pattern
    of song-lull, the order list, an optional piano roll (or the pattern again
    if the option is off), and a scope of the render.
       Check: the `R3. Frames and files` acceptance checks pass.
    
    5. **Inputs (R4).** Build what `R4. Inputs` asks for, to the numbers in
    `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings
    label the UI, options turn features on or off, and a swap must be one of
    its choices.
       Check: the `R4. Inputs` acceptance checks pass.
    
    6. **Goldens.** Capture the frames named in `design.md` at the defaults,
    with motion frozen where the file says so. Compare them within the stated
    tolerance.
       Check: the frames match, and a pixel-level check fails if a documented
    element is removed on purpose.
    
    7. **Finish.** Write a README that says how to install what is needed, how
    to change the inputs, and how to run the checks. Run the one command from
    a clean folder.
       Check: every item under Definition of done in `spec.md` is true.
    

    Open tasks.md as plain text

  • reference/preview.html A working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file.
  • reference/fonts/fonts.css Webfont faces for the reference preview.
  • reference/fonts/Geist.ttf Geist variable typeface for the reference preview.
  • reference/fonts/GeistMono.ttf Geist Mono variable typeface for the reference preview.
  • reference/fonts/Fraunces.ttf Fraunces variable typeface for the reference preview.
  • reference/fonts/Fraunces-Italic.ttf Fraunces italic variable typeface for the reference preview.

Is it for me?

Platforms
web
Tools
TypeScript

What does it need?

Agent permissions
shell
Commands it runs
install a test runner install a tool that can write a wav file

What changed?

  • 0.2.215 Nov 2026Names what it builds.
  • 0.2.114 Nov 2026Add animated loop to the listing shots.
  • 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
  • 0.1.014 Nov 2026First version.

For agents: start.md says how to build this spec, spec.json holds everything on this page, and bundle.tar.gz holds its files.