se7en beatlab · studio ecosystem
Four plugins. One invisible engine that processes in a separate process, off your DAW's audio thread. Zero configuration: you load the plugin and it works.
Each Se7en plugin loads light in the session — UI and state. The heavy processing runs in the Se7en Audio Server: a separate high-priority process outside the DAW's audio thread. And if the server isn't there? The plugin processes locally, instantly. The engine is an advantage, never a dependency.
The line
The Se7en plugins talk to each other through four internal groups (A–D) inside the engine — no DAW buses, no routing windows. Star use case: the vocal track sends to group A; Easy Vocals, sitting on the beat, listens to A and makes room for the voice. One block of latency on that path; your DAW's own sidechain always takes priority if you prefer it.
| Format | VST3 · Windows x64 (the only validated platform today) |
|---|---|
| Process | Heavy DSP in a separate high-priority process, off the DAW audio thread |
| Without the server | Instant local fallback — the plugin always sounds |
| Audio privacy | Audio never leaves your machine (local loopback only). Licensing uses a signed, anonymous heartbeat — and works offline with a cached manifest. |
| Sidechain | 4 internal groups (A–D), +1 block latency; DAW sidechain always wins |
| Authenticity | Cryptographic challenge-response between plugin and engine — a gate, not DRM theater |
| Interfaces | Each plugin keeps its original frontend — characters, not a generic re-skin |
From a working studio
No committee designed this: a producer with 25 years of records built it for his own workflow, and opens it to people who produce for real.