Repository navigation
ORBIT 0.4.1
ORBIT 0.4.1
Changes
- Brought the original OP-1's Synth / Drum / Event Tape / Mixer workflow and T1 engine / T2 envelope / T3 effect / T4 LFO controls to the FM-1 hardware controls and web editing interface. The default encoder colors are blue / green / white / orange.
- Mixer KNOB 1–4 controls LEVEL or PAN for the four tracks. SELECT also provides access to the existing SWING / LEVEL / LEN / PAN controls for the selected track.
- Added the Orbit wordmark and boot screen, English as the default web language, preview input and stereo visualizer taps, and recovery from interrupted editor restores.
- Reduced PHASE resonance window calculations and overload voice searches to resolve the existing host CPU and ALNK0 static budget failures. Golden references, budget baselines, and tolerances were not changed.
- Rebuilt the web emulator from the same C firmware while preserving the SLOOP and Felucca comparison binaries.
Installation and compatibility
Download the attached orbit.fwsc and verify it using SHA256SUMS. The installation identity remains FM-1_900; the firmware version is ORBIT 0.4.1.
python3 tools/fm1_install.py orbit.fwscThe FUN5 save format, support for reading older FUN1–FUN4 projects, ORBIT engine IDs, and editor protocol v9 are preserved. Back up your data before downgrading to ORBIT 0.3 / SLOOP 2.3, which cannot read FUN5 files.
The web emulator runs the actual C engine and stores projects and settings in the browser's IndexedDB. Event Tape edits sequencer events; it is not PCM audio recording. USB, SysEx, sample uploads, and Bluetooth are not supported in the emulator.
Validation scope
The pi32v2 build, memory and static budget checks, 19 Linux host programs and the full test runner, fresh macOS instruction-counted golden/CPU checks, and the latest native HTTP/PCM and actual package format checks passed. orbit.fwsc is 610,019 B, with SHA-256 31afad04333e6593e0333039c53f26b53ccab032b665cdc8e4aa3ec82bb53253. Golden and CPU baselines for the 12 existing independent-engine presets remain unavailable.
Results are recorded in the validation log. At the time of this release's validation, no physical FM-1 was connected, so flashing, boot, USB transfers, IRQ cycles, audio underruns, and latency were unverified. Passing the target build and browser checks does not establish hardware stability.