SEM family: the sequencers (the Two Voice's, the OB-6's and the TEO-5's) #3

Open
opened 2026-10-11 23:39:08 +00:00 by bcox · 1 comment
Owner

The Oberheim Two Voice (TVS-1) has a small sequencer beside its two SEMs. mini-SEM has none; instruments/sem/synth.h lists it as not done.

Wanted: the Two Voice's sequencer for mini-SEM.

mini-SEM was built without Oberheim's manuals, and nothing about the sequencer has been read: the number of steps, whether its two rows drive the two SEMs separately or one drives pitch and the other something else, what it can modulate besides pitch, and how it is clocked and started are all unknown here. Find the Two Voice's owner's manual first and add it to docs/references.md.

Open questions for the owner:

  • whether this and the Poly-800's sequencer share anything in engine/;
  • whether a sequence is kept in the patch file;
  • how its knobs appear on the page.

The OB-6's and the TEO-5's sequencers

Added on 2026-10-11, when a few of the OB-6's and the TEO-5's things went into mini-SEM without their sequencers. The owner asked for them to be kept on this ticket with the Two Voice's.

By their published specifications, which is all that has been read (docs/references.md):

  • OB-6: a polyphonic step sequencer of up to 64 steps, with rests.
  • TEO-5: a polyphonic step sequencer of 64 steps.

These are a different kind of thing from the Two Voice's, which is an analog sequencer of a few steps set by knobs: they record notes and chords played on the keyboard, a step at a time. Whether one piece of work can serve both kinds is one more question for the list above. So is whether the polyphonic one is shared with the other instruments' step sequencers, #2 and #5, in engine/, beside the arpeggiator in engine/player.h.

Read both manuals first (#14).

The Oberheim Two Voice (TVS-1) has a small sequencer beside its two SEMs. mini-SEM has none; `instruments/sem/synth.h` lists it as not done. Wanted: the Two Voice's sequencer for mini-SEM. mini-SEM was built without Oberheim's manuals, and nothing about the sequencer has been read: the number of steps, whether its two rows drive the two SEMs separately or one drives pitch and the other something else, what it can modulate besides pitch, and how it is clocked and started are all unknown here. Find the Two Voice's owner's manual first and add it to `docs/references.md`. Open questions for the owner: - whether this and the Poly-800's sequencer share anything in `engine/`; - whether a sequence is kept in the patch file; - how its knobs appear on the page. ## The OB-6's and the TEO-5's sequencers Added on 2026-10-11, when a few of the OB-6's and the TEO-5's things went into mini-SEM without their sequencers. The owner asked for them to be kept on this ticket with the Two Voice's. By their published specifications, which is all that has been read (`docs/references.md`): - **OB-6**: a polyphonic step sequencer of up to 64 steps, with rests. - **TEO-5**: a polyphonic step sequencer of 64 steps. These are a different kind of thing from the Two Voice's, which is an analog sequencer of a few steps set by knobs: they record notes and chords played on the keyboard, a step at a time. Whether one piece of work can serve both kinds is one more question for the list above. So is whether the polyphonic one is shared with the other instruments' step sequencers, #2 and #5, in `engine/`, beside the arpeggiator in `engine/player.h`. Read both manuals first (#14).
bcox changed title from SEM family: the Two Voice's sequencer to SEM family: the sequencers (the Two Voice's, the OB-6's and the TEO-5's) 2026-10-12 02:46:03 +00:00
Author
Owner

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 labels
No milestone
No project
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#3
No description provided.