Before Regenerating a Song, Diff the ABC Score

One chord in a fictional game menu song feels too dark. Everything else works: the melody, chorus, tempo, and ending.

The note in the review chat says:

Make that moment brighter.

The team does not need a new song. It needs one clear change.

YuE2 uses ABC notation as a symbolic planning layer. If your YuE2 access point exposes that score, save it before editing. Controls may differ by interface or plan.

Read the Score as Text

ABC notation stores notes, rhythm, tempo, key, and chord symbols in a text file.

X:1
T:Menu Theme
M:4/4
L:1/8
Q:1/4=96
K:C

"C" E2 G2 A2 G2 |
"Am" E2 C2 D4 |
"F" F2 A2 G2 E2 |
"G" D2 G2 G4 |

The header records the setup:

• M: meter
• L: default note length
• Q: tempo
• K: key

Chord symbols sit inside quotation marks. This gives the team something concrete to review instead of relying on “make it happier.”

Change the Smallest Useful Part

The second bar uses A minor:

"Am" E2 C2 D4 |

Change only the chord:

"C" E2 C2 D4 |

Save both files:

menu-theme-v3.abc
menu-theme-v4.abc

Then compare them:

git diff --no-index menu-theme-v3.abc menu-theme-v4.abc

The result should show one intended edit:

- "Am" E2 C2 D4 |
+ "C" E2 C2 D4 |

If the diff also shows a new tempo, missing bar, changed note, or duplicated section, inspect the file before rendering again.

A small change record can make the boundary clear:

example_only: true

expected_change:
  bar: 2
  chord: "Am -> C"

keep:
  key: C
  meter: 4/4
  tempo: 96
  bar_count: 4
  melody: unchanged
  lyrics: unchanged

This confirms the intended score edit. It does not prove that the next audio file will differ in only one place.

Listen to the Full Render

Rendering can also change vocal tone, timing, pronunciation, dynamics, or arrangement.

After creating the new version:

1. Start a few seconds before the edited bar.
2. Check the transition into and out of it.
3. Compare the full song with the previous version.
4. Read the lyrics while listening.
5. Record which version was accepted.

Use careful language in the review note:

version: menu-theme-v4
score_change: "Bar 2 chord changed from Am to C"
result: accepted
notes: "Transition feels brighter; vocal timing remains usable."

“Remains usable” is safer than “unchanged” unless both files have been checked closely.

Reusing a seed may help with comparison, but it does not guarantee identical output around the edited section.

Check Rights Before Publishing

An editable score does not remove permission or copyright questions.

Before release:

• Use only lyrics and reference recordings you are allowed to process.
• Do not copy a protected melody or imitate a recognizable singer.
• Check the current terms for the model, access point, and account plan.
• Keep the original score, edited score, prompt, seed, and audio versions together.
• Ask a musician to review important changes when accuracy matters.

A text diff cannot tell whether a melody is original, whether a reference was authorized, or whether a finished recording is cleared for commercial use.

It can answer a smaller but useful question:

Did we change the line we meant to change?