Difference between revisions of "2006:Score Following Proposal"
Arshiacont (talk | contribs) (→Evaluation procedures) |
Arshiacont (talk | contribs) |
||
| Line 16: | Line 16: | ||
== Evaluation procedures == | == Evaluation procedures == | ||
| + | |||
| + | Evaluation procedure consists of running score followers on a database of aligned audio to score where the database contains score, and performance audio (for system call) and a reference alignment (for evaluations) -- See below for details. | ||
| + | |||
| + | === Suggested calling formats for submitted algorithms === | ||
| + | During evaluation, each system will be called in '''command line''' with the following format: | ||
| + | |||
| + | <system-execution-file> <input-folder> <output-filename> | ||
| + | |||
| + | The input folder contains the score and audio performance of the score. Your submitted binaries should be able to BROWSE this folder and use the appropriate score and audio file and undertake the score following task, and write the results to the output file as given. | ||
| + | |||
| + | It is important to be able to create the output ascii file in a "different" path than the default. | ||
| + | |||
| + | In order to consider the issue of training, an alternative call format would be: | ||
| + | |||
| + | <system-execution-file> <input-folder> <output-filename> <training-folder> | ||
| + | |||
| + | where the training folder contains appropriate files for training. Obviously, if this third argument is not given, it is assumed that there is no learning/training phase. | ||
=== Input data === | === Input data === | ||
| Line 34: | Line 51: | ||
# MIDI note number in score (int) | # MIDI note number in score (int) | ||
| − | |||
=== Evaluation metrics === | === Evaluation metrics === | ||
| Line 40: | Line 56: | ||
=== Evaluator pseudo-code === | === Evaluator pseudo-code === | ||
| − | == | + | == Reference Database == |
| + | Reference database contains score, and performance audio (for system call) and a reference alignment (for evaluations). | ||
| + | |||
| + | === Contributions === | ||
| + | |||
| + | === Content Format === | ||
| + | ==== Score Files ==== | ||
| + | Scores are in MIDI formats. | ||
| + | ==== Audio Files ==== | ||
| + | Audio will be either WAVE or AIFF that contain real performances of a given MIDI score. | ||
| + | ==== Reference alignment ==== | ||
| + | The ''reference files'' constitute a ground truth alignment between a MIDI score and a recording of it. They have one line per score note, with the columns: | ||
| + | |||
| + | # note onset time in reference audio file [ms] | ||
| + | # note start time in score [ms] | ||
| + | # MIDI note number in score [nn] | ||
== Potential Participants == | == Potential Participants == | ||
Revision as of 14:08, 19 July 2006
Contents
Proposers
- Arshia Cont (University of California in San Diego (UCSD) and Ircam - Realtime Applications Team, France) - cont@ircam.fr
- Diemo Schwarz (Ircam - Realtime Applications Team, France) - schwarz@ircam.fr
Title
Score Following
Description
Score Following is the real-time alignment of incoming music signal to the music score. The music signal can be symbolic (Midi Score Following) or Audio.
This page describes a proposal for evaluation of score following systems. Discussion of the evaluation procedures on the MIREX 06 "ScoreFollowing06" contest planning list will be documented on the Score Following page. A full digest of the discussions is available to subscribers from the MIREX 06 "ScoreFollowing06" contest planning list archives.
Submissions will be required to estimate alignment precision according to the indexed times, type of alignment (monophonic, polyphonic), type of training and realtime performance, also separated into two domains (upon enough submissions) for symbolic and audio systems.
Status
Evaluation procedures
Evaluation procedure consists of running score followers on a database of aligned audio to score where the database contains score, and performance audio (for system call) and a reference alignment (for evaluations) -- See below for details.
Suggested calling formats for submitted algorithms
During evaluation, each system will be called in command line with the following format:
<system-execution-file> <input-folder> <output-filename>
The input folder contains the score and audio performance of the score. Your submitted binaries should be able to BROWSE this folder and use the appropriate score and audio file and undertake the score following task, and write the results to the output file as given.
It is important to be able to create the output ascii file in a "different" path than the default.
In order to consider the issue of training, an alternative call format would be:
<system-execution-file> <input-folder> <output-filename> <training-folder>
where the training folder contains appropriate files for training. Obviously, if this third argument is not given, it is assumed that there is no learning/training phase.
Input data
Each system will need an Audio input as well as a Score to follow (or align).
File formats
Score used for this year's MIREX would be MIDI files. Audio format would be standard WAV or AIFF, as performances of the given MIDI score.
Output data
File formats
ASCII output for each score following system as described below.
Content
The result files represent the alignment found by a score following system between a MIDI score and a recording of a performance of it. They have one line per detected note with the columns:
- estimated note onset time in performance audio file (ms)
- detection time relative to performance audio file (ms)
- note start time in score (ms)
- MIDI note number in score (int)
Evaluation metrics
Evaluator pseudo-code
Reference Database
Reference database contains score, and performance audio (for system call) and a reference alignment (for evaluations).
Contributions
Content Format
Score Files
Scores are in MIDI formats.
Audio Files
Audio will be either WAVE or AIFF that contain real performances of a given MIDI score.
Reference alignment
The reference files constitute a ground truth alignment between a MIDI score and a recording of it. They have one line per score note, with the columns:
- note onset time in reference audio file [ms]
- note start time in score [ms]
- MIDI note number in score [nn]
Potential Participants
- Arshia Cont (UCSD / Ircam)
- Roger Dannenberg (Carnegie Mellon University)
- Christopher Raphael (Indiana university)
- Diemo Schwarz (Ircam)
- Miller Puckette (UCSD)
- Ozgur Izmirli (Connolle)
- Cort Lippe (University of Buffalo)
- Frank Weinstock (TimeWarp Technologies)
