The host that runs the plugins serves the console and Zynthian alike. Each card says where a feature stands on the console, on Zynthian and on any other host. "To confirm" means this state has not been checked on the console yet.
A crash stays in one plugin
If a plugin crashes, only that plugin stops. The rest of your set keeps playing.
Every plugin runs in a worker process of its own, or shares one with the plugins next to it in a chain. A worker that dies is started again by the daemon with its settings and the links it had made, so a bad plugin costs you a moment, not the show.
- After a killed worker, the daemon put it back with its settings and its links in about 350 ms, on the Pi 5 under Zynthian.Measured with: plugin-hostd 0.19.0, omx-clap-host 0.29.0
- ConsoleReleasedplugin-hostd 0.16.0
- ZynthianReleasedzynthian-ui omx-track 2026110701
- Any hostReleasedplugin-hostd 0.20.0
Detail
A chain in one worker
Plugins in series share one worker and one JACK client. You get most of the memory back.
The daemon plans what can run together: a run of plugins in series is one worker, and a parallel slot, the mixer strip or a jalv plugin ends the run. A processor that runs alone has a Grouping entry in its options that says why. Grouping is off until you turn it on.
- Memory for 16 plugins in a chain: 55 MB under plugin-hostd, against 99 MB for mod-host and 690 MB for jalv, which runs one process per plugin.Measured with: plugin-hostd 0.18.0, omx-clap-host 0.29.0, mod-host 0.10.9, jalv 1.6.9 · 48 kHz
- Time to add 16 plugins one by one: 80 ms into a plugin-hostd chain, against 364 ms for mod-host and 13.8 s for jalv.Measured with: plugin-hostd 0.18.0, omx-clap-host 0.29.0, mod-host 0.10.9, jalv 1.6.9 · 48 kHz
- ConsoleReleasedplugin-hostd 0.16.0
- ZynthianReleasedzynthian-ui omx-track 2026110701
- Any hostReleasedplugin-hostd 0.20.0
Detail
A MOD GUI for every plugin
Plugins that ship no interface get one, drawn from the same layout as the controller pages.
omx-panel builds a MOD GUI for each plugin that has none, so MOD-UI pedalboards show a real panel. The same layout feeds the pages on the Zynthian screen, so the two always agree.
- ConsoleReleasedomx-panel 0.9.1
- ZynthianReleasedzynthian-sys omx-track 2026110701
- Any hostReleasedomx-panel 0.12.0
Detail
Ducker, doubler and tone
Music under a voice, a double-tracked sound without a second take, and a tone tilt with a DJ filter.
omx-ducker pulls the programme down while a key is heard, by a set depth with attack, hold and release. omx-doubler adds up to four slightly delayed, detuned and drifting copies spread across the stereo field. omx-tone tilts the whole tone darker or brighter about a pivot and sweeps a resonant DJ filter with one knob.
- ConsoleComing
- ZynthianReleasedomx-plugins 0.19.1
- Any hostReleasedomx-plugins 0.19.1
Detail
Effects that ship with it
EQ, compressor, gate, reverb, delay, drive and a one-load channel strip, as CLAP and LV2.
omx-plugins carries the effects used in the console, each as a CLAP and an LV2 plugin. Add them one by one and choose the order, or load omx strip: trim, filters, a gate, four EQ bands and a compressor in one load and one worker, its five stages in any order.
- omx strip costs about 5.9 µs per block; omx eq8 and omx comp together about 11.4 µs, with eight EQ bands against four.Measured with: omx-plugins 0.18.0, Raspberry Pi 5 · 48 kHz, 512 frames
- ConsoleReleasedomx-plugins 0.18.0
- ZynthianReleasedomx-plugins 0.19.1
- Any hostReleasedomx-plugins 0.19.1
Detail
What loads is what was measured
A plugin is pinned the first time it is used. If its files change, it is measured again.
The pin ties a plugin name to the exact file that was qualified. The host loads only pinned plugins, so a plugin that was swapped or updated behind its back does not run on trust.
- ConsoleReleasedplugin-hostd 0.16.0
- ZynthianReleasedzynthian-sys omx-track 2026110701
- Any hostReleasedplugin-hostd 0.20.0
Detail
Every plugin measured on your device
You see how heavy a plugin is and whether it is safe before you add it.
plugin-qualify runs each plugin on the device and writes what it found: latency, real-time safety and cost. The menus are built from those records. The records package ships ready-made results for the Pi 5, and a sync in the background checks only the plugins whose files changed.
- Of 1602 plugins tried on the device, 1079 run in a shared worker and 306 in a worker of their own.Measured with: plugin-qualify 0.18.5, Raspberry Pi 5
- ConsoleReleasedplugin-qualify 0.18.5
- ZynthianReleasedzynthian-ui omx-track 2026110701, zynthian-sys omx-track 2026110701
- Any hostReleasedplugin-qualify 0.20.0, plugin-qualification-records 2026110901
Detail
A plugin that breaks the rules is isolated
A plugin that corrupts the host's own state is moved to a worker of its own.
Every plugin call saves and checks the registers a function must keep. A plugin that changes one is caught and runs alone from then on, so it cannot take the rest of a chain with it.
- ConsoleReleasedplugin-hostd 0.16.0
- ZynthianReleasedplugin-hostd 0.20.0
- Any hostReleasedplugin-hostd 0.20.0
Detail
Big synths use all four cores
A synth that splits its voices into tasks plays more notes, because every core helps.
The host starts helper threads, pinned to the cores the plugin may use. A plugin gets them only after qualification found it safe for real time with the helpers running and faster with them. Any other plugin runs as before. You do not set anything on Zynthian.
- The mean cost of one block with 48 voices fell from 3335.5 to 857.9 µs, 3.9 times faster, with no block over its deadline. This is a test plugin; Surge XT has no figure of this kind because it does not split its voices.Measured with: omx-clap-host 0.29.0, test plugin of 16 tasks per block, Raspberry Pi 5 · 48 kHz, 256 frames
- ConsoleReleasedomx-clap-host 0.27.0
- ZynthianReleasedomx-clap-host 0.31.0
- Any hostReleasedomx-clap-host 0.31.0, plugin-qualify 0.20.0
Detail