Blog

Guide

ElevenLabs Music v2 Pre-Launch Acceptance Guide: Build an Audition Sheet for Music Candidates

Nov 18, 2026
Against a deep charcoal background, a horizontal amber band of light sweeps diagonally past, with a few dark short lines dotted below, serving as the article cover image.
On this page

Why prepare an audition sheet before the model launches

The most common way music review goes wrong is not that the model is bad, but that there is no shared standard. After launch, everyone puts on their own headphones and plays a different clip—some listen to the first eight seconds, others to the chorus loop—and the conclusion ends up as "feels okay" or "a bit weird"—conclusions that can neither be reproduced nor traced back.

Before the model is officially available is precisely the best window to prepare acceptance assets: there is no pressure from final cuts, nor the forced push of "ship first, talk later," so the team can calmly write down "what counts as usable" into a sheet that can be checked, scored, and compared. Once the model can run, you just execute against the sheet, and the review meeting turns from a debate into a verification meeting.

We must first clarify the boundaries: ElevenLabs Music v2 is currently in a **coming soon** state. This article contains no test results and no usage examples. What is written here is a set of methodological assets—what the audition sheet looks like, how to record defects, and how to compare versions. Once the model launches, simply fill the candidate audio into the sheet.

Preparing in advance has another hidden benefit: when acceptance dimensions are written down, teams discover that many disagreements actually come from misaligned scenarios, not from the audio quality itself. The earlier this discovery happens, the better.

The process along the light band: first prepare the audition sheet, leave the model slot empty for now, then move toward the first review.

First define the music's usage scenarios and acceptance dimensions

The granularity of the acceptance object should match the final cut, not "whether a piece of music sounds good on its own." It is recommended to sample in layers according to real usage in the final cut:

  • Opening/intro: The first few seconds must establish themselves; focus on whether the start is clear and whether there is ineffective buildup.
  • Background bed: Long-duration low-attention listening; focus on whether it is pleasant on repeat and whether it competes with vocals or narration.
  • Transition/section change: Check whether the emotional connection is natural and whether the transition can be completed within the specified duration.
  • Loop segment: Check whether the start and end can be seamlessly spliced, and whether obvious mechanical repetition appears after several loops.

Then map each scenario to observable dimensions, avoiding words like "pleasant" or "high-end":

  • Structural completeness: Is there a recognizable beginning, development, turn, and conclusion, or is it evenly laid out throughout?
  • Loop seam: When the tail frame connects back to the head frame, are there pops, breaks, or rhythmic misalignment?
  • Dynamic range: Does the contrast between strong and weak exist within a reasonable range, and is the sense of compression too heavy?
  • Style consistency: Does the actual listening experience match the style and instrumentation described in the prompt?
  • Usable density: What proportion of the total duration consists of valid segments that can be directly used in the final cut?

Dimensions should be kept to five to seven; too many and reviewers cannot finish filling them out, too few and you cannot tell where the problem lies. Each dimension needs a judgment statement—what counts as pass, what counts as a defect—written down in advance.

Structure of the audition sheet: fields and scoring criteria

The core of the audition sheet is not "looking good," but enabling different reviewers to fill in comparable results for the same audio segment. Fields can be divided into four groups:

Positioning fields

Scenario (intro/bed/transition/loop), candidate ID, duration, generation date. These columns answer "for which position was this audio prepared."

Input fields

Prompt text verbatim (record word for word, do not rewrite), key parameter definitions (duration, style description, etc.). The prompt must be saved as-is; any abbreviation will cause subsequent reproduction to fail.

Scoring fields

Each acceptance dimension uses a unified three-level scale, such as "pass / marginal / fail," and allows one remark. Three levels are more stable than five levels or a ten-point scale, and judgments between reviewers are easier to align; the finer the score, the greater the subjective noise.

Conclusion fields

Defect tag (choose from a preset vocabulary, no free-form wording allowed) + one-sentence explanation + recommended action for that candidate (keep / redo / discard).

Two practical details:

  1. One row per candidate; do not cram multiple candidates into one row, otherwise version comparison becomes impossible.
  2. Reserve a "re-review" column in the sheet to record whether the judgment changed in the second round—a flipped judgment is itself valuable data, indicating that a dimension is not clearly defined.

The scoring criteria must be clearly stated in the header: what equipment to listen on, how many times to listen, and whether pausing is allowed. These seemingly trivial conventions determine whether the data is usable.

Structure of the audition sheet: scenario, candidate, scoring dimensions, and conclusion each form a column group; the area swept by the light band indicates where reviewers must align on the same standard.

Defect logging: make problems reproducible and classifiable

A defect record that cannot be reproduced is as good as not recorded. The minimum information set should contain four items:

  • Prompt text verbatim: complete, unpolished, including punctuation.
  • Parameter definitions: the duration and style settings for this generation, described clearly in words, not vague "default."
  • Review conditions: headphones or speakers, volume range, whether looped playback was used.
  • Phenomenon description: at what time point, what was heard, and what was expected.

The phenomenon description should avoid stacking adjectives. "Around 12 seconds the low frequencies suddenly become thin, inconsistent with the first half" is usable; "the audio quality is a bit poor" is not.

Defect classification is recommended to be split by attributable cause rather than by listening impression:

Structural

Missing sections, abrupt transitions, truncated endings, misaligned loop points. These problems are usually related to duration and structural requirements.

Consistency

Style drift, sudden instrumentation changes, excessive variation across multiple generations from the same prompt.

Mixing

Volume imbalance, crushed dynamics, vocals or narration being masked.

Usability

The overall usable ratio is too low; many segments cannot go directly into the final cut.

Preset five to eight tags per category; reviewers choose from the vocabulary and do not coin terms on the spot. Once the vocabulary is stable, the defect library can be statistically analyzed and answer "what proportion does this type of problem account for."

Version comparison: change only one variable

The most common mistake in version comparison is mixing model differences with prompt differences. For example, the first round uses a short prompt, the second round changes to a long prompt and also changes the duration, and the conclusion says "the new version is better"—methodologically, this conclusion does not hold.

Three disciplines for controlling variables:

Same prompt, same duration

When comparing two rounds of generation results, the prompt text and duration must be exactly the same. If the prompt must be changed, list that change as a separate experiment and do not mix it with the version comparison in the same sheet.

Blind listening

Reviewers should not know in advance which version each item is, otherwise expectations will contaminate judgment. Candidate IDs are randomly assigned, and version information is known only to the organizer.

Randomized order

The listening order of the same batch of candidates must be shuffled to avoid position effects such as "the one heard first is better." Reshuffle before each review round.

The output of comparison is not "A is better than B," but differences by dimension: whether structural defects decreased, whether loop seams improved, whether usable density changed. Only when it lands on dimensions can the difference guide the next step—whether to adjust the prompting strategy or wait for model iteration.

If the two rounds trade wins across multiple dimensions, do not force a total score ranking. Recording "which is more suitable in which scenario" is more useful than a single total score.

Review process and conclusion exits

Reviews need people, rounds, and exits, otherwise they drag on indefinitely.

Who reviews

At least two roles: users (people who actually edit and score) and gatekeepers (people responsible for final cut quality). Users judge usable density, gatekeepers judge the lower bound. It is not recommended to involve everyone; the more people, the more scattered the standards.

How many rounds

Two rounds are enough. The first round is filled out independently without discussion; the second round re-reviews only the candidates where judgments diverged in the first round—the divergence itself points to dimension definitions that need clarification. More than two rounds usually means the dimensions are not clearly defined; going back to revise the sheet is more effective than continuing meetings.

Conclusion exits

Every candidate and every scenario must land on one of three conclusion types:

  • Usable: can go directly into the final cut; defect tags are empty or only record-level remarks remain.
  • Conditionally usable: usable in specific scenarios, or requires minor manual trimming or splicing; the conditions must be stated.
  • Unusable: major dimensions fail, or defects cannot be fixed in post-production.

"Feels okay" does not belong to any category and must be placed. The follow-up actions corresponding to the three conclusion types must also be agreed in advance: usable enters the asset library, conditionally usable comes with handling notes, unusable enters the defect library as a regression sample.

Finally, give the overall acceptance a written closure: which scenarios have met the standard, which scenarios still have systemic defects, and what the next round of acceptance should focus on. This paragraph is more important than any score.

How to reuse this acceptance asset after launch

Once the model is officially available, this asset is not archived but moved into normal operation:

  • The audition sheet becomes a fixed form whenever a new prompting strategy or new version is integrated; the fields stay the same, only the candidates change.
  • The defect library becomes a regression sample set; each iteration first runs this batch of samples to see whether old problems recur.
  • Dimension definitions are revised in small steps as the business changes, but revisions must carry version numbers, otherwise historical data is not comparable.

A pragmatic approach is to keep the audition sheet, defect vocabulary, and re-review records in one place; when new members onboard, they read the header first and then listen to samples—this is much faster than oral transmission of review standards.

For ElevenLabs Music v2's specific launch status and integration information, refer to the model page; once the model is available, fill in the first batch of candidate audio according to the sheet above, and the acceptance process is up and running.

Related articles

View all articles →

Start building with persistent AI artifacts

Get your API key and call image, video and audio models through one task-based API.

Read the API docs