What Makes Generated Music Good?

Chapter 4 asked whether a model could be trained, adapted, reproduced, and debugged correctly. Chapter 5 asks a more difficult question:

Is the resulting system actually good enough for its intended use?

There is no single property called music quality that captures every answer.

A generated clip may have clean audio but weak composition. It may follow the prompt but repeat one phrase. It may sound impressive in isolation but fail when edited into a video. It may produce one excellent sample while failing most other prompts.

Evaluation therefore begins by dividing quality into separate dimensions.

Audio fidelity

Fidelity concerns how the sound is rendered rather than whether the composition is interesting.

Possible defects include:

1. Clipping or harsh saturation
2. Metallic codec artifacts
3. Hiss, hum, or unstable background noise
4. Warbling pitch
5. Smearing of attacks and percussion
6. Unnatural vocal consonants
7. Stereo instability
8. Sudden changes in loudness or ambience
9. Silence or corrupted endings

A technically clean loop can still be harmonically dull, structurally repetitive, or unrelated to the prompt.

Local and global coherence

A five-second segment mainly reveals local relationships. A three-minute track also reveals whether the model can organise time.

Global evaluation can examine:

1. Recognisable section boundaries
2. Motif return and variation
3. Contrast between sections
4. Harmonic direction
5. Changes in density and instrumentation
6. Transition quality
7. Build-up and release
8. Ending quality

Short excerpts should not be used to claim long-form structural quality.

Automated prompt-alignment proxies

Models such as CLAP and MuLan place text and audio in related embedding spaces. Similarity between a prompt embedding and an audio embedding can provide a scalable proxy for semantic alignment.

The score remains dependent on the embedding model. It may respond strongly to broad genre or instrument cues while missing timing, arrangement, negation, subtle production instructions, or long-form structure.

Embedding similarity should therefore complement attribute checks and listening tests.

Diversity is not the same as randomness

A diverse model can produce several appropriate musical solutions. A random model may produce outputs that differ greatly but fail the task.

Diversity can be examined at several levels:

1. Different melodies for the same prompt
2. Different arrangements and instrumentation
3. Different rhythmic interpretations
4. Different outputs for genuinely different prompts
5. Coverage across the intended genre or cultural domain
6. Variation across seeds without loss of quality

Diversity should be measured among outputs that first meet basic validity and adherence requirements.

Originality and non-replication

Originality is not established by comparing two generated samples only with each other.

A system can generate a diverse batch while every output resembles different training examples. Conversely, a style-consistent collection can share common instrumentation and rhythm without copying a particular work.

An originality evaluation may include:

1. Exact token or fingerprint matches
2. Near-neighbour retrieval
3. Melody and interval comparisons
4. Chroma and harmonic similarity
5. Spectrogram or embedding similarity
6. Prompt-targeted extraction tests
7. Human review of flagged pairs

The metric and threshold must match the kind of reproduction being investigated.

Editability and workflow fit

Creators may need more than a finished stereo file.

Useful evaluation questions include:

1. Can the track be cut on beat?
2. Is the tempo stable enough for synchronisation?
3. Does it contain a clean intro and ending?
4. Can sections be extended without obvious seams?
5. Can unwanted elements be removed or regenerated?
6. Are stems or symbolic controls available?
7. Does the output preserve quality after normal editing?
8. Does the file meet the required technical format?

A less impressive track may be more valuable if it is easier to adapt to the project.

Usefulness depends on the application

The same output can be excellent for one task and unsuitable for another.

A loose ambient texture may work well beneath narration but fail as a listening-focused single. A complex cinematic cue may sound impressive but leave no space for dialogue. A melody may inspire a songwriter while being too rough for release.

Evaluation should begin with the intended user, setting, constraints, and decision that the score will support.

Quality dimensions can conflict

Improving one dimension can weaken another.

Examples include:

1. Stronger guidance improves prompt adherence but may reduce variation.
2. Higher sampling temperature increases variety but may reduce stability.
3. Aggressive denoising removes noise but may smear musical detail.
4. Strict style adaptation improves domain fit but narrows broader diversity.
5. Longer duration increases usefulness for songs but exposes more structural failures.
6. Heavy post-processing improves loudness consistency but may damage dynamics.

Report trade-offs rather than hiding them inside one average.

Human listening remains necessary

Listeners can assess qualities that are difficult to capture fully with automated metrics, including musical development, emotional effect, production plausibility, and task usefulness.

Controlled listening should consider:

1. Consistent playback equipment and loudness
2. Randomised sample order
3. Hidden model identities
4. Clear rating instructions
5. Defined listening windows
6. Suitable reference and anchor samples
7. Listener screening or expertise where relevant
8. Repeated items for reliability checks
9. Reporting uncertainty and disagreement

The correct listening design depends on the purpose of the evaluation.

Report more than the mean

An average can hide unstable behaviour.

A quality report should consider:

1. Mean and median ratings
2. Variation and confidence intervals
3. Prompt-level performance
4. Listener disagreement
5. Failure and regeneration rates
6. Performance by genre, language, culture, instrument, and duration where relevant
7. Best, typical, and worst examples
8. Automated-human metric correlation
9. Known blind spots and unmeasured properties

The purpose is to show where the system works, where it fails, and how certain the evaluation is.

Turning dimensions into scalable measurements

This section defined what should be evaluated. The next section, Automated Evaluation, examines how distributional audio metrics, classifiers, embeddings, symbolic statistics, control-alignment scores, and replication searches can measure parts of those dimensions at scale.