2026:Rhythm Game Chart Generation - Revision history

Carolina Carusi: /* Timeline */

2026-09-10T08:00:20Z

‎Timeline

Carolina Carusi at 07:59, 10 September 2026

2026-09-10T07:59:24Z

Ziyunliu: /* Submission Requirements */

2026-09-09T09:26:39Z

‎Submission Requirements

Ziyunliu: /* Timeline */

2026-09-09T09:24:36Z

‎Timeline

Ziyunliu: /* Submission Requirements */

2026-09-09T09:22:38Z

‎Submission Requirements

Ziyunliu: /* Timeline */

2026-09-09T09:19:35Z

‎Timeline

Ziyunliu: /* Timeline */

2026-09-09T09:19:28Z

‎Timeline

Ziyunliu: /* Submission Requirements */

2026-09-09T09:16:45Z

‎Submission Requirements

Ziyunliu: /* Community Evaluation */

2026-09-06T13:39:43Z

‎Community Evaluation

Ziyunliu: /* Submission Requirements */

2026-09-05T14:50:19Z

‎Submission Requirements

@@ Line 117: / Line 117: @@
 * '''July 1, 2026''': Submission system opens
-* '''Sep 11, 2026 (midnight AoE)''': Submission deadline for the generative system (Git repository/Docker image) + report (PDF, 2-4 pages)
+* '''Sep 11, 2026''': Submission deadline for the generative system (Git repository/Docker image) + report (PDF, 2-4 pages)
 * '''Sep 12, 2026''': Test set released
-* '''Sep 14, 2026 (midnight AoE)''': Submission deadline for the generated beatmaps (populated <code>.osz</code> files containing <code>.osu</code> files)
+* '''Sep 14, 2026''': Submission deadline for the generated beatmaps (populated <code>.osz</code> files containing <code>.osu</code> files)
 * '''Oct 15, 2026''': Results published
-All the deadlines above are before midnight, Anywhere on Earth.
+All the deadlines above are before '''midnight, Anywhere on Earth'''.
 = Organizers =

@@ Line 117: / Line 117: @@
 * '''July 1, 2026''': Submission system opens
-* '''Sep 11, 2026''': Submission deadline for the generative system (Git repository/Docker image) + report (PDF, 2-4 pages)
+* '''Sep 11, 2026 (midnight AoE)''': Submission deadline for the generative system (Git repository/Docker image) + report (PDF, 2-4 pages)
 * '''Sep 12, 2026''': Test set released
-* '''Sep 14, 2026''': Submission deadline for the generated beatmaps (populated <code>.osz</code> files containing <code>.osu</code> files)
+* '''Sep 14, 2026 (midnight AoE)''': Submission deadline for the generated beatmaps (populated <code>.osz</code> files containing <code>.osu</code> files)
 * '''Oct 15, 2026''': Results published

@@ Line 106: / Line 106: @@
 Participants are required to submit the source code and model checkpoints of their systems via a link to a '''Git repository (specifying a unique commit hash)''' or a '''Docker image digest''' by '''September 11, 2026'''. Participants are free to convert the raw data into any internal format that best suits their model architecture, provided the complete pipeline is included in the submission. Submissions must be accompanied by a '''technical report in PDF format (2-4 pages)''' detailing the '''model architecture, dataset, and training process'''.
-Following the system submission deadline, the '''hidden test set''' will be released. This set will include at least 3 '''template <code>.osz</code> files''', each containing an '''audio file''' and '''5 template <code>.osu</code> files''' with ground truth uninherited timing points. Participants will have a '''>= 48-hour window''' to execute their ''frozen'' systems on their own hardware of choice to generate the required outputs. For each song in the test set, the system should generate '''hit objects (mandatory)''' and '''inherited timing points (optional)''' for '''all 5 difficulty levels''' (Kantan, Futsuu, Muzukashii, Oni, Inner Oni). By the end of the >= 48-hour window, participants should submit their populated <code>.osz</code> files containing the completed <code>.osu</code> files. Please include your '''contact information''' in your submission so that we can send the templates to you directly.
+Following the system submission deadline, the '''hidden test set''' will be released. This set will include at least 3 '''template <code>.osz</code> files''', each containing an '''audio file''' and '''5 template <code>.osu</code> files''' with ground truth uninherited timing points. Participants will have a '''>= 48-hour window''' to execute their ''frozen'' systems on their own hardware of choice to generate the required outputs. For each song in the test set, the system should generate '''hit objects (mandatory)''' and '''inherited timing points (optional)''' for '''all 5 difficulty levels''' (Kantan, Futsuu, Muzukashii, Oni, Inner Oni). By the end of the >= 48-hour window, participants should submit their populated <code>.osz</code> files containing the completed <code>.osu</code> files. Please include your '''contact information''' in your technical report so that we can send the templates to you directly.
 Note that some attributes (such as x and y axes) in hit objects are not relevant to osu!taiko gameplay, and therefore should not be predicted (see [https://osu.ppy.sh/wiki/en/Client/File_formats/osu_%28file_format%29 this page] for details). In the submission, participants can set these attributes to default values (e.g. 256 for x and 192 for y).

@@ Line 119: / Line 119: @@
 * '''Sep 11, 2026''': Submission deadline for the generative system (Git repository/Docker image) + report (PDF, 2-4 pages)
 * '''Sep 12, 2026''': Test set released
-* '''Sep 14, 2026''': Submission deadline for the generated beatmaps (packed archive containing <code>.osu</code> files)
+* '''Sep 14, 2026''': Submission deadline for the generated beatmaps (populated <code>.osz</code> files containing <code>.osu</code> files)
 * '''Oct 15, 2026''': Results published

@@ Line 104: / Line 104: @@
 = Submission Requirements =
-Participants are required to submit the source code and model checkpoints of their systems via a link to a '''Git repository (specifying a unique commit hash)''' or a '''Docker image digest''' by '''September 11, 2026'''. Participants are free to convert the raw data into any internal format that best suits their model architecture, provided the complete pipeline is included in the submission. Submissions must be accompanied by a '''technical report in PDF format (2-4 pages)''' detailing the '''model architecture, dataset, and training process'''. Please include your '''contact information''' in your submission.
+Participants are required to submit the source code and model checkpoints of their systems via a link to a '''Git repository (specifying a unique commit hash)''' or a '''Docker image digest''' by '''September 11, 2026'''. Participants are free to convert the raw data into any internal format that best suits their model architecture, provided the complete pipeline is included in the submission. Submissions must be accompanied by a '''technical report in PDF format (2-4 pages)''' detailing the '''model architecture, dataset, and training process'''.
-Following the system submission deadline, the '''hidden test set''' will be released. This set will include at least 3 '''template <code>.osz</code> files''', each containing an '''audio file''' and '''5 template <code>.osu</code> files''' with ground truth uninherited timing points. Participants will have a '''>= 48-hour window''' to execute their ''frozen'' systems on their own hardware of choice to generate the required outputs. For each song in the test set, the system should generate '''hit objects (mandatory)''' and '''inherited timing points (optional)''' for '''all 5 difficulty levels''' (Kantan, Futsuu, Muzukashii, Oni, Inner Oni). By the end of the >= 48-hour window, participants should submit their populated <code>.osz</code> files containing the completed <code>.osu</code> files.
+Following the system submission deadline, the '''hidden test set''' will be released. This set will include at least 3 '''template <code>.osz</code> files''', each containing an '''audio file''' and '''5 template <code>.osu</code> files''' with ground truth uninherited timing points. Participants will have a '''>= 48-hour window''' to execute their ''frozen'' systems on their own hardware of choice to generate the required outputs. For each song in the test set, the system should generate '''hit objects (mandatory)''' and '''inherited timing points (optional)''' for '''all 5 difficulty levels''' (Kantan, Futsuu, Muzukashii, Oni, Inner Oni). By the end of the >= 48-hour window, participants should submit their populated <code>.osz</code> files containing the completed <code>.osu</code> files. Please include your '''contact information''' in your submission so that we can send the templates to you directly.
 Note that some attributes (such as x and y axes) in hit objects are not relevant to osu!taiko gameplay, and therefore should not be predicted (see [https://osu.ppy.sh/wiki/en/Client/File_formats/osu_%28file_format%29 this page] for details). In the submission, participants can set these attributes to default values (e.g. 256 for x and 192 for y).

@@ Line 28: / Line 28: @@
 === Community Evaluation ===
-In this stage, a single showcase song will be selected for community evaluation. Participating players will choose a difficulty level aligned with their skill level and playtest charts generated by each model alongside a human-authored chart. Players will vote on musical representation, creativity, gameplay, and they will be asked to identify which chart is authored by human.
+In this stage, a single showcase song will be selected for community evaluation. Participating players will choose a difficulty level aligned with their skill level and playtest charts generated by each model alongside a human-authored chart. Players will vote on musical representation, creativity, gameplay, and human-likeness of the generated charts.
 = Resources =