One idea, several moods

Continue Morning song. Keep the original recipe and change one dimension. Hear the differences, then save the Candidate you want to keep as a named Version.

Continue from your first piece

Keep the first chapter's Project id, original lyrics, style, seed 2026192201, and saved Morning Version. Listen again and write one question: do I want more space in the arrangement, a lyric line that sings better, or another random starting point?

These changes generate new short fragments; they do not edit the earlier audio. In the same Project's “Versions”, select two saved works and compare them in the continuous A/B player. The same seed does not guarantee identical bytes across models, environments, or versions.

1. Choose a question worth listening for

Select a recipe to see exactly what changes. The first is a verified example. The others are inspiration recipes that have not been tuned or auditioned. They illustrate directions to try, not promised results. This only changes the tutorial's example inputs; it generates no music.

Hear the original recipeA lighter piano arrangementTry another phraseAnother random starting point

Verified baseline

Keep all first-chapter inputs. Listen to the warm voice with guitar and piano, then note one thing to change next.

View and copy inputs · JSON

{
  "style": "English, gentle folk pop, warm clear voice, acoustic guitar and piano, light bass and drums, 96 BPM",
  "lyrics": "[Verse]\nMorning gathers on the window\nQuiet streets begin to glow\nI will carry one small promise\nEvery step can help it grow\n\n[Chorus]\nWalk with me into the daylight\nLet the little river flow\nWe can make a brighter moment\nWith the kindness that we show",
  "seed": 2026192201,
  "max_seconds": 35
}

Complete example: services/api/examples/creator/morning-song.json ↗

Copy inputs

2. Listen with a goal

Experiment	Keep first	Listen for
Change style only	Original lyrics, seed, clip-length setting	Instrument density, voice, and mood; style words are not exact arrangement commands.
Change one lyric line	Original style, seed, other lyrics	Natural articulation and phrasing, and a memorable line; it may not appear within this clip.
Change seed only	Original style, complete lyrics, clip-length setting	A melody or structure that suits you better in another result; one difference is not a stable rule.

Hear the whole piece first, then focus on your question. Record a short preference such as “B has clearer vocals; A has a more natural ending.” Keep the original result instead of comparing from memory.

Compare two works in one player

1. In “Versions”, inspect the original Morning Version and another Version you explicitly saved. Select them as “Version A” and “Version B”, then choose “Use this pair”. Unsaved Candidates are not comparison choices; with one Version, choose “Listen to A only”.
2. Wait for the audio, then press “Play”. Use “Switch to A” and “Switch to B” to hear the same instant. Switching while paused at12 seconds keeps12 seconds; switching during playback continues when the target is ready. This preserves absolute seconds, without aligning beats, lyrics or phrases.
3. Expand “Common listening region” and try a start of2 seconds and end of4 seconds. Choose “Set region”, then “Play region”. It plays once and pauses at4 seconds. Drag or resize the waveform region within the range both clips contain. A manual seek cancels this bounded playback.
4. Open “Lyrics and inputs” to inspect the current creative draft. For a chosen A/B work’s saved lyrics and inputs, open that Version’s “Submitted inputs”; open its corresponding Score from the Version. Music continues across navigation. Explicitly auditioning a Candidate, Reference Audio or draft MIDI changes the source. Choose “Return to comparison” in the player to resume A/B, starting paused at0.

When a target is shorter than the current position, it stops paused at its actual end. Returning to the longer work stays paused. After a natural end, explicitly press “Play” to hear it from the start. A new pair starts paused at0; if the old region does not fit its common range, set a new one when prompted. The region is not silently shortened.

Reload restores only Version choices and the A/B side that remain valid in this Project, paused at0, without position or region. When choice storage is unavailable, comparison still works for this session; reload recovery is not guaranteed. Keep the works when audio or Version reads fail: choose “Reread audio” or “Reread versions”; restore a missing original Audio/ABC file first. Rereading audio starts paused at0, avoiding another seek to a position that could not decode. One available Version can still play alone. Recovery does not generate or save new work.

3. Try the next Candidate in the same Project

To continue from work you kept, open “Versions” and inspect the saved parent relationships. Choose an earlier work, such as the original Morning version. Inspect its inputs, origin and “Saved outputs”, then choose “Continue from this version”. This opens that Version's Score and preserves your current drafts. Choose “Use this version’s inputs” separately when you want its style, lyrics and seed.

1. Inspect or edit the ABC, then explicitly choose “Select saved Score” or “Save and select this Score”.
2. Keep lyrics and seed, change only the style to a lighter piano arrangement, then generate from the selected Score. Check that the submitted parent is the original Morning version you chose.
3. Listen to the new Candidate. If you like it, name it “Morning · light piano” and explicitly save a Version. Unsaved Candidates remain outside the relationship view.
4. Return to the original and save another direction. Both new Versions link to the original; the newest branch does not automatically become the next starting point. Reloading reads the same relationships and saved snapshots.

A list can have several independent starting points; a Version without a parent is valid. If reading fails, choose “Reread versions”; an error is not empty history. Restore a missing original Audio or ABC file before rereading. Existing history remains. If the starting point cannot be confirmed, your draft remains: return to the actual Version or reread the starting point, then inspect and explicitly select again.

In the formal Web's music generation page, choose “Explore with these inputs” on an earlier Candidate, change one input, generate, listen and record your judgment. Earlier Candidates and Versions remain. To keep a deliberately selected melody while changing style, use regeneration on the Score page; it retains selected ABC and source parent. Use the supplement below when you need scripts and downloaded files, with a new output directory for each attempt.

Current entrypoint: reuse the same Project

This command demonstrates “change seed only.” Replace the Project id and keep the controlled first-chapter lyrics. It creates a new Job and downloads a new Candidate, without saving a Version. Replace --style for a style experiment. For lyrics, copy the original to your own new UTF-8 file, change one line, and pass the new path with --lyrics-file. Keep the original lyrics and other inputs.

uv run --project services/api --no-sync python services/api/examples/generate_save.py generate --project-id <PROJECT_ID> --style "English, gentle folk pop, warm clear voice, acoustic guitar and piano, light bass and drums, 96 BPM" --lyrics-file services/api/examples/creator/morning-song-lyrics.txt --seed 2026192202 --output-dir data/morning-candidate-02

Change style only: a lighter piano arrangement. Keep the original lyrics and seed, and use a new download directory. This inspiration recipe has not been auditioned.

uv run --project services/api --no-sync python services/api/examples/generate_save.py generate --project-id <PROJECT_ID> --style "English, gentle folk pop, warm clear voice, soft piano, restrained drums, 96 BPM" --lyrics-file services/api/examples/creator/morning-song-lyrics.txt --seed 2026192201 --output-dir data/morning-piano-01

Change one lyric line. The controlled UTF-8 file below replaces only the original first line. This is also an unauditioned experiment. Keep style and seed unchanged.

[Verse]
Morning sunlight finds the window
Quiet streets begin to glow
I will carry one small promise
Every step can help it grow

[Chorus]
Walk with me into the daylight
Let the little river flow
We can make a brighter moment
With the kindness that we show

Complete example: services/api/examples/creator/morning-sunlight-lyrics.txt ↗

uv run --project services/api --no-sync python services/api/examples/generate_save.py generate --project-id <PROJECT_ID> --style "English, gentle folk pop, warm clear voice, acoustic guitar and piano, light bass and drums, 96 BPM" --lyrics-file services/api/examples/creator/morning-sunlight-lyrics.txt --seed 2026192201 --output-dir data/morning-sunlight-01

Choose one question and submit one of these commands each time. Use a new directory name if the output directory exists. To try your own lyrics, keep the original example, save your changed full text in your own UTF-8 file, and select it with --lyrics-file.

4. Choose the one you want to keep

Listen to the new Candidate and inspect its ABC, then save a Version in the same Project if you like it. Name the change, such as “Morning · seed 02.” After saving, select it and the original Morning Version as A/B, listen again and record your preference. You can use a Version from the first chapter as parent to record the starting point. That relationship is creative provenance, not a local audio edit.

You can leave every Candidate unsaved if none is right yet. Finished generation is not a finished creative choice.

Current save entrypoint: keep the new Candidate as a Version

Replace the actual Project, Candidate, and saved parent Version ids. Omit --parent-version-id when there is no parent. All ids must belong to this Project.

uv run --project services/api --no-sync python services/api/examples/generate_save.py save --project-id <PROJECT_ID> --candidate-id <NEW_CANDIDATE_ID> --name "Morning - seed 02" --parent-version-id <FIRST_VERSION_ID>

If saving conflicts, read the existing Version first

When the save command returns 409, the CLI prints the HTTP status and URL, without the existing Version id from the response body. In local Swagger, read this Project's version list with GET /projects/{project_id}/versions. Look for a saved record with the submitted candidate_id. If found, check its actual name and parent_version_id, record the returned Version id, and read GET /projects/{project_id}/versions/{version_id} to confirm what you kept. Generate a new Candidate for a new creative intent. If no record matches, retain the Candidate id and error, then use the saving and Asset recovery guide to check other save failures.

If waiting disconnects, query the original Job as in the first chapter to avoid repeated inference. Change one dimension in the next round and keep a clear starting point.

What could you ask next?

• Make lyrics on the same theme shorter: change one line and listen for more direct expression.
• Use fewer instrument instructions: remove one arrangement request and listen for focus.
• Notice a rhythm in Reference Audio, then describe a new style goal in words.

These are experiments, not tuned finished recipes. Keep inputs, Jobs, listening notes, and selected Versions so the next session has a clear starting point.

Source version: 1ce3268Page source: docs/learn/variations.en.md