REAL PROJECT / SAVED EDIT TRAIL

One conversation.
Music that stays editable.

“rnb trap demo 01” moves from groove direction to exact Drum elements, a Track replacement, chord-performance changes, and a saved four-track mix.

143 BPM8 barsChords · Melody · Drums · Bass

Public-safe crop of the Lyra Studio Track editor at saved version 111 — Actual Lyra StudioSaved checkpoint v111 · four editable Tracks

Three edit modes · one saved Project

See what changed.
Hear the whole loop.

Direct manipulation, a scoped Track replacement, and a prompt regeneration all remain inspectable in the same editable lineage.

TWO LISTENING LAYERSEvery Full Mix and Track A/B plays from Bar 1 through Bar 8.

Hear the edit inside the Project, then isolate the changed Track without losing the shared playhead position.

STUDIO INPUT · NO TEXT PROMPT

“Creator dragged one Note vertically in the Piano Roll.”

CHANGED1 canonical Note · MIDI 94 → 82−12 semitones at Bar 7 · Beat 2.5.

PRESERVED43 other Notes + the target Note’s timingStart, duration, and velocity stayed exact. No AI Provider was invoked.

The edit remains part of the saved Project lineage, even though it was made by hand instead of by prompt.

Piano Roll follows the A/B audio switch.

BAR 7BAR 8

EDIT

FULL 8-BAR LOOP · 143 BPM

0:00

CHANGE

0:13

NOW HEARINGA · saved parent · Full Mix

FIRST CHANGEBar 7 · Beat 2.5

Public-safe crop of Lyra Studio showing editable MIDI Tracks without conversation, model, Run, or history data — ACTUAL PRODUCT SURFACE · PUBLIC-SAFE CROPDirect MIDI · private model and history controls omitted

EVIDENCE BOUNDARY

Each player contains a complete 8-bar Full Mix and the complete changed Track, level-matched for useful A/B listening. The Mix keeps every untargeted Track identical across its pair. Historical per-version bounce bytes were not retained, so these are reconstructed listening previews—not original exported WAVs.

Runtime passed · Artifact hashes verified · Human listening remains a separate judgment

Track scope · v105 → v106

Replace one instrument.
Then simplify only its rhythm.

Context from the other Tracks informs the edit. It does not expand permission to rewrite them.

v105 · user

“On Track 4, replace the 808 with a bass. Make the new Bass rhythmic. Compose that. Preserve Tracks 1–3 and all of their current Regions and Events unchanged.”

v106 · user

“bass a lil too complicated make it slighty easier in rhythm”

Track 1ChordsLOCKED

Track 2MelodyLOCKED

Track 3DrumsLOCKED

Track 4808 → BassREPLACED / RHYTHM REVISED

v105 changedTrack 4 identity + Bass events

v105 preservedTracks 1–3 · Regions · Events

v106 changedBass rhythm only

v106 preservedPitch · duration · velocity · timing · glide

Event dimension · v107 → v109

Same chords.
Three performances.

The selected chord identities remain stable while the way their notes enter changes.

v107

Natural Roll Up

Applied Roll Up to 4 selected chords over 1 beat with natural timing and fixed duration.

v108

Even Roll Up

Applied Roll Up to 4 selected chords over 1 beat with even timing and fixed duration.

v109

Block

Applied Block to 4 selected chords.

Project structure · v74 → v76

The conversation can edit the Project—not just its notes.

v74Delete Drum Region1 MIDI Region removed

v75Delete Drum TrackTrack 3 removed

v76Add Trap DrumsNew Drum Track composed

Image + audio + boundaries

The proof is inspectable.

Public-safe crop of the Lyra Studio Track editor at saved version 71 — Actual product · v71Saved version remains reopenable and editable

Exact v111 render

Listen to the selected final checkpoint.

Project: rnb trap demo 01 · v111
Render: Validation passed · 48 kHz · 24-bit · stereo
SHA-256: 03b027d59364…ac467
Edit audio: v65–v71 are replayed from their saved canonical events through the frozen historical renderer. The original WAV bytes were not retained, so these are labeled reconstructed checkpoints—not invented historical A/B files.
Listening claim: The player enables audition here; automated validation is not presented as a separate human listening sign-off.