SEM family and Prophets: key assign, shift, level and detune for each zone, as the JX and the Jupiters have #60

Open
opened 2026-10-13 02:18:11 +00:00 by bcox · 0 comments
Owner

Ben decided on 2026-10-12 that the SEM family and the Prophets should come to have, for each zone, what the JX family and the Jupiters keep for each zone, and that it goes the SEM's way to the JX's and not the other. Not started.

What differs today

  • mini-JX and mini-JP: each zone has its own zone.assign, zone.key_priority, zone.unison_detune, zone.shift, zone.detune, zone.portamento, zone.bend, zone.hold, zone.lever and zone.level (the Jupiters a subset), under zone. and z2.zone. to z4.zone., on engine/seats.h. The JX-10 and the Jupiter-8 keep these for upper and lower separately.
  • mini-SEM and mini-P5: a zone has only its keys, its octave and its arpeggiator (zone.key, zone.top, zone.octave, arp.*). How keys are given voices, the unison's detune and the key priority belong to the whole instrument: voice.assign, voice.unison_detune, voice.unison_voices, voice.key_priority.

Why

The hardware has it. The OB-Xa's and the OB-8's split has a transposition for each half and a balance, and the OB-8's a detune for the lower; today those are reachable only through each half's sound, less the filter's tracking and the arpeggiator. The T8 keeps its unison switch in each program, so one side of its split can be a unison and the other not.

To work out

  • Stored patches. voice.assign, voice.unison_detune and voice.key_priority are in every stored mini-SEM and mini-P5 patch. They have to go on meaning what they did: most simply as the first zone's, with a zone that has no line of its own taking the first's.
  • Whether the two move onto engine/seats.h. Their modes are not the JX's: the SEM family has Rotate, voice.unison_voices and a turn kept by each zone; the Prophets have the Prophet-5's unison and the T8's. engine/seats.h has three ways and would want those added, or the two keep their own key handling and gain only the per-zone settings.
  • Which of the ten each instrument takes. zone.shift, zone.level and zone.detune are the ones the manuals speak for. zone.portamento, zone.bend, zone.hold and zone.lever are the JX-10's and may not belong on an Oberheim or a Prophet.
  • The page, which shows a zone's block through kZones: the new settings go in each zone's block, as the JX's are.
  • A parameter both have gets the same name in both: the JX's names stand.

Every instrument's bench that this touches wants running on the Pi before and after.

Ben decided on 2026-10-12 that the SEM family and the Prophets should come to have, for each zone, what the JX family and the Jupiters keep for each zone, and that it goes the SEM's way to the JX's and not the other. Not started. ## What differs today - **mini-JX and mini-JP**: each zone has its own `zone.assign`, `zone.key_priority`, `zone.unison_detune`, `zone.shift`, `zone.detune`, `zone.portamento`, `zone.bend`, `zone.hold`, `zone.lever` and `zone.level` (the Jupiters a subset), under `zone.` and `z2.zone.` to `z4.zone.`, on `engine/seats.h`. The JX-10 and the Jupiter-8 keep these for upper and lower separately. - **mini-SEM and mini-P5**: a zone has only its keys, its octave and its arpeggiator (`zone.key`, `zone.top`, `zone.octave`, `arp.*`). How keys are given voices, the unison's detune and the key priority belong to the whole instrument: `voice.assign`, `voice.unison_detune`, `voice.unison_voices`, `voice.key_priority`. ## Why The hardware has it. The OB-Xa's and the OB-8's split has a transposition for each half and a balance, and the OB-8's a detune for the lower; today those are reachable only through each half's sound, less the filter's tracking and the arpeggiator. The T8 keeps its unison switch in each program, so one side of its split can be a unison and the other not. ## To work out - **Stored patches.** `voice.assign`, `voice.unison_detune` and `voice.key_priority` are in every stored mini-SEM and mini-P5 patch. They have to go on meaning what they did: most simply as the first zone's, with a zone that has no line of its own taking the first's. - **Whether the two move onto `engine/seats.h`.** Their modes are not the JX's: the SEM family has Rotate, `voice.unison_voices` and a turn kept by each zone; the Prophets have the Prophet-5's unison and the T8's. `engine/seats.h` has three ways and would want those added, or the two keep their own key handling and gain only the per-zone settings. - **Which of the ten each instrument takes.** `zone.shift`, `zone.level` and `zone.detune` are the ones the manuals speak for. `zone.portamento`, `zone.bend`, `zone.hold` and `zone.lever` are the JX-10's and may not belong on an Oberheim or a Prophet. - **The page**, which shows a zone's block through `kZones`: the new settings go in each zone's block, as the JX's are. - A parameter both have gets the same name in both: the JX's names stand. Every instrument's bench that this touches wants running on the Pi before and after.
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#60
No description provided.