bcox/mini-800
1
0
Fork 0
Code Issues 36 Pull requests Projects Releases Packages Wiki Activity Actions

Poly-800: the step sequencer #2

New issue
Open
opened 2026-10-11 23:39:08 +00:00 by bcox · 1 comment
bcox commented 2026-10-11 23:39:08 +00:00
Owner
Copy link

The Poly-800 has a step sequencer on its panel. mini-800 has none: CLAUDE.md lists it among what is "also on the hardware" and says everything other than the voice can be MIDI for now.

Wanted: the Poly-800's sequencer, played through engine/player.h as the arpeggiator is, so that no instrument's synth.h knows of it.

Before building it, read the owner's manual's pages on the sequencer (linked from docs/references.md) for how many steps it holds, how notes, rests and ties are entered, how chords are stored, and what its clock can follow. None of that has been read yet.

Open questions for the owner:

  • whether it belongs in engine/ for every instrument, as the arpeggiator does, or to the Poly-800 alone;
  • whether a sequence is kept in the patch file or beside it;
  • how steps are entered with no hardware panel (the page, MIDI, or both).
The Poly-800 has a step sequencer on its panel. mini-800 has none: CLAUDE.md lists it among what is "also on the hardware" and says everything other than the voice can be MIDI for now. Wanted: the Poly-800's sequencer, played through `engine/player.h` as the arpeggiator is, so that no instrument's `synth.h` knows of it. Before building it, read the owner's manual's pages on the sequencer (linked from `docs/references.md`) for how many steps it holds, how notes, rests and ties are entered, how chords are stored, and what its clock can follow. None of that has been read yet. Open questions for the owner: - whether it belongs in `engine/` for every instrument, as the arpeggiator does, or to the Poly-800 alone; - whether a sequence is kept in the patch file or beside it; - how steps are entered with no hardware panel (the page, MIDI, or both).
bcox commented 2026-10-13 00:10:54 +00:00
Author
Owner
Copy link

Ben decided on 2026-10-12 that no instrument's sequencer is cloned: one sequencer is built for every instrument, #56, with the features he chooses from each hardware one. This issue stays open as a reminder to mine this sequencer for features, and is not to be built as it stands.

Ben decided on 2026-10-12 that no instrument's sequencer is cloned: one sequencer is built for every instrument, #56, with the features he chooses from each hardware one. This issue stays open as a reminder to mine this sequencer for features, and is not to be built as it stands.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bcox/mini-800#2
No description provided.