Creates and revises the sound. It does not write MIDI, Regions, BPM, Arrangement, or MixState.
Project → Revision
Music you can revise.Not just regenerate.
Lyra turns creative direction into targeted musical changes while preserving the decisions you want to keep.
“Let Melody 2 answer the lead in bar 4. Keep everything else.”
ChangedMelody 2 · Bar 4
Preserved5 Tracks · Timing
SoundRack v0.35 · Patchbay v0.6
A prompt becomes an instrument, not a disposable recording.
SoundRack owns the playable Patch. Patchbay owns how that exact source enters the Project, routes through the graph, and becomes a reproducible mix.
Real Project case
Dark Stage Tines started as “give me a dark normal piano sound.”
Lyra planned three prompt-grounded candidates. The selected six-operator Native Patch stayed editable: Body darkness, Hammer presence, and Room distance remain temporary audition controls over one shared melody; the website demo does not save a Patch.
- SemanticPatch keeps musical intent readable
- EnginePatch keeps executable parameters inspectable
- Temporary audition stays separate from persisted Patch lineage
- The hosted MIDI Lab editor keeps the exact Library asset

The Project points to the chosen immutable Patch and its renderer evidence.
Owns canonical MixState, typed graph execution, meters, and offline mix artifacts.

Same conversation Project · new timbres
Listen to the saved SoundRack sources through the Project mix.
This is the latest offline render with no audition-excluded bindings—not a transient realtime audition bed.
- Project
- rhythmetic boombap · v10 · 91 BPM
- Audio
- 48 kHz · 24-bit · stereo · 12.36 s
- Render
- Offline · validation passed
- SHA-256
- 3e5a0f412b7f…
Native engines, browser audition, hosted editor, and Patchbay graph execution are exercised.
Patch revisions, source hashes, MixState identity, and the copied WAV hash remain traceable.
Candidate planning is optional and failure-visible; deterministic local semantics remain a development fallback.
Recording, Flex and time stretching, AU/VST hosting, and third-party vendor editors are not part of this release. The current Project route supports exact SoundRack sources and validated offline Patchbay rendering.
Arrange uploaded audio without flattening the source.
Lyra DAW v1.0.0-rc.1 keeps imported WAV and MIDI assets addressable while edits become reversible Project revisions.
Verified runtime case
Two Audio Tracks. Three waveform Regions. Source bytes unchanged.
Regions were edited, undone, and restored after reopen while their original assets remained hash-bound. The Patchbay graph and live meters persisted with the Project.
- Move across time and compatible Tracks
- Trim, Slip, Scissors
- Cut, Copy, Paste, Duplicate
- Region Gain, Fades, Normalize
- Undo, Redo, Reopen, Archive, Bounce
This upload-only RC does not yet include recording, Flex or time stretching, or AU/VST hosting.
A first multi-track foundation.
Lyra can now bring Chords, Bass, 808, Drums, and explicit Melody Tracks into one project while keeping each Track available for the next decision.
“Make the bass simpler. Keep everything else.”
ChangedBass
KeptChords, Melody 1, Melody 2, 808, Drums, and Project timing
Explicit Melody Tracks
Add a lead, a counterline, or another independent Melody Track.
Change the movement. Keep the chord.
Lyra can revise one performance dimension while carrying harmony, voicing, and voice leading forward.
“Keep the rhythm, make it tighter, and let the notes come up one by one.”
ChangedPerformance
KeptHarmony, voicing, and voice leading
Agent instruction
Move a Harmony Event to an exact bar and beat.
This changes the composition and creates a focused generated version.
Direct Piano Roll edit
Edit individual MIDI notes without another generation.
Move, resize, change velocity, add, or delete one note inside the event.
Give direction where it matters.
Explicit choices win. Open choices may come from the Project or Lyra, and their source remains visible.
Set the musical contextDirect the foundation when it matters, or leave an explicit choice open.
Tempo
Set it, inherit it, or leave it to Lyra
20-300 BPM, source stays visibleTonal context
Key and Mode follow the same authority rule
Your choice, Project, or LyraHarmonic mood
Direct the emotional shape of a progression
Warm, tense, sparse, suspended, darkHarmonic rhythm
Reshape when each Harmony Event arrives
Exact bars, beats, holds, connectors, blanksShape harmony and movementChange the part of the harmonic result that carries the requested feeling.
Chord color
Change extensions without restarting
7ths, 9ths, 11ths, 13ths, suspensionsVoicing
Open, tighten, widen, or change register
Measured spacing and registerVoice leading
Control how voices travel between chords
Common tones and smooth top linesPerformance
Roll, retrigger, offset, shorten, or hold
Per-voice timing, duration, velocityKeep the result editableThe generated object stays audible, addressable, and available for another decision.
Direct MIDI
Edit the generated result note by note
Pitch, start, length, velocity, add, deleteVersions
Compare, undo, redo, and continue
Every revision remains addressableAudition
Hear the result before export
Preview sounds and local WAV renderOutput
Keep the musical object, not only the audio
MIDI and WAVDifferent prompts. Different harmonic decisions.
Listen to how Key, Mode, BPM, and chord color shape four generated loops.
Sad boom bap
D minor supports the sad direction. 87 BPM leaves space for a laid-back boom-bap pocket.
Dm9 → B♭maj9 → Gm9 → Dm9 → A7(♭9, ♭13)Urban minor
C minor keeps the requested color dark. 78 BPM gives the passing chords room to register.
Cm7 → A♭maj9 → Fm11 → F♯m7♭5 → D♭maj7Warm minor
The request sets C natural minor. Lyra chooses 84 BPM to keep the result warm and unhurried.
Cm9 → Fm9 → G7(♭9) → Am7♭5 → G7(♭9)Jazz connectors
B♭ major gives the extended voicings a warm center. 87 BPM keeps the connecting movement clear.
B♭maj9 → Gm9 → F13 → B♭maj9 → Dm9 → G7(♭9, ♭5) → Cm9Build rhythm from audible layers.
Each style selects a local pattern and matching kit, then keeps the layer structure available for inspection.
Rendered mix from the selected local Pattern set and matching Drum Kit.
What the evidence supports now.
Validated behavior, work in evaluation, and future development are shown separately.
Validated
- SoundRack v0.35 editable SemanticPatch and EnginePatch paths across subtractive, FM/PM, wavetable, and sampler engines
- Patchbay v0.6 canonical MixState, typed routing graph, immutable offline render artifacts, and persistent realtime meters
- Three saved SoundRack instruments bound to one conversation Project and reproduced in a validated offline Patchbay mix
- Upload-only DAW runtime with two Audio Tracks, three waveform Regions, and unchanged source bytes
- Region move, cross-track move, trim, slip, scissors, copy, paste, gain, fades, and normalize
- Project undo, redo, reopen, archive, bounce, and a persistent Patchbay graph with live meters
- Foundational multi-track projects with Chords, Bass, 808, and Drums
- Explicit Melody creation, semantic revision, and note-level editing
- Targeted Track changes that preserve the rest of the Project
- Targeted single-track Chord revisions
- Piano Roll editing, compare, undo, and redo
- Style-scoped Drum assembly with independent stems
In evaluation
- Cross-device Project reopen and longer browser sessions
- Realtime playback performance across larger Projects
- Mix translation across common playback systems
- Musical quality across controlled generations
- Drum intent and pattern-choice quality
In development
- Main Agent product layer across the complete DAW workflow
- Recording, input monitoring, takes, comping, and automation recording
- Flex or time-stretch editing and AU/VST hosting
- Melody integration in default Track sets
- More performance styles and playing techniques