MIREX Wiki - Recent changes [en]

2026:Music Performance Difficulty Prediction

Junyan — Thu, 20 Aug 2026 20:05:02 GMT

‎Submission Requirements

2026:Rhythm Game Chart Generation

Ziyunliu — Tue, 11 Aug 2026 15:42:24 GMT

‎Algorithmic Evaluation

2026:Music Audio Generation

Tia — Thu, 06 Aug 2026 08:14:59 GMT

2026:Music Audio Generation

Junyan — Sun, 26 Jul 2026 16:17:56 GMT

‎Contact

2026::Music Audio Generation

Junyan — Sun, 26 Jul 2026 16:17:37 GMT

Junyan deleted page 2026::Music Audio Generation content before blanking was: "'''Task Captain:''' Yingxin Liang, Rythmix AI == Task Description == The MIREX 2026 Cover Song Generation task asks an AI music system to remake a full song according to a style or arrangement prompt. The output can ch..."

2026:Music Audio Generation

Junyan — Sun, 26 Jul 2026 16:17:25 GMT

Created page with "'''Task Captain:''' Yingxin Liang, Rythmix AI == Task Description == The MIREX 2026 Cover Song Generation task asks an AI music system to remake a full song according to a s..."

New page

'''Task Captain:''' Yingxin Liang, Rythmix AI

== Task Description ==

The MIREX 2026 Cover Song Generation task asks an AI music system to remake a full song according to a style or arrangement prompt.

The output can change the style, instruments, arrangement, timbre, or tempo, but it should still be recognizable as a version of the source song. The evaluation checks whether the melody is preserved, the harmony works, the key is coherent, the prompt is followed, and the arrangement sounds complete.

For each test item, participants will receive:

* one full-length source song
* one prompt

Participants must generate one complete cover-song audio file for every test item. The output should cover the full song structure rather than provide only an excerpt, preview, or isolated section. No fixed duration is imposed because tempo and arrangement may change.

=== Examples ===

The following examples use the same full-length source song with three target
style prompts. For each prompt, results from two reference-conditioned systems
are provided.

These examples are for explanation only and will not be used as test items.

'''Full audio player:''' [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/ Listen to all examples]

{| class="wikitable"
! Source audio
! ACE-Step 1.5 SFT XL
! SongEcho
! Exact prompt
|-
| rowspan="3" | [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/source_original.mp3 Source song (MP3)]
| [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/ace_step_prompt_01_classic_pop_ballad.mp3 Audio (MP3)]
| [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/songecho_prompt_01_classic_pop_ballad.mp3 Audio (MP3)]
| '''Prompt 01 — Classic pop ballad'''
<br />
<code>Warm nostalgic classic pop ballad, expressive piano, acoustic guitar, soft live drums, melodic bass and elegant strings, intimate verses and emotional choruses, preserve the original vocal melody, lyrics and song structure.</code>
|-
| [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/ace_step_prompt_02_indie_rock.mp3 Audio (MP3)]
| [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/songecho_prompt_02_indie_rock.mp3 Audio (MP3)]
| '''Prompt 02 — Indie rock'''
<br />
<code>Indie rock emotional female vocals, pop, folk, dreamy, acoustic guitar, electric guitar, strings, drums, bass, percussion</code>
|-
| [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/ace_step_prompt_03_soul_folk_acapella.mp3 Audio (MP3)]
| [https://tiaal.github.io/songecho-cover-metrics/mirex-audio/audio/songecho_prompt_03_soul_folk_acapella.mp3 Audio (MP3)]
| '''Prompt 03 — Soul folk acapella'''
<br />
<code>soul folk acapella, pop, folk, singer-songwriter, mellow</code>
|}

The examples should make the input-output relationship clear: the system receives the source song and prompt, then generates a new full-song arrangement. They are not examples of voice conversion or ordinary human-performed covers.

== Evaluation ==

The official evaluation will be based on expert listening. Three trained evaluators are planned. System identities will be hidden during evaluation.

Each generated cover will be rated on a five-point scale in the following dimensions:

# '''Melody''' - whether the main melody is preserved or plausibly adapted, without salient pitch or contour errors.
# '''Harmony''' - whether the chord progression and chord-melody relationship are musically coherent.
# '''Key Consistency''' - whether the output maintains a coherent tonal center, unless modulation is intentional.
# '''Style Consistency''' - whether the output follows the target style or arrangement prompt.
# '''Arrangement and Production''' - whether the instrumentation, texture, balance, timbre, and production support a complete musical result.

The rating scale is:

* '''5:''' very good, with no salient problem;
* '''4:''' acceptable, with only minor imperfections;
* '''3:''' a noticeable issue, but still musically usable;
* '''2:''' a severe issue affecting musical coherence or usability;
* '''1:''' a substantial or persistent failure.

The official system score will be the average of the five dimension scores across test items and evaluators. Dimension-level results will also be reported.

Evaluators may provide short time-stamped notes for important errors. Inter-rater agreement will be reported with the final results.

== Supporting Objective Features ==

The organizers may report diagnostic features such as large-leap ratio (LLR), pitch range (PR), pitch stability (PS), key confidence (KC), in-key note ratio (IKNR), key-change rate (KCR), loudness deviation, loudness range (LRA), and spectral contrast (SC).

KCR refers to the rate at which the estimated local key changes across adjacent analysis windows. These features are provided only as descriptive diagnostic evidence. They will '''not''' contribute to the official score, system ranking, or tie-breaking. In particular, key-related features do not measure chord-function quality and will not be used as automatic harmony scores. PR and PS are also descriptive pitch summaries rather than validated quality scores.

== Dataset ==

The test set will focus on contemporary tonal popular music, such as pop, pop rock, synth-pop, dance-pop, acoustic pop, folk-pop, and pop ballads.

To keep the evaluation consistent, styles dominated by highly complex, non-functional, modal, or tonally ambiguous harmony will not be included.

All source songs will be provided by the task captain, who will secure the permissions needed to distribute and transform them for this evaluation. Participants may use the source songs only for this task and may not redistribute them.

Official test materials must not be used for training or fine-tuning. Participants may generate multiple candidates and select one for submission, but the selection process must be disclosed.

== Submission ==

Both commercial and open-source systems are allowed, provided that participants have the right to use the system for this evaluation and disclose the system name, version, and any external services used.

Participants will run their systems themselves and submit generated audio and metadata. Model code and checkpoints are not required.

Each submission should include:

* one complete audio output for every official source-prompt pair;
* metadata linking each output to its test item;
* a short system description or MIREX extended abstract; and
* disclosure of training data, pretrained models, candidate selection, and any manual post-processing.

For each test item, participants must report the total number of candidate outputs generated before selecting the submitted version. For example, a submitted output selected from 20 generations should be reported as <code>1 selected from 20</code>.

The final audio format, naming convention, and submission method will follow the instructions provided by the MIREX organizers.

== Baseline ==

At least one reference-conditioned music generation system will be included as a baseline. A text-only music generation system may also be reported as a comparison because it does not use the source-song reference.

Before the test set is released, the organizers will run the reference-conditioned baseline on all test items to confirm that the inputs, prompts, audio requirements, and evaluation workflow function as intended.

== Resources ==

* Diagnostic framework and code: https://github.com/TiaaL/songecho-cover-metrics
* Associated paper: [https://arxiv.org/abs/2607.19688 A Diagnostic Evaluation Framework for AI-Generated Cover Songs Using Music-Theoretic and Acoustic Features]

== Timeline ==

{| class="wikitable"
! Stage
! Date
|-
| Test songs and prompts release
| August 5, 2026
|-
| Submission deadline
| September 15, 2026
|-
| Evaluation questionnaire preparation
| September 16-20, 2026
|-
| Subjective evaluation
| September 21-October 5, 2026
|-
| Result aggregation and analysis
| October 6-12, 2026
|-
| Final results ready
| By October 15, 2026
|}

== Contact ==

If you have any questions or suggestions about the task, please contact:

- '''Yingxin Liang''' — Hangzhou Xiaoying Innovation Technology Co., Ltd. (Rythmix AI)
- Email: yingxinliang.yxl@gmail.com
[mailto:yingxinliang.yxl@gmail.com yingxinliang.yxl@gmail.com]

[[Category:MIREX 2026]]

MIREX HOME

Junyan — Sun, 26 Jul 2026 16:16:47 GMT

‎Task Descriptions

@@ Line 81: / Line 81: @@
 * '''Compute declaration''': GPU memory footprint and average inference time per piece.
-Final submission must be made through the [[2026_Submission_Guidelines|MIREX submission system]]. Submissions exceeding the 24-hour total inference budget on the full test set, or failing on more than 5% of test items, are reported but excluded from the primary ranking.
+Final submission must be made through the [[Submission_Guidelines|MIREX submission system]]. Submissions exceeding the 24-hour total inference budget on the full test set, or failing on more than 5% of test items, are reported but excluded from the primary ranking.
 == Timeline ==

@@ Line 20: / Line 20: @@
 === Algorithmic Evaluation ===
-In this stage, we will manually pick 3 songs for evaluation. First, we will use [https://pypi.org/project/osu-sr-calculator/ osu! star rating calculator] to calculate the star ratings of the generated beatmaps. This allows us to assess whether the model's difficulty conditioning is functioning correctly. Then, we will follow [https://osu.ppy.sh/wiki/en/Client/Beatmap_editor/AiMod AiMod] and [https://github.com/Naxesss/MapsetVerifier MapsetVerifier] to detect unplayable placements of objects algorithmically. Models passing this evaluation phase will move on to human evaluation.
+In this stage, we will manually pick at least 3 songs for evaluation. First, we will use [https://pypi.org/project/osu-sr-calculator/ osu! star rating calculator] to calculate the star ratings of the generated beatmaps. This allows us to assess whether the model's difficulty conditioning is functioning correctly. Then, we will follow [https://osu.ppy.sh/wiki/en/Client/Beatmap_editor/AiMod AiMod] and [https://github.com/Naxesss/MapsetVerifier MapsetVerifier] to detect unplayable placements of objects algorithmically. Models passing this evaluation phase will move on to human evaluation.
 === Expert Evaluation ===

← Older revision		Revision as of 16:17, 26 July 2026
Line 153:		Line 153:
	- Email: yingxinliang.yxl@gmail.com		- Email: yingxinliang.yxl@gmail.com
	[mailto:yingxinliang.yxl@gmail.com yingxinliang.yxl@gmail.com]		[mailto:yingxinliang.yxl@gmail.com yingxinliang.yxl@gmail.com]
−
−	~~[[Category:MIREX 2026]]~~

@@ Line 25: / Line 25: @@
 * [[2026:AI-Generated Music Detection]] <TC: [mailto:ldzhangyx@outlook.com Yixiao Zhang] & [mailto:you.zhang@rochester.edu Neil Zhang]>
 * [[2026:Music Performance Difficulty Prediction]] <TC: [mailto:huan.zhang@qmul.ac.uk Huan Zhang] & [mailto:pedro@songscription.ai Pedro Ramoneda]>
+* [[2026:Music Audio Generation]] <TC: [mailto:yingxinliang.yxl@gmail.com Yingxin Liang]>
 ==Call for Challenges==

@@ Line 4: / Line 4: @@
 The MIREX 2026 Cover Song Generation task asks an AI music system to remake a full song according to a style or arrangement prompt.
-−
 The output can change the style, instruments, arrangement, timbre, or tempo, but it should still be recognizable as a version of the source song. The evaluation checks whether the melody is preserved, the harmony works, the key is coherent, the prompt is followed, and the arrangement sounds complete.
@@ Line 51: / Line 51: @@
 The examples should make the input-output relationship clear: the system receives the source song and prompt, then generates a new full-song arrangement. They are not examples of voice conversion or ordinary human-performed covers.
 == Evaluation ==
@@ Line 84: / Line 112: @@
 == Dataset ==
-The test set will focus on contemporary tonal popular music, such as pop, pop rock, synth-pop, dance-pop, acoustic pop, folk-pop, and pop ballads.
+The official test set consists of the four source-song and prompt pairs listed above. The songs are contemporary tonal popular music and cover four target arrangements: trap, classic rock, acoustic folk, and modern electronic.
-To keep the evaluation consistent, styles dominated by highly complex, non-functional, modal, or tonally ambiguous harmony will not be included.
+All source songs are provided by the task captain, who has secured the permissions needed to distribute and transform them for this evaluation. Participants may use the source songs only for this task and may not redistribute them.
 Official test materials must not be used for training or fine-tuning. Participants may generate multiple candidates and select one for submission, but the selection process must be disclosed.
@@ Line 144: / Line 170: @@
 | By October 15, 2026
 |}
 == Contact ==
@@ Line 150: / Line 175: @@
 If you have any questions or suggestions about the task, please contact:
-- '''Yingxin Liang''' — Hangzhou Xiaoying Innovation Technology Co., Ltd. (Rythmix AI)
+* '''Yingxin Liang''' — Hangzhou Xiaoying Innovation Technology Co., Ltd.
-- Email: yingxinliang.yxl@gmail.com
+* Email: [mailto:yingxinliang.yxl@gmail.com yingxinliang.yxl@gmail.com]