Chicken Strip · The foundation

Why REAPER
& CLAP?

Chicken Strip is built around three deliberate choices: REAPER as the first host, CLAP as the plug-in contract and Rust as the processing engine. Each one removes uncertainty from a different part of the real-time audio path.

Three choices. One goal.

Keep the audio path dependable.

We chose the stack from the outside in: a host that supports serious routing, a format designed for modern host and plug-in cooperation, and a language that combines low-level control with stronger safety.

Choice 01 · Host

REAPER

A fast, tightly coded host with deep routing and enough flexibility to test Chicken Strip in demanding, real sessions.

Headroom for the mix
Fast startup, strong multiprocessor support and low-friction editing make REAPER a pragmatic test bed for dense sessions. The plug-ins, buffer size and computer still set the real ceiling.
Sessions that move
Project tabs, full automation and up to 128 routable channels per track cover the complicated routing and comparison work that serious mixes demand.
Deliverables at scale
The Region Render Matrix, render queues and batch conversion turn stems, regions and alternate versions into a repeatable operation.

Why it matters now: one host makes failures reproducible and support deep. That gives the beta a clear target without limiting where Chicken Strip can go next.

REAPER overview

Choice 02 · Format

CLAP

A modern, open contract that lets the host and plug-in cooperate without turning every capability into part of a bloated core.

Host-managed work
CLAP includes an optional thread-pool extension, so plug-ins can ask the host to coordinate parallel work instead of building isolated worker pools.
Stable, then extensible
A CLAP 1.x plug-in can load in a CLAP 1.y host. Optional extensions let each side advertise the capabilities it actually supports.
Open by design
CLAP is released under MIT terms, uses a compact C-compatible ABI and is supported by REAPER across macOS, Windows and Linux.

The honest boundary: a thread-pool contract is not a free speed-up. Chicken Strip still has to keep real-time work bounded and verify every capability it relies on.

CLAP specification

Choice 03 · Engine

Rust

Predictable low-level performance without making memory corruption the normal price of writing real-time DSP.

No garbage collector
Rust has no runtime garbage collector, removing that source of unpredictable pauses from code that must meet an audio-buffer deadline.
Safer shared state
Ownership and thread-safety rules prevent many invalid references, buffer mistakes and data races before the plug-in ever reaches a host.
A narrow unsafe edge
CLAP's C ABI can stay at a small audited boundary while the DSP engine and parameter system remain mostly safe, strongly typed Rust.

The honest boundary: Rust does not make an audio callback safe automatically. We still preallocate and keep locks, file access and unbounded work away from real-time processing.

Why Rust

Compatibility, clearly stated

What the first beta supports.

The technology choices explain the direction. This is the practical support boundary: one host, one format and three desktop operating systems.

DAW

REAPER

REAPER is the initial supported host and the only DAW in the September beta programme.

Format

CLAP

Chicken Strip ships as a CLAP plug-in. VST3, Audio Units and AAX are not part of the initial beta.

Systems

Mac, Windows, Linux

We are recruiting beta testers on macOS with Apple silicon or Intel, Windows and Linux.

Beta testing starts September 2026

Bring your REAPER sessions.

The beta will test real projects, everyday mixing, phase alignment, performance, stability and recall. Final minimum operating-system versions will be confirmed before downloads open.

September beta Join as Beta Tester