2006:Audio Tempo Extraction - Revision history

IMIRSELBot: Robot: Automated text replacement (-\[\[([A-Z][^:]+)\]\] +2006:\1)

2010-05-13T18:04:24Z

Robot: Automated text replacement (-\[\[([A-Z][^:]+)\]\] +2006:\1)

2006-10-06T22:51:39Z

‎Proposer

2006-08-17T16:12:01Z

‎Evaluation Procedures

2006-08-16T21:28:06Z

2006-08-16T12:24:55Z

‎Output Data

2006-08-10T14:43:54Z

‎Participants

2006-08-10T14:23:19Z

‎Description

2006-08-10T14:17:12Z

‎Description

2006-08-09T08:33:25Z

‎Participants

2006-08-09T08:18:04Z

‎Participants

@@ Line 1: / Line 1: @@
 == Results ==
-Results are on [[Audio Tempo Extraction Results]] page.
+Results are on [[2006:Audio Tempo Extraction Results]] page.
 == Proposer ==

@@ Line 1: / Line 1: @@
 == Proposer ==
@@ Line 6: / Line 9: @@
 Dirk Moelants (IPEM, Ghent University) dirk@moelants.net
 Title
 == Automatic tempo extraction ==

@@ Line 72: / Line 72: @@
 ''References'':
-* McKinney, M.F. and Moelants, D. (2004), Deviations from the resonance theory of tempo induction, Conference on Interdisciplinary Musicology, Graz. URL: http://gewi.kfunigraz.ac.at/~cim04/CIM04_paper_pdf/McKinney_Moelants_CIM04_proceedings_t.pdf
+* McKinney, M.F. and Moelants, D. (2004), Deviations from the resonance theory of tempo induction, Conference on Interdisciplinary Musicology, Graz. URL: http://www-gewi.uni-graz.at/staff/parncutt/cim04/CIM04_paper_pdf/McKinney_Moelants_CIM04_proceedings_t.pdf
-* Moelants, D. and McKinney, M.F. (2004), Tempo perception and musical content: What makes a piece slow, fast, or temporally ambiguous? International Conference on Music Perception & Cognition, Evanston, IL. URL: http://www.northwestern.edu/icmpc/proceedings/ICMPC8/PDF/AUTHOR/MP040237.PDF
+* Moelants, D. and McKinney, M.F. (2004), Tempo perception and musical content: What makes a piece slow, fast, or temporally ambiguous? International Conference on Music Perception & Cognition, Evanston, IL. URL: http://icmpc8.umn.edu/proceedings/ICMPC8/PDF/AUTHOR/MP040237.PDF
 '''2) Evaluation of tempo extraction algorithms'''
@@ Line 84: / Line 84: @@
 The algorithm with the best average P-score will win the contest. We will provide some measures of statistical significance to the results, most likely through bootstrapping the test data.
 == Relevant Test Collections ==

← Older revision		Revision as of 21:28, 16 August 2006
Line 99:		Line 99:

	We will provide 20 excerpts with ground truth data for participants to try/tune their algorithms before submission. The remaining 140 excerpts will be novel to all participants.		We will provide 20 excerpts with ground truth data for participants to try/tune their algorithms before submission. The remaining 140 excerpts will be novel to all participants.
		+
		+	==Practice Data==
		+	You can find it here:
		+
		+	https://www.music-ir.org/evaluation/MIREX/data/2006/beat/
		+
		+	User: beattrack Password: b34trx
		+
		+	https://www.music-ir.org/evaluation/MIREX/data/2006/tempo/
		+
		+	User: tempo Password: t3mp0
		+
		+	Data has been uploaded in both .tgz and .zip format.

@@ Line 37: / Line 37: @@
 === Output Data ===
-Submitted programs should output two tempi (a slower tempo, T1, and a faster tempo, T2) as well as the strength of T1 relative to T2 (0-1). The results should either be written to a text file in the following format:
+Submitted programs should output two tempi (a slower tempo, T1, and a faster tempo, T2) as well as the strength of T1 relative to T2 (0-1). The relative strength of ST2 (not output) is simply 1 - ST1.  The results should either be written to a text file in the following format:
 T1<tab>T2<tab>ST1

@@ Line 52: / Line 52: @@
 * Douglas Eck (University of Montreal), eckdoug@iro.umontreal.ca
 * Matthew Davies (Queen Mary, University of London), matthew.davies@elec.qmul.ac.uk
 Other Potential Participants

@@ Line 25: / Line 25: @@
 A more pragmatic reason for using perceptual tempo rather than notated tempo as a ground truth for our contest is that we simply do not have the notated tempo of our test set. If we notate it by having a panel of expert listeners tap along and label the excerpts, we are by default dealing with the perceived tempo. The handling of this data as ground truth must be done with care.
-=== Audio Data ===
+=== Input data ===
 === Output Data ===
-Submitted programs should output the primary tempo, the secondary tempo and the relative strength of . The results should either be saved to a text file.
+Submitted programs should output two tempi (a slower tempo, T1, and a faster tempo, T2) as well as the strength of T1 relative to T2 (0-1). The results should either be written to a text file in the following format:
-.0123156<br>
+T1<tab>T2<tab>ST1
 Each submission should be accompanied with a README file describing how the program should be used. For instance:

← Older revision		Revision as of 14:17, 10 August 2006
Line 25:		Line 25:
	A more pragmatic reason for using perceptual tempo rather than notated tempo as a ground truth for our contest is that we simply do not have the notated tempo of our test set. If we notate it by having a panel of expert listeners tap along and label the excerpts, we are by default dealing with the perceived tempo. The handling of this data as ground truth must be done with care.		A more pragmatic reason for using perceptual tempo rather than notated tempo as a ground truth for our contest is that we simply do not have the notated tempo of our test set. If we notate it by having a panel of expert listeners tap along and label the excerpts, we are by default dealing with the perceived tempo. The handling of this data as ground truth must be done with care.

		+	=== Audio Data ===
		+
		+	=== Output Data ===
		+
		+	Submitted programs should output the primary tempo, the secondary tempo and the relative strength of . The results should either be saved to a text file.
		+
		+	Example of possible output:
		+
		+	0.0123156<br>
		+	1.9388662<br>
		+	3.8777323<br>
		+	5.8165980<br>
		+	7.7554634<br>
		+
		+	Each submission should be accompanied with a README file describing how the program should be used. For instance:
		+
		+	To run the program ''foobar'' on the file input.wav and store the results in the file output.txt, the following command should be used:
		+
		+	foobar -i input.wav > output.txt

	== Participants ==		== Participants ==

@@ Line 38: / Line 38: @@
 * Bill Sethares (University of Wisconsin-Madison), sethares@ece.wisc.edu
 * Fabien Gouyon (University Pompeu Fabra) and Simon Dixon (OFAI), fgouyon@iua.upf.es, simon@oefai.at
-* Iasonas Antonopoulos (University of Athens), jantonop@di.uoa.gr
+* Iasonas Antonopoulos (University of Athens) and Aggelos Pikrakis (University of Athens), jantonop@di.uoa.gr, pikrakis@di.uoa.gr
 == Evaluation Procedures ==