Difference between revisions of "2014:Audio Fingerprinting"

From MIREX Wiki
Line 22: Line 22:
  
 
Command format:
 
Command format:
  builder %file.db.list% %db_dir%
+
  builder %fileList4db% %dir4db%
where %file.db.list% is the input list of database audio files named as uniq_key.wav For example:
+
where %fileList4db% is a file containing the input list of database audio files, with name convention as uniqueKey.wav. For example:
  ./AFP/database/00001.wav
+
  ./AFP/database/00001.mp3
  ./AFP/database/00002.wav
+
  ./AFP/database/00002.mp3
  ./AFP/database/00003.wav
+
  ./AFP/database/00003.mp3
  ./AFP/database/00004.wav
+
  ./AFP/database/00004.mp3
 
  ...
 
  ...
 
Output file(s) should be placed into %db_dir%
 
Output file(s) should be placed into %db_dir%

Revision as of 01:49, 27 July 2014

Description

This task is audio fingerprinting, also known as query by (exact but noisy) examples. Several companies have launched services based on such technology, including Shazam, Soundhound, Intonow, Viggle, etc. Though the technology has been around for years, there is no benchmark dataset for evaluation. This task is the first step toward building an extensive corpus for evaluating methodologies in audio fingerprinting.

Data

Database

  • 10,000 songs (*.mp3) in the database, in which there is exact one song corresponding to each query. (That is, there is no out-of-vocabulary query in the query set.) This dataset is hidden and not available for download.

Query set

The query set has two parts:

  • 4000 (???) clips of wav format: These are hidden and not available for download
  • 1264 clips of wav format: These recordings are noisy versions of George's music genre dataset. You can download the query set via this link

All the query set is mono recordings of 8-12 sec, with 44.1 KHz sampling rate and 16-bit resolution. The set was obtained via different brands of smartphone, at various locations with various kinds of environmental noise.

Evaluation Procedures

The evaluation is based on the query set (two parts), with top-1 hit rate being the performance index.

Submission Format

Participants are required to submit a breakdown version of the algorithm, which includes the following two parts:

1. Database Builder

Command format:

builder %fileList4db% %dir4db%

where %fileList4db% is a file containing the input list of database audio files, with name convention as uniqueKey.wav. For example:

./AFP/database/00001.mp3
./AFP/database/00002.mp3
./AFP/database/00003.mp3
./AFP/database/00004.mp3
...

Output file(s) should be placed into %db_dir%

2. Matcher

Command format:

matcher %db_dir% %file.query.list% %resultFile%

where %db_dir% is the directory for the built database.

%file.query.list% is the input list of query clips, for example:

./AFP/query/q0001.wav
./AFP/query/q0002.wav
./AFP/query/q0003.wav
./AFP/query/q0004.wav
...

The result file gives retrieved result for each query. The format should be:

%main_query_file_name% %main_top_1_candiate_file_name%

For example:

q0001 00204
q0002 08964
q0003 05566
...

Time and hardware limits

Due to the potentially high number of participants in this and other audio tasks, hard limits on the runtime of submissions are specified. The time/storage limits of different steps are shown in the following table:

Steps Time limit Storage (hard disk) limit
builder 24 hours 3 GB
matcher 10 hours N/A

Submissions that exceed these limitations may not receive a result.

Potential Participants

Discussion

name / email

Bibliography