Builtforthebooth.
The native app runs the same Rust engine as the web app, without the browser in the way: a few milliseconds of latency, any audio interface, HID controllers, and timecode vinyl later on. macOS first, Windows after.
Your hand moves. The sound follows.
Output latency, target ranges from our capability matrix. Desktop runs a 64–256 sample buffer.
Targets, not measurements: the engine is in development.
The browser is a great practice room. The booth needs more.
Latency
Native audio APIs and a real-time audio thread with no allocation and no locks. Controller moves feel attached to the sound.
Any interface
Master and cue on one multichannel interface, or on two separate devices with drift compensation.
Controllers
Jog wheels, platter displays and LED feedback over HID, plus MIDI. The same JSON mappings as the web app.
Timecode vinylPlanned
Planned for a later phase. The browser's input latency is too high for it, so it's desktop only.
macOS first. Windows next.
- [01] First
macOS
Apple silicon and Intel. CoreAudio, so most interfaces work without extra drivers.
- [02] Next
Windows
WASAPI and ASIO. Ships once the macOS build has held up at real gigs.
What it will need.
These are targets while we build. Final numbers come out of the four-deck CPU and memory tests.
- OS
- macOSmacOS 13 Ventura or later
- WindowsWindows 10 / 11, 64-bit
- Processor
- macOSApple silicon or Intel Core i5 (2018+)
- Windows4-core x86-64, 2018 or newer
- Memory
- macOS8 GB, 16 GB for four decks
- Windows8 GB, 16 GB for four decks
- Audio
- macOSCoreAudio device; 4-channel for cue
- WindowsWASAPI or ASIO device; 4-channel for cue
- Display
- macOS1280 × 800 or larger
- Windows1366 × 768 or larger
- Disk
- macOS500 MB plus analysis cache
- Windows500 MB plus analysis cache
Get the first build.
We'll send early macOS builds to a small group first, then widen it. Tell us your platform so we know who to write to when.
