Opus 2
Opus 2 is out as a beta: not a bigger pack, but a plugin manager for the OP-1.
- Custom firmware
- Beta
- Low brick risk
- Reversible
Source codeWebsite: opus-op1.pages.dev
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Opus 2 is a firmware mod for the original Teenage Engineering OP-1 on firmware #246 (not the OP-1 field). Its
small core loads plugins: .opmod files you copy into a mods folder on the OP-1's USB disk. Every feature is a
plugin, so you pick the mods and swap them as files, with no reflashing.
Beta 2: sequencers through the bridge, lighter audio, and fixes from the first week. Still a beta: it has run in an emulator with the OP-1's own firmware and on my own OP-1. Back up your tape, synth and drum folders first.
Get it
- The core. Make the update on https://opus-op1.pages.dev/patcher/ from your own copy of TE's
op1_246.op1. It runs in your browser and nothing is uploaded. Install it through the OP-1's update mode: switch it off, hold COM while switching it on, press 1, copy the file onto the "OP-1" disk and eject it. Never choose 7 or 8 there, they erase your sounds and tape. - The plugins. Download
opus2-starter-pack.zipbelow, put the OP-1 in disk mode (shift + COM, then T3) and drag the zip'smodsfolder onto the disk. It merges with the one there and replaces the plugins that changed. Or take only the.opmodfiles you want. Then eject the disk on your computer (the OP-1 leaves disk mode): they load at the next start. - Coming from op1r or Hundekraft? Add
bridge.opmodtoo (below).
From beta 1: the same steps. Make the new file (the old one is beta 1's), install it, then drag the new pack's
mods folder onto the disk, and the new bridge.opmod if you use it. Your sounds, presets and tape stay.
| Target | the original OP-1, firmware #246 only |
| The update | op1_246_opus2.op1, 13,150,681 bytes |
| Its SHA-256 | 763fb0a463024eb24a70b5039979d6280a7a59c6b070cf3088aa513aa19bd0af |
| Made from | TE's op1_246.op1, SHA-256 c5315218f825f143b415ca554516541898abee843d3a236df0b54c04e1fb13a9 |
| The starter pack | opus2-starter-pack.zip, 20 plugins, SHA-256 5f9f0a7b07957c630b7c9fa017e55c7561b2e089d323e99086a61b38ad8a3843 |
| The bridge | bridge.opmod 0.8.0, SHA-256 9be7d1b0bbf542675f4da355b1b31a73af52929a4c30b440c5212cf109b868e6 |
Every file's SHA-256 is in SHA256SUMS.txt.
What's new
- Lighter audio. Plugins' audio memory now sits where the screen's updates don't slow it down. With the pack installed and nothing playing, the audio load on my OP-1 went from about 36-43 % to about 10 %. Plate and chorus rest while nothing reaches them, and plate, chorus, bitcrush and outatime do the same sound in fewer cycles.
- Plate fixed. It lagged or got switched off on the master: its audio was slowed by the screen sharing its memory, at times enough for the CPU guard to switch it off. Thanks to Audivit for the report.
- Sequencers through the bridge (bridge 0.8.0): op1r's chord, dots, euclid, grids, oracle and peal, and Hundekraft's c64arp, dots, euclid, oracle and peal, as new rows in the OP-1's sequencer list (shift + the sequencer key), each with its own page. Their patterns are saved, and left / right move the keyboard's octave as on the stock sequencers.
- FN + blue push switches Fx overdrive's second effect on an effect page where the effect itself takes the blue push, such as a bridged one. Thanks to EmergingStates for the report.
- Engine pages follow the LFO in every value they show, as the OP-1's own screens do.
- An incompatible preset (a sound whose engine isn't installed) is refused again, with "needs" and the engine's name. Since beta 1 it loaded as iter.
- The diagnostics' task manager no longer counts the plugins' work twice under "opus core".
- For plugin authors: core 2.8 runs plugin sequencers, keeps a page's still part (
opus_page_still) and gives audio buffers memory of their own (opus_alloc_audio). A page's art may be up to 128 KB. The plugin kit's docs are updated.
New plugin versions: amp 1.0.5, bitcrush 2.0.1, chorus 2.0.2, dx 0.4.0, outatime 1.1.3, Fx overdrive 2.0.1, plate 2.0.4, scales and chords 1.1.0, the bridge 0.8.0. The others are as in beta 1. Every plugin with its keys, CPU and memory: https://opus-op1.pages.dev
Known issues
- With a colour theme, the dim edges of text in a colour other than green can look green on the OP-1's screen. TE's own screens show it too: it's the panel, not Opus.
- With USB plugged in, holding Stop at power-on makes the logo take longer.
- In the bridge: swapping effects between bridged plugins can stop the OP-1 as you leave the effect list, and a colour theme misses some shades on bridged plugins' pages.
The bridge (alpha)
bridge.opmod is a download of its own, not part of the starter pack. It runs op1r's synth engines, effects and
sequencers (.op1p) and Hundekraft's (.knl) on Opus as they are, with their own screens and pages, and sounds saved
with them play. Put new plugin files in the disk's mods/bridge folder. The bridge's settings list every file it
found, what loaded and why a file didn't. Where both firmwares have a sequencer of the same name, the first file
loads.
It's an unstable alpha, expect bugs. Opus's own plugins run much better on Opus 2, since they're made for its core, while a bridged plugin runs through a layer that stands in for its own firmware. Porting a plugin to Opus 2's format is the way to go. Not bridged yet: LFOs (Hundekraft's quad) and other features, drum and sampler engines, and engines that play samples.
op1r is by popcorp and Hundekraft's firmware by Hundekraft. Every bridged plugin stays its author's work.
Going back
te-boot, the OP-1's own updater and recovery, is never touched, so the way back is always there.
- To stock or another firmware: Opus's menu, T1 (system), the cleaner: turn green to "at restart", then switch the OP-1 off and on. Then install the other firmware through update mode as above (stock is TE's
Before you start
- How hard is it?
- EasyCopy a file or use a web page. No extra software.
- What you need
- A computer
- Can it break my device?
- Very unlikely to break anything.
- Can I undo it?
- Yes. You can go back to the official software.
Did it work for you?
Did Opus 2 v2.0-beta.2 work on your Teenage Engineering OP-1?
On v2.0-beta.2: 1 works · 0 didn't · 0 bricked
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: Teenage Engineering OP-1.
No compatibility information yet.
Getting started
From the project's README ("Opus"):
Mods for the original Teenage Engineering OP-1, firmware 246. By LizardMan.
A hobby project, built in free time and at its own pace. Help is always welcome, and if you'd like to support it, there's Ko-fi.
Opus 2 is out as a beta: not a bigger pack, but a plugin manager for the OP-1. Its small core loads plugins, .opmod files you copy into a mods folder on the OP-1's disk. Add one, remove one, swap them, no reflashing. The starter pack has all of Opus 1's features as plugins, plus dx (a DX7 voice player for your own .syx banks), outatime (a time-travel synth engine), iter (the OP-1's own hidden engine) and a Halloween colour theme. The bridge, an alpha, runs op1r's and Hundekraft's synths, effects and sequencers on Opus.
- The core: make the update from your own stock firmware with the patcher at https://opus-op1.pages.dev/patcher/. It runs in your browser and nothing is uploaded.
- The plugins: the starter pack, each plugin on its own and the bridge are in Releases.
- Your own plugins: the plugin kit (GPL-3.0).
Opus 1 (1.0.1) stays on the site as legacy, one pack built and tested together: https://opus-op1.pages.dev/opus1/
Report a bug · Ideas and questions · Releases
Moving in and out
Opus is built so you can try it without risk and leave without losing anything.
- Coming from stock, Opus 1, op1r or Hundekraft: your sounds, presets and tape stay. Opus 1's sounds play with …
Risk and recovery
- Brick risk
- Low
- Reversible
- Yes
- Requires opening the device
- No
From the project's README ("Moving in and out"):
Opus is built so you can try it without risk and leave without losing anything.
- Coming from stock, Opus 1, op1r or Hundekraft: your sounds, presets and tape stay. Opus 1's sounds play with the starter pack in the mods folder. op1r's and Hundekraft's synths, effects and sequencers play with the bridge.
- A plugin removed: a sound that needs it is kept exactly as it is, shows "needs" with the plugin's name, and plays again when the plugin comes back.
- Leaving: the cleaner (Opus's menu, system) makes your data ready for stock or another mod, and keeps a copy of everything it changes. Install Opus again and it all comes back. Going back to Opus 1 needs no cleaner.
- The way back is always there: Opus never changes te-boot, the OP-1's own updater and recovery.
Releases
| Version | Name | Released |
|---|---|---|
| v2.0-beta.2 | Opus 2.0 beta 2 (build 2)Pre-release | 29 October 2026 |
| v2.0-beta.1 | Opus 2.0 beta (build 1)Pre-release | 27 October 2026 |
Credits, license and support
- License
- GPL-3.0