Difference between revisions of "2006:Symbolic Melodic Similarity"
(→Task suggestion: Symbolic Melodic Similarity) |
(→Building of the ground truth) |
||
| Line 27: | Line 27: | ||
| − | === Building | + | === Building the ground truth === |
Unlike last year, it is now nearly impossible to manually build a proper ground truth in advance. | Unlike last year, it is now nearly impossible to manually build a proper ground truth in advance. | ||
Suggestion: Pool the top M results of all participating algorithms and let every participant judge the relevance of the matches for some queries. | Suggestion: Pool the top M results of all participating algorithms and let every participant judge the relevance of the matches for some queries. | ||
To make that a manageable burden, it is important that the algorithms do not only return the names of the matching MIDI files for tasks 2 and 3, but also where the matching bit starts and ends in the matching MIDI file. We can then automatically extract those matching bits and put them into small new MIDI files whose relevance can then be quickly checked. | To make that a manageable burden, it is important that the algorithms do not only return the names of the matching MIDI files for tasks 2 and 3, but also where the matching bit starts and ends in the matching MIDI file. We can then automatically extract those matching bits and put them into small new MIDI files whose relevance can then be quickly checked. | ||
Revision as of 09:40, 16 May 2006
Contents
Overview
This page is devoted to discussions of The MIREX06 Symbolic Melodic Similarity contest. Discussions on the MIREX 06 Symbolic Melodic Similarity contest planning list will be briefly digested on this page. A full digest of the discussions is available to subscribers from the MIREX 06 Symbolic Melodic Similarity contest planning list archives.
Task suggestion: Symbolic Melodic Similarity
Proposed tasks
1. Retrieve the most similar incipits from the UK subset of the RISM A/II collection (about 15,000 incipits), given one of the incipits as a query, and rank them by melodic similarity. Both the query and the collection are monophonic.
2. Like task 1, but with a collection of mostly polyphonic MIDI files to be searched for matches. The query would still be monophonic. The MIDI files 10,000 randomly picked files from a collection of about 60,000 MIDI files that were harvested from the Web. They include different genres (Western and Asian popular music, classical music, ringtones, just to name a few).
3. Like task 2, but with a smaller, more focused collection: about 1000 .kar files (Karaoke MIDI files) with mostly Western popular music.
Inputs/Outputs:
Task 1:
Input: about 15,000 MIDI files containing mostly monophonic incipits, and a MIDI file containing the monophonic query.
Expected Output: a list of the names of the X most similar matching MIDI files, ordered by similarity. (the value of X is to be decided)
Task 2: Input: about 10,000 mostly polyphonic MIDI files plus a MIDI file containing a monophonic query. Output: a list of the X most similar file names, ordered by similarity, plus for each file the time (offset from the beginning in seconds) where the query matches and where the matching bit ends.
Task 3: Like task 2.
Building the ground truth
Unlike last year, it is now nearly impossible to manually build a proper ground truth in advance.
Suggestion: Pool the top M results of all participating algorithms and let every participant judge the relevance of the matches for some queries. To make that a manageable burden, it is important that the algorithms do not only return the names of the matching MIDI files for tasks 2 and 3, but also where the matching bit starts and ends in the matching MIDI file. We can then automatically extract those matching bits and put them into small new MIDI files whose relevance can then be quickly checked.
