Recipes

Make a cover

The make_song prompt does this in one step — most clients show it as a slash command. By hand:

1. song_format and capabilities, so the model knows the shape and the limits.
2. Work out the key, the tempo and the sections — from what the model knows of the record or from a chord chart, never from lyrics. The prompt says so: a lyrics page tells it nothing a chord chart does not, and a NØISE song carries none.
3. check_chords on the chords, against the key.
4. chord_shapes for the grips.
5. build_song.

Ask the model to say how sure it is. The prompt tells it to, because an admitted guess is useful and a confident wrong chord is not.

Change one thing about an existing song

Send the song as base and only the change as changes. That way the model never has to restate the whole chart, which is where things quietly get dropped.

{
  "base": "noise://song?d=…",
  "mode": "direct",
  "changes": [
    { "op": "setSection", "index": 1, "patch": { "fillIn": "crash", "preset": "TIGHT", "energy": "lift" } }
  ]
}

The operations are setSong, setSection, addSection, removeSection, setBar and transpose. A setSection patch may set one field of a lane and leave the rest; setSong takes the style, the kit and the song's own lanes. Anything pointing at a section or bar that does not exist is refused by name rather than guessed at.

Give the song its shape

The band plays a good arrangement by itself; the lanes are for what makes this song recognisable. Read the song like a drummer would and touch as little as possible:

"style": "rock", "kit": "rock.clean", "preset": "LAID BACK",
"sections": [
  { "name": "INTRO", "energy": "hold", "bars": ["G", "B", "C", "Cm"] },
  { "name": "VERSE", "repeats": 2, "bars": ["G", "B", "C", "Cm"] },
  { "name": "CHORUS", "energy": "lift", "fillIn": "crash", "preset": "DRIVING", "colorLayer": true, "bars": ["G", "B", "C", "Cm"] },
  { "name": "VERSE", "fillIn": "splash", "fillOut": "fill", "bars": ["G", "B", "C", "Cm"] },
  { "name": "CHORUS", "energy": "lift", "fillIn": "crash", "preset": "DRIVING", "colorLayer": true, "bars": ["G", "B", "C", "Cm"] },
  { "name": "BRIDGE", "energy": "groove", "preset": "TIGHT", "fillOut": "none", "bars": ["G", "B", "C", "Cm"] },
  { "name": "OUTRO", "energy": "hold", "drumsOff": true, "bars": ["G", "B", "C", "Cm"] }
]

Seven sections, the lanes touched in four places: the choruses arrive on a crash and play DRIVING, the second verse lands soft and fills back in, the bridge tightens and goes straight into the last chorus, the outro is the guitar alone. Everything else follows. The song_format guide has the rules behind this — energy first, let the verse follow, mark the arrivals, the fill is the way out, a preset per kind of section, feel changes are rare, drums off is a real silence.

The rebuilt song keeps a sourceId pointing at the original, so the lineage survives.

Transpose

{ "base": "…", "changes": [{ "op": "transpose", "semitones": -2 }] }

The key moves, absolute chords move with it, and they are re-spelled the way the new key wants them. Key-relative degrees need no change — they follow the key by themselves.

Grips move up or down the neck with their chord, except where that is impossible: a grip with an open string cannot move (there is no fret below the nut) and one that would run off the end of the neck cannot either. Those fall back to NØISE's own grip, and the answer says which ones did.

Ask for grips you can actually play

{ "song": { … }, "fillGrips": true, "gripCategory": "open" }

Every chord without a grip gets one. Where the category has nothing for a chord — Bm has no open grip, it is a barre chord — it falls back to NØISE's default and tells you:

no open grip exists for Bm (easy), so the app's own default was used

Build on a song from the catalogue

Pass a song's public id as base:

{ "base": "d_OxIkOTen", "changes": [{ "op": "setSong", "patch": { "bpm": 96 } }] }

Only published songs can be read this way.

Write it the way a musician would

Since 0.71 three notations from the chart text work inside build_song's bars, and the band plays all three:

• A descending bass line: ["C", "C/B", "Am", "Am/G"] — or, to keep it transposable, {"degree": 1}, {"degree": 1, "bass": "7"}, {"degree": 6}, {"degree": 6, "bass": "5"}. The bass is a degree of the key; a note name ("bass": "E") works too.
• A chorus that kicks in early: "^G" on its first chord — the band strikes it an eighth before the bar and holds it over. "^^G" is a sixteenth early.
• A change on beat 4: ["C(3)", "G(1)"] in one bar.

A song played with a capo takes "capo": 2 on the song and its chords as the hands play them — Wonderwall is Em shapes with a capo on 2, and NØISE's band sounds it in F♯ minor.