Difference between revisions of "2008:Query by Tapping"
From MIREX Wiki
(→Overview) |
(→Task description) |
||
| Line 3: | Line 3: | ||
== Task description == | == Task description == | ||
| − | * '''Test database''': | + | * '''Test database''': 103 ground-truth mono MIDI files. |
| − | * '''WAV Quries''': | + | * '''WAV Quries''': 533 query files to retrieve 103 known target from collection. So far, 1~6 human assessors have listened and tapped a 15 seconds query rhythm from beginning for each target songs. WAV files are recorded in 8k-8bit. |
| − | + | * '''Evaluation''': Return top 10 candidates for each query file. 1 point is scored for a hit in the top 10 and 0 is scored otherwise(Top-10 hit rate). | |
| − | * '''Evaluation''': | ||
== Data processing proposal for calling formats == | == Data processing proposal for calling formats == | ||
Revision as of 21:36, 21 August 2008
Contents
Overview
The main purpose of QBT(Query by Tapping) is to evaluate MIR system in retrieval ground-truth MIDI files by the tapping rhythm. This task provides query rhythm files in WAV formate. Evaluation database and query files can be download from http://210.68.135.13/ki/QBT.rar (updated on 2008/8/22)
Task description
- Test database: 103 ground-truth mono MIDI files.
- WAV Quries: 533 query files to retrieve 103 known target from collection. So far, 1~6 human assessors have listened and tapped a 15 seconds query rhythm from beginning for each target songs. WAV files are recorded in 8k-8bit.
- Evaluation: Return top 10 candidates for each query file. 1 point is scored for a hit in the top 10 and 0 is scored otherwise(Top-10 hit rate).
Data processing proposal for calling formats
Indexing the MIDIs collection
Indexing_exe <var1> <var2> where <var1>==<directory_of_MIDIs> <var2>==<indexing_files_output_and_working_directory>
Running for the query files
Running_exe <var3> <var4> <var5> where <var3>==<directory_of_indexed_file> <var4>==<directory_of_query_rhythm_files> <var5>==<answer_file_output_directory>
Data processing for output answer file formats
The answer file for each run would look like:
Q0001:0003,0567,0999,<insert X more responses>,XXXX Q0002:0103,0567,0998,<insert X more responses>,XXXX Q000X:0002,0567,0999,<insert X more responses>,XXXX
Each line represents to each of the queries in a given task run.
Submission closing date
22th August 2008.
Interested Participants
- Shu-Jen Show Hsiao(show.cs95g at nctu.edu.tw)
- Rainer Typke: I would be interested if the query data can also be made available in symbolic form so we can see what part of the performance comes from good onset detection from audio, and what comes from a good matching algorithm.
- Hong-Ru Lee (khair at mirlab dot org)
