Difference between revisions of "MIREX HOME"

From MIREX Wiki
(MIREX 2015 Deadline Dates (Tentative))
(MIREX 2017 Deadline Dates)
(34 intermediate revisions by 6 users not shown)
Line 1: Line 1:
==Welcome to MIREX 2015==
+
==Welcome to MIREX 2017==
  
This is the main page for the eleventh running of the Music Information Retrieval Evaluation eXchange (MIREX 2015). The International Music Information Retrieval Systems Evaluation Laboratory ([https://music-ir.org/evaluation IMIRSEL]) at the Graduate School of Library and Information Science ([http://www.lis.illinois.edu GSLIS]), University of Illinois at Urbana-Champaign ([http://www.illinois.edu UIUC]) is the principal organizer of MIREX 2015.  
+
This is the main page for the eleventh running of the Music Information Retrieval Evaluation eXchange (MIREX 2017). The International Music Information Retrieval Systems Evaluation Laboratory (IMIRSEL) at [https://ischool.illinois.edu School of Information Sciences], University of Illinois at Urbana-Champaign ([http://www.illinois.edu UIUC]) is the principal organizer of MIREX 2017.  
  
The MIREX 2015 community will hold its annual meeting as part of [http://ismir2015.uma.es The 16th International Conference on Music Information Retrieval], ISMIR 2015, which will be held in Malaga, Spain, October 26th-30th, 2015. The MIREX plenary and poster sessions will be held during the conference.
+
The MIREX 2017 community will hold its annual meeting as part of [https://ismir2017.smcnus.org The 18th International Conference on Music Information Retrieval], ISMIR 2017, which will be held in Suzhou, China, October 23-28, 2017.
  
 
J. Stephen Downie<br>
 
J. Stephen Downie<br>
Line 10: Line 10:
 
==Task Leadership Model==
 
==Task Leadership Model==
  
Like ISMIR 2014, we are prepared to improve the distribution of tasks for the upcoming MIREX 2015.  To do so, we really need leaders to help us organize and run each task.
+
Like ISMIR 2016, we are prepared to improve the distribution of tasks for the upcoming MIREX 2017.  To do so, we really need leaders to help us organize and run each task.
  
To volunteer to lead a task, please add your name to the "Captains" column on the new [[2015:Task Captains]] page. Please direct any communication to the [https://mail.lis.illinois.edu/mailman/listinfo/evalfest EvalFest] mailing list.
+
To volunteer to lead a task, please complete the form [https://goo.gl/forms/bDID8cOV8p7mJ9Nt1 here]. Current information about task captains can be found on the [[2017:Task Captains]] page. Please direct any communication to the [https://mail.lis.illinois.edu/mailman/listinfo/evalfest EvalFest] mailing list.
  
 
What does it mean to lead a task?
 
What does it mean to lead a task?
Line 24: Line 24:
 
We really need leaders to help us this year!
 
We really need leaders to help us this year!
  
==MIREX 2015 Deadline Dates (Tentative)==
+
==MIREX 2017 Deadline Dates==
 +
* '''August 21st 2017'''
 +
** Audio Classification (Train/Test) Tasks <TC: IMIRSEL>
 +
** Audio K-POP Genre Classification <TC: IMIRSEL>
 +
** Audio K-POP Mood Classification <TC: IMIRSEL>
 +
** Audio Fingerprinting <TC: Chung-Che Wang>
  
* '''July 16th 2015'''
+
* '''August 31st 2017'''
** Audio Classification (Train/Test) Tasks
+
** Structural Segmentation <TC: Matthew McCallum>
 +
** Multiple Fundamental Frequency Estimation & Tracking <TC: Yun Hao (IMIRSEL)>
 +
** Audio Tempo Estimation <TC: Aggelos Gkiokas, Sebastian Böck, Paul Brossier, Matthew McCallum>
 +
** Set List Identification <TC: Ming-Chi Yen>
  
* '''August 16th 2015'''
+
* '''September 4th 2017'''
** Audio Music Similarity and Retrieval
+
** Audio Onset Detection <TC: Sebastian Böck, Paul Brossier, Matthew McCallum>
** Symbolic Melodic Similarity
+
** Audio Beat Tracking <TC: Sebastian Böck, Paul Brossier, Matthew McCallum>
** Structural Segmentation
+
** Audio Key Detection <TC: Johan Pauwels>
** Multiple Fundamental Frequency Estimation & Tracking
+
** Audio Downbeat Detection <TC: Sebastian Böck, Paul Brossier, Matthew McCallum>
** Audio Tempo Estimation
+
** Real-time Audio to Score Alignment(a.k.a Score Following) <TC: Julio Carabias>
** Audio Offset Detection
+
** Audio Cover Song Identification <TC: Chris Tralie, Ming-Chi Yen>
** Audio Tag Classification
+
** Discovery of Repeated Themes & Sections <TC: Tom Collins,Anja Volk,Berit Janssen,Iris Ren>
** Set List Identification
+
** Audio Chord Estimation <TC: Johan Pauwels>
 +
** Query by Singing/Humming <TC:Cheng-Tse Wu>
  
* '''September 9th 2015'''
+
* '''September 11th 2017'''
** Audio Onset Detection
+
** Automatic Lyrics-to-Audio Alignment <TC: Georgi Dzhambazov, Jens Kofod Hansen>
** Audio Beat Tracking
+
** Drum Transcription <TC: Richard Vogl, Carl Southall, Chih-Wei Wu>
** Audio Key Detection
 
** Audio Downbeat Detection
 
** Real-time Audio to Score Alignment(a.k.a Score Following)
 
** Audio Cover Song Identification
 
** Discovery of Repeated Themes & Sections
 
** Audio Melody Extraction
 
** Query by Singing/Humming
 
** Audio Chord Estimation
 
** Singing Voice Separation
 
** Audio Fingerprinting
 
** Music/Speech Classification/Detection
 
  
'''Nota Bene''': We will have about three grand UX challenges. The deadlines will be announced soon.
+
==MIREX 2017 Submission Instructions==
 
 
==MIREX 2015 Submission Instructions==
 
 
* Be sure to read through the rest of this page
 
* Be sure to read through the rest of this page
 
* Be sure to read though the task pages for which you are submitting
 
* Be sure to read though the task pages for which you are submitting
 
* Be sure to follow the [[2009:Best Coding Practices for MIREX | Best Coding Practices for MIREX]]
 
* Be sure to follow the [[2009:Best Coding Practices for MIREX | Best Coding Practices for MIREX]]
* Be sure to follow the  [[MIREX 2014 Submission Instructions]] including both the tutorial video and the text
+
* Be sure to follow the  [[MIREX 2017 Submission Instructions]] including both the tutorial video and the text
 +
* The MIREX 2017 Submission System can be found at: https://www.music-ir.org/mirex/sub/ .
  
==MIREX 2015 Possible Evaluation Tasks==
+
==MIREX 2017 Possible Evaluation Tasks==
  
* [[2015:GC15UX|2015:Grand Challenge on User Experience]]
+
* [[2017:Audio Classification (Train/Test) Tasks]], incorporating:
* [[2015:Audio Classification (Train/Test) Tasks]], incorporating:
 
 
** Audio US Pop Genre Classification
 
** Audio US Pop Genre Classification
 
** Audio Latin Genre Classification
 
** Audio Latin Genre Classification
 
** Audio Music Mood Classification
 
** Audio Music Mood Classification
 
** Audio Classical Composer Identification
 
** Audio Classical Composer Identification
** [[2015:Audio K-POP Mood Classification]]
+
** [[2017:Audio K-POP Mood Classification]]
** [[2015:Audio K-POP Genre Classification]]
+
** [[2017:Audio K-POP Genre Classification]]
* [[2015:Audio Cover Song Identification]]
+
* [[2017:Audio Beat Tracking]]
* [[2015:Audio Tag Classification]]  
+
* [[2017:Audio Chord Estimation]]
* [[2015:Audio Music Similarity and Retrieval]]
+
* [[2017:Audio Cover Song Identification]]
* [[2015:Symbolic Melodic Similarity]]
+
* [[2017:Audio Downbeat Estimation]]
* [[2015:Audio Onset Detection]]
+
* [[2017:Audio Key Detection]]
* [[2015:Audio Key Detection]]
+
* [[2017:Audio Onset Detection]]
* [[2015:Real-time Audio to Score Alignment (a.k.a Score Following)]]
+
* [[2017:Audio Tempo Estimation]]
* [[2015:Query by Singing/Humming]]
+
* [[2017:Automatic Lyrics-to-Audio Alignment]]
* [[2015:Audio Melody Extraction]]
+
* [[2017:Drum Transcription]]
* [[2015:Multiple Fundamental Frequency Estimation & Tracking]]
+
* [[2017:Multiple Fundamental Frequency Estimation & Tracking]]
* [[2015:Audio Chord Estimation]]
+
* [[2017:Real-time Audio to Score Alignment (a.k.a Score Following)]]
* [[2015:Query by Tapping]]
+
* [[2017:Structural Segmentation]]
* [[2015:Audio Beat Tracking]]
+
* [[2017:Discovery of Repeated Themes & Sections]]
* [[2015:Structural Segmentation]]
+
* [[2017:Audio Fingerprinting]]
* [[2015:Audio Tempo Estimation]]
+
* [[2017:Set List Identification]]
* [[2015:Discovery of Repeated Themes & Sections]]
+
* [[2017:Query by Singing/Humming]]
* [[2015:Audio Downbeat Estimation]]
+
* [[2016:Singing Voice Separation]] (TASK INACTIVE THIS YEAR)
* [[2015:Audio Fingerprinting]]
+
* [[2016:Audio Offset Detection]] (TASK INACTIVE THIS YEAR)
* [[2015:Singing Voice Separation]]
+
* [[2016:Audio Tag Classification]] (TASK INACTIVE THIS YEAR)
 +
* [[2016:Audio Music Similarity and Retrieval]] (TASK INACTIVE THIS YEAR)
 +
* [[2016:Symbolic Melodic Similarity]] (TASK INACTIVE THIS YEAR)
 +
* [[2016:Audio Melody Extraction]] (TASK INACTIVE THIS YEAR)
 +
* [[2016:Query by Tapping]] (TASK INACTIVE THIS YEAR)
  
  
Line 116: Line 116:
  
 
# submit a DRAFT 2-3 page extended abstract PDF in the ISMIR format about the submitted programme(s) to help us and the community better understand how the algorithm works when submitting their programme(s).
 
# submit a DRAFT 2-3 page extended abstract PDF in the ISMIR format about the submitted programme(s) to help us and the community better understand how the algorithm works when submitting their programme(s).
# submit a FINALIZED 2-3 page extended abstract PDF in the ISMIR format prior to ISMIR 2014 for posting on the respective results pages (sometimes the same abstract can be used for multiple submissions; in many cases the DRAFT and FINALIZED abstracts are the same)
+
# submit a FINALIZED 2-3 page extended abstract PDF in the ISMIR format prior to ISMIR 2016 for posting on the respective results pages (sometimes the same abstract can be used for multiple submissions; in many cases the DRAFT and FINALIZED abstracts are the same)
# present a poster at the MIREX 2014 poster session at ISMIR 2014
+
# present a poster at the MIREX 2016 poster session at ISMIR 2016
  
  
 
===Software Dependency Requests===
 
===Software Dependency Requests===
If you have not submitted to MIREX before or are unsure whether IMIRSEL currently supports some of the software/architecture dependencies for your submission a [https://docs.google.com/forms/d/1ZgC72BhhN0PFFiaj9NDejRdl1eW7wAFLIyMhAtoV0CA/viewform?usp=send_form dependency request form is available]. Please submit details of your dependencies on this form and the IMIRSEL team will attempt to satisfy them for you.  
+
If you have not submitted to MIREX before or are unsure whether IMIRSEL currently supports some of the software/architecture dependencies for your submission a [http://goo.gl/forms/pAxzWnuHti dependency request form is available]. Please submit details of your dependencies on this form and the IMIRSEL team will attempt to satisfy them for you.  
  
 
Due to the high volume of submissions expected at MIREX 2015, submissions with difficult to satisfy dependencies that the team has not been given sufficient notice of may result in the submission being rejected.
 
Due to the high volume of submissions expected at MIREX 2015, submissions with difficult to satisfy dependencies that the team has not been given sufficient notice of may result in the submission being rejected.
Line 128: Line 128:
 
Finally, you will also be expected to detail your software/architecture dependencies in a README file to be provided to the submission system.
 
Finally, you will also be expected to detail your software/architecture dependencies in a README file to be provided to the submission system.
  
==Getting Involved in MIREX 2015==
+
==Getting Involved in MIREX 2017==
MIREX is a community-based endeavour. Be a part of the community and help make MIREX 2015 the best yet.
+
MIREX is a community-based endeavour. Be a part of the community and help make MIREX 2017 the best yet.
  
  
 
===Mailing List Participation===
 
===Mailing List Participation===
If you are interested in formal MIR evaluation, you should also subscribe to the "MIREX" (aka "EvalFest") mail list and participate in the community discussions about defining and running MIREX 2015 tasks. Subscription information at:  
+
If you are interested in formal MIR evaluation, you should also subscribe to the "MIREX" (aka "EvalFest") mail list and participate in the community discussions about defining and running MIREX 2017 tasks. Subscription information at:  
 
[https://mail.lis.illinois.edu/mailman/listinfo/evalfest EvalFest Central].  
 
[https://mail.lis.illinois.edu/mailman/listinfo/evalfest EvalFest Central].  
  
If you are participating in MIREX 2015, it is VERY IMPORTANT that you are subscribed to EvalFest. Deadlines, task updates and other important information will be announced via this mailing list. Please use the EvalFest for discussion of MIREX task proposals and other MIREX related issues. This wiki (MIREX 2015 wiki) will be used to embody and disseminate task proposals, however, task related discussions should be conducted on the MIREX organization mailing list (EvalFest) rather than on this wiki, but should be summarized here.  
+
If you are participating in MIREX 2017, it is VERY IMPORTANT that you are subscribed to EvalFest. Deadlines, task updates and other important information will be announced via this mailing list. Please use the EvalFest for discussion of MIREX task proposals and other MIREX related issues. This wiki (MIREX 2017 wiki) will be used to embody and disseminate task proposals, however, task related discussions should be conducted on the MIREX organization mailing list (EvalFest) rather than on this wiki, but should be summarized here.  
  
Where possible, definitions or example code for new evaluation metrics or tasks should be provided to the IMIRSEL team who will embody them in software as part of the NEMA analytics framework, which will be released to the community at or before ISMIR 2015 - providing a standardised set of interfaces and output to disciplined evaluation procedures for a great many MIR tasks.
+
Where possible, definitions or example code for new evaluation metrics or tasks should be provided to the IMIRSEL team who will embody them in software as part of the NEMA analytics framework, which will be released to the community at or before ISMIR 2017 - providing a standardised set of interfaces and output to disciplined evaluation procedures for a great many MIR tasks.
  
  
Line 146: Line 146:
 
Please note that because of "spam-bots", MIREX wiki registration requests may be moderated by IMIRSEL members. It might take up to 24 hours for approval (Thank you for your patience!).
 
Please note that because of "spam-bots", MIREX wiki registration requests may be moderated by IMIRSEL members. It might take up to 24 hours for approval (Thank you for your patience!).
  
==MIREX 2005 - 2014 Wikis==
+
==MIREX 2005 - 2016 Wikis==
Content from MIREX 2005 - 2014 are available at:
+
Content from MIREX 2005 - 2016 are available at:
 +
'''[[2016:Main_Page|MIREX 2016]]'''
 +
'''[[2015:Main_Page|MIREX 2015]]'''
 
'''[[2014:Main_Page|MIREX 2014]]'''  
 
'''[[2014:Main_Page|MIREX 2014]]'''  
 
'''[[2013:Main_Page|MIREX 2013]]'''  
 
'''[[2013:Main_Page|MIREX 2013]]'''  

Revision as of 13:49, 5 September 2017

Welcome to MIREX 2017

This is the main page for the eleventh running of the Music Information Retrieval Evaluation eXchange (MIREX 2017). The International Music Information Retrieval Systems Evaluation Laboratory (IMIRSEL) at School of Information Sciences, University of Illinois at Urbana-Champaign (UIUC) is the principal organizer of MIREX 2017.

The MIREX 2017 community will hold its annual meeting as part of The 18th International Conference on Music Information Retrieval, ISMIR 2017, which will be held in Suzhou, China, October 23-28, 2017.

J. Stephen Downie
Director, IMIRSEL

Task Leadership Model

Like ISMIR 2016, we are prepared to improve the distribution of tasks for the upcoming MIREX 2017. To do so, we really need leaders to help us organize and run each task.

To volunteer to lead a task, please complete the form here. Current information about task captains can be found on the 2017:Task Captains page. Please direct any communication to the EvalFest mailing list.

What does it mean to lead a task?

  • Update wiki pages as needed
  • Communicate with submitters and troubleshooting submissions
  • Execution and evaluation of submissions
  • Publishing final results

Due to the proprietary nature of much of the data, the submission system, evaluation framework, and most of the datasets will continue to be hosted by IMIRSEL. However, we are prepared to provide access to task organizers to manage and run submissions on the IMIRSEL systems.

We really need leaders to help us this year!

MIREX 2017 Deadline Dates

  • August 21st 2017
    • Audio Classification (Train/Test) Tasks <TC: IMIRSEL>
    • Audio K-POP Genre Classification <TC: IMIRSEL>
    • Audio K-POP Mood Classification <TC: IMIRSEL>
    • Audio Fingerprinting <TC: Chung-Che Wang>
  • August 31st 2017
    • Structural Segmentation <TC: Matthew McCallum>
    • Multiple Fundamental Frequency Estimation & Tracking <TC: Yun Hao (IMIRSEL)>
    • Audio Tempo Estimation <TC: Aggelos Gkiokas, Sebastian Böck, Paul Brossier, Matthew McCallum>
    • Set List Identification <TC: Ming-Chi Yen>
  • September 4th 2017
    • Audio Onset Detection <TC: Sebastian Böck, Paul Brossier, Matthew McCallum>
    • Audio Beat Tracking <TC: Sebastian Böck, Paul Brossier, Matthew McCallum>
    • Audio Key Detection <TC: Johan Pauwels>
    • Audio Downbeat Detection <TC: Sebastian Böck, Paul Brossier, Matthew McCallum>
    • Real-time Audio to Score Alignment(a.k.a Score Following) <TC: Julio Carabias>
    • Audio Cover Song Identification <TC: Chris Tralie, Ming-Chi Yen>
    • Discovery of Repeated Themes & Sections <TC: Tom Collins,Anja Volk,Berit Janssen,Iris Ren>
    • Audio Chord Estimation <TC: Johan Pauwels>
    • Query by Singing/Humming <TC:Cheng-Tse Wu>
  • September 11th 2017
    • Automatic Lyrics-to-Audio Alignment <TC: Georgi Dzhambazov, Jens Kofod Hansen>
    • Drum Transcription <TC: Richard Vogl, Carl Southall, Chih-Wei Wu>

MIREX 2017 Submission Instructions

MIREX 2017 Possible Evaluation Tasks


Note to New Participants

Please take the time to read the following review articles that explain the history and structure of MIREX.

Downie, J. Stephen (2008). The Music Information Retrieval Evaluation Exchange (2005-2007):
A window into music information retrieval research.Acoustical Science and Technology 29 (4): 247-255.
Available at: http://dx.doi.org/10.1250/ast.29.247

Downie, J. Stephen, Andreas F. Ehmann, Mert Bay and M. Cameron Jones. (2010).
The Music Information Retrieval Evaluation eXchange: Some Observations and Insights.
Advances in Music Information Retrieval Vol. 274, pp. 93-115
Available at: http://bit.ly/KpM5u5


Runtime Limits

We reserve the right to stop any process that exceeds runtime limits for each task. We will do our best to notify you in enough time to allow revisions, but this may not be possible in some cases. Please respect the published runtime limits.


Note to All Participants

Because MIREX is premised upon the sharing of ideas and results, ALL MIREX participants are expected to:

  1. submit a DRAFT 2-3 page extended abstract PDF in the ISMIR format about the submitted programme(s) to help us and the community better understand how the algorithm works when submitting their programme(s).
  2. submit a FINALIZED 2-3 page extended abstract PDF in the ISMIR format prior to ISMIR 2016 for posting on the respective results pages (sometimes the same abstract can be used for multiple submissions; in many cases the DRAFT and FINALIZED abstracts are the same)
  3. present a poster at the MIREX 2016 poster session at ISMIR 2016


Software Dependency Requests

If you have not submitted to MIREX before or are unsure whether IMIRSEL currently supports some of the software/architecture dependencies for your submission a dependency request form is available. Please submit details of your dependencies on this form and the IMIRSEL team will attempt to satisfy them for you.

Due to the high volume of submissions expected at MIREX 2015, submissions with difficult to satisfy dependencies that the team has not been given sufficient notice of may result in the submission being rejected.


Finally, you will also be expected to detail your software/architecture dependencies in a README file to be provided to the submission system.

Getting Involved in MIREX 2017

MIREX is a community-based endeavour. Be a part of the community and help make MIREX 2017 the best yet.


Mailing List Participation

If you are interested in formal MIR evaluation, you should also subscribe to the "MIREX" (aka "EvalFest") mail list and participate in the community discussions about defining and running MIREX 2017 tasks. Subscription information at: EvalFest Central.

If you are participating in MIREX 2017, it is VERY IMPORTANT that you are subscribed to EvalFest. Deadlines, task updates and other important information will be announced via this mailing list. Please use the EvalFest for discussion of MIREX task proposals and other MIREX related issues. This wiki (MIREX 2017 wiki) will be used to embody and disseminate task proposals, however, task related discussions should be conducted on the MIREX organization mailing list (EvalFest) rather than on this wiki, but should be summarized here.

Where possible, definitions or example code for new evaluation metrics or tasks should be provided to the IMIRSEL team who will embody them in software as part of the NEMA analytics framework, which will be released to the community at or before ISMIR 2017 - providing a standardised set of interfaces and output to disciplined evaluation procedures for a great many MIR tasks.


Wiki Participation

If you find that you cannot edit a MIREX wiki page, you will need to create a new account via: Special:Userlogin.

Please note that because of "spam-bots", MIREX wiki registration requests may be moderated by IMIRSEL members. It might take up to 24 hours for approval (Thank you for your patience!).

MIREX 2005 - 2016 Wikis

Content from MIREX 2005 - 2016 are available at: MIREX 2016 MIREX 2015 MIREX 2014 MIREX 2013 MIREX 2012 MIREX 2011 MIREX 2010 MIREX 2009 MIREX 2008 MIREX 2007 MIREX 2006 MIREX 2005