Maestro

A closer look at what's happening inside a music session.

Music production · Private beta

Maestro session view showing three synthetic tracks registering with a live masking finding — **Session.** Live session state as tracks register, before anything is named or saved.

Maestro mixer showing synthetic track meters and a masking issue between Synthetic Bass and Synthetic Pulse — **Mixer.** 3 of 3 tracks live, with a masking issue between two synthetic tracks called out for review.

Maestro spectrum panel showing a synthetic integrated post-fader signal chart — **Spectrum.** Integrated post-fader spectrum, captured at 124 BPM, four bars back.

Walkthrough. 26.5 seconds of the real local application: session registration, the mixer with its masking finding, then spectrum.

Transcript

A title card establishes the recording scope. The local Maestro UI shows three generic tracks registering, the mixer view with a visible masking finding, and the spectrum view. The "Logic Pro connected" badge stays visible as recorded — it reflects synthetic plugin registration, not a real Logic Pro connection.

Synthetic session data traveling through the real local WebSocket server, session aggregation, and the real React/Tauri interface. No real audio, DAW, or coaching API is used. Synthetic demo data, captured 2026-09-08.

What's working, and what's still in progress

Missing or stale audio evidence stays visible in the UI instead of being papered over with a confident guess.

What's working

Synthetic session registration and track ingest through the real local server
Masking analysis surfaced per track, with the finding kept visible in the UI
Mixer and spectrum views rendered by the real local application

Still in progress

No AU/VST or FFT extraction from real PCM audio
No Logic Pro or other DAW bridge — the bridge process is a safety stub
No coaching API; the assistant panel is not wired to a model