SEM family: the OB-1 #37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ben asked on 2026-10-12 which instruments of the families already here were missed, and for an issue a family. Everything below is from recollection, with no manual read; issue #20's list was wrong in several places for the same reason, so read the manuals first and correct this. Each is to be an extension of the existing instrument, as the Jupiters and the JX family are, never a "model" switch.
filter.four_pole, split and double as zones, the OB-8's portamento ways), but never gone through as instruments. The OB-8's Page 2 is partly #9.Goes with #14: Oberheim's manuals were never read.
Done on the
family-extensionsbranch, without the OB-1. Written by Claude; nothing here has been played or heard, and Ben has not confirmed any choice in it.What was found
Oberheim's own, on archive.org, all now in
docs/references.md:The manuals against this issue's recollection
filter.four_poleand split and double as zones, F-ENV is a SEM's envelope 2 to VCO 2's pitch (vco2.env_pitch), pink noise is in both specifications (noise.pink, which was put in as the OB-X8's), OSC 2 ONLY isbend.target, the lever panel's own LFO isstick.lfo2, and the OB-8's VOLUME MOD and its two sawtooths were in as the OB-6's.engine/portamento.honly the steps are the OB-8's (QUANTIZE, half steps). Its other two are MATCH (off: each voice glides at a slightly different rate; the OB-Xa calls it OFFSET and starts with it on) and PORTAMENTO BEND (every note slides in from a set interval). Neither was here. Legato-only and time-per-octave are in no Oberheim manual read.What was built
Seven parameters, each at nothing until asked for, so every stored patch renders as before:
vco1.triangle(each sound).env.pedalandenv.pedal_release(each sound): controller 64 as the sustain footswitch, starting at the OB-Xa's 7 seconds, to the OB-8's 20.voice.low_note: a unison on the lowest key held.voice.portamento_offset: OFFSET, or MATCH off, as a fixed error in each voice's glide time.voice.portamento_bend: the OB-8's, -12 to +18 semitones, which is its quarter tone a key.Nothing in
engine/changed. No bench was run: nothing was added to what every patch works out a sample or a block. CLAUDE.md lists which settings make an OB-Xa, an OB-8 and an OB-SX.Not built, and why
vco*.tune,amp.level,vco*.detune), less the filter's tracking. The JX family'szone.shift,zone.levelandzone.detunewould fit.For Ben
Listed under "Open decisions" in CLAUDE.md. The ones that matter most: whether a unison should play the lowest key as it comes; whether controller 64 on this instrument should be this release pedal or #11's hold; how large the portamento offset should be, the manuals saying only "slightly"; and whether zones should gain shift, level and detune.
Ben answered on 2026-10-12 which key a unison plays: "put in a switch. the user can choose lowest if they want. that switch should also be available on other instruments where it is relevant." So
voice.low_notestays off as it comes on the SEM family, and the DW-8000, the Juno, the MS-20 (voice.low_note) and the JX family (zone.low_note) were given the same switch, on thefamily-extensionsbranch.The low note switch is now a key priority switch of three positions, as Ben asked on 2026-10-12 ("low, high, last"):
voice.key_priority, or a zone'szone.key_priority, 0 the latest key, 1 the lowest, 2 the highest, on the SEM family, the DW-8000, the Juno, the SH-101, the MS-20, the JX family and the Jupiters. Each starts where it was (the latest; the MS-20 the highest), and a Jupiter patch stored withzone.low_notestill loads. On branchfamily-extensions, not merged.The unison's key priority, again (2026-10-12, branch
family-extensions, not pushed). Ben asked that the shared switch start at whatever the original's own rule is. Sovoice.key_priorityon the SEM family now starts at 1, the lowest key, as the OB-X's, OB-Xa's and OB-8's owner's manuals have it, where it started at 0, the latest. A patch stored with novoice.key_priorityline played the latest and now plays the lowest; 0 gives back what it played. The highest, 2, is none of the three's.Ben's word on 2026-10-12: the OB-Xa and OB-8 are done; the OB-SX is a preset OB-X and is dropped as something to look into further; this stays open for the OB-1, which is not to be done now.
SEM family: the OB-Xa, OB-8 and OB-SX by name, and the OB-1to SEM family: the OB-1Progress on the night of 2026-10-12. This stays open for the OB-1 alone, which is not to be done now.
lfo.square_downin each sound andlfo2.square_downfor the second LFO, off as they come. On, the square rests at nothing and steps down by the depth wherever the LFO goes. He heard it and asked for nothing of it to change.vco1.xmodshould read as a switch at its hardware depth, which nobody knows. The OB-8's Page 2 LFO functions are #9.Everything said here is on
main, pushed, on the night of 2026-10-12. What was heard was heard on Ben's laptop, not on the Pi.