Video unavailable. Open the source below.
NewHow it uses Jev
Given a natural-language music prompt, the app makes sequential Jev Choice calls for a composition plan, instruments, harmony, phrase intent, groove parameters, and complete-bar patterns. Code renders the selected patterns into editable notes.
What Jev decides
Illustrative next-event request shape (4 of 100 choices shown)Example answers · not a recorded Jev response · Source ↗
Question 1 · next event
YOUR APP
INSTRUCTION
Choose the concrete next event that best continues this instrumental phrase. Consider the original request, existing notes, position, harmony and phrase intent. Choose only from the supplied complete events.
STATE
Fixture request for a slow blues lead: 4/4 at 84 BPM, electric keys on the lead lane, cursor tick 480, dominant seventh harmony, one prior note, and phrase intent to develop the idea without filling every beat. This shows request fields, not a captured live call or answer. The four displayed candidate labels are representative options from the fixture’s 100-choice set.
JEV · CHOICE
- N_60_120
- N_60_240
- N_61_120
- R_120
App workflow
- Describe the music
Provide a natural-language prompt that seeds the composition plan.
- Choose composition structure
Use sequential Choice decisions for plan attributes, instruments, harmony, phrase intent, and per-lane groove.
- Compose bars
Ask Jev to choose complete-bar patterns from candidates built for the current lane and musical context.
- Render and edit
Convert selected patterns into notes, then play, reshape, persist, or export the composition as MIDI.
Why it is interesting
It builds an editable multitrack symbolic composition from bounded decisions, with rolling context for recent notes and a motif; deterministic edits and MIDI export remain in application code.