Glossary
The words that Oscyl’s apps, code and documentation use, in alphabetical order. Each entry links to the page that tells more.
Audition
To play a program on the synth without storing it. Oscyl sends the program to the edit buffer. An audition plays one program, for example a sound that you pick in Generate. Live plays each edit as you make it, and Hold to compare plays the saved program while you hold the button. See What happens when you plug in a synth.
Backup
A library file that holds what a synth’s slots held before Oscyl wrote to
them. Sync and oscyl restore make one first and write nothing when they
cannot. See The command line.
Bank
A numbered run of slots on a synth, for example U1 on the Prophet Rev2. A bank is writable, or it is a factory bank that Oscyl never writes. See The driver contract.
Character
A kind of sound that Generate can make, such as “fuzz bass” or “power chord”. Each driver lists its own characters. See What Oscyl is.
Conformance suite
The checks that every driver must pass against its
simulator, in the crate oscyl-conformance. CI runs them on
every commit. See The driver contract.
Driver
The code that teaches Oscyl one synth model: its messages, its program bytes,
its files and its editor pages. A driver is a Rust crate under
crates/drivers/. See Architecture.
Edit buffer
The synth’s working copy of the program that it plays now. Oscyl changes it to audition a program. The synth forgets it when you pick another program, and its stored programs do not change.
Field
One parameter of a program, such as a filter’s cutoff, with its range of raw values. A driver lists its fields in a fixed order. See The driver contract.
Generate
The part of the apps that makes new programs. You pick a
character and set four dials: Bright, Movement, Grit and
Ambience. Oscyl makes six programs, and you can vary them, cross two of
them, or keep one. Each has a recipe code. The command line
does the same with oscyl generate.
Library
A list of programs for one synth model, kept in a file on your computer or
phone. Oscyl’s own format is .oscyllib. Oscyl also reads and writes each
synth’s own file formats. See
The .oscyllib library format.
Live
The switch in the apps that plays every edit on the synth at once, in the edit buffer. On a minilogue xd, Live also follows the synth’s knobs and program changes. See What happens when you plug in a synth.
logue SDK
KORG’s kit for writing user units: oscillators and effects in C. The minilogue xd, the prologue and the other logue synths load them into their unit slots. “logue” is KORG’s name for this family of synths. See User unit.
Oscillator unit
One prebuilt logue SDK unit, made by Oscyl, whose sound comes from data. Oscyl fills it with a new oscillator and loads it into a minilogue xd or a prologue, only when you keep one. It is optional, and it is not a synth engine. See The oscillator unit.
Program
One sound of a synth: all its parameter values and its name, as the synth stores them in one slot. KORG calls it a program. Other makers say patch or preset.
Recipe code
A short text that names a sound from Generate: its character, its four
dials and its seed, for example power-chord-ygy6c734s69jn. The same code
makes the same sound again, on any synth that has that character.
Request engine
The part of oscyl-driver that runs a synth’s protocol. It keeps one
request in flight, matches each reply to it, and fails a request whose reply
does not come. It is sans-IO: it never touches a port or a clock. See
Architecture.
Session
A driver’s protocol for one connected synth, behind the trait
DriverSession. Most sessions use the request engine.
See The driver contract.
Shelf
The unit files that Oscyl keeps for each synth, ready to load into a free unit slot. See The command line.
Simulator
A driver’s model of its synth, in code. It answers messages as the synth does, with no sound. Tests, the conformance suite and the apps’ demo mode use it. See Try Oscyl without a synth.
Slot
One numbered place for a program in the synth’s memory. The apps number slots from 1, the code from 0.
Sync
The action that writes your edited programs to the synth, after a backup. See What happens when you plug in a synth.
Tier
How far Oscyl trusts a driver. Tier 3 compiles, and Tier 2 passes the conformance suite. Tier 1 is also checked on the real synth for each release. See Supported synths.
User unit
A user oscillator or effect, made with KORG’s logue SDK, in one of the unit slots of a minilogue xd or a prologue. Oscyl lists them, loads them and clears them. See Supported synths.