Difference between revisions of "MIREX HOME"

From MIREX Wiki
(MIREX 2016 Deadline Dates)
(MIREX 2018 Deadline Dates)
 
(20 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Welcome to MIREX 2016==
+
==Welcome to MIREX 2018==
  
This is the main page for the eleventh running of the Music Information Retrieval Evaluation eXchange (MIREX 2016). The International Music Information Retrieval Systems Evaluation Laboratory ([https://music-ir.org 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 2016.  
+
This is the main page for the eleventh running of the Music Information Retrieval Evaluation eXchange (MIREX 2018). 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 2018.  
  
The MIREX 2016 community will hold its annual meeting as part of [https://wp.nyu.edu/ismir2016/ The 17th International Conference on Music Information Retrieval], ISMIR 2016, which will be held in New York City, USA, August 7-11, 2016. The MIREX plenary and poster sessions will be held during the conference.
+
The MIREX 2018 community will hold its annual meeting as part of [http://ismir2018.ircam.fr The 19th International Society for Music Information Retrieval Conference], ISMIR 2018, which will be held in Paris, France, September 23-27, 2018.
  
 
J. Stephen Downie<br>
 
J. Stephen Downie<br>
Line 10: Line 10:
 
==Task Leadership Model==
 
==Task Leadership Model==
  
Like ISMIR 2015, we are prepared to improve the distribution of tasks for the upcoming MIREX 2016.  To do so, we really need leaders to help us organize and run each task.
+
Like previous years, we are prepared to improve the distribution of tasks for the upcoming MIREX 2018.  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 [[2016: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/5igUsWBxrwMvF2h62 here]. Current information about task captains can be found on the [[2018: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 2016 Deadline Dates==
+
==MIREX 2018 Deadline Dates==
 +
* <del>'''July 21st 2018'''</del>  '''July 31st 2018'''
 +
** [[2018:Audio Classification (Train/Test) Tasks]] <TC: Yun Hao (IMIRSEL)>, including
 +
*** Audio US Pop Genre Classification
 +
*** Audio Latin Genre Classification
 +
*** Audio Music Mood Classification
 +
*** Audio Classical Composer Identification
 +
** [[2018:Audio K-POP Mood Classification]] <TC: Yun Hao (IMIRSEL)>
 +
** [[2018:Audio K-POP Genre Classification]] <TC: Yun Hao (IMIRSEL)>
 +
** [[2018:Audio Fingerprinting]] <TC: Chung-Che Wang>
  
* '''June 23rd 2016'''
+
* '''July 31st 2018'''
** Audio Classification (Train/Test) Tasks
+
** [[2018:Multiple Fundamental Frequency Estimation & Tracking]] <TC: Yun Hao (IMIRSEL)>
 +
** [[2018:Set List Identification]] <TC: Ming-Chi Yen>
 +
** [[2018:Audio Melody Extraction]] <TC: Derek Wu>
  
* '''July 1st 2016'''
+
* '''August 4th 2018'''
** Audio Music Similarity and Retrieval
+
** [[2018:Audio Onset Detection]] <TC: Vidya Rangasayee, Priya Arora, Sebastian Böck>
** Structural Segmentation
+
** [[2018:Audio Beat Tracking]] <TC: Aggelos Gkiokas>
** Multiple Fundamental Frequency Estimation & Tracking
+
** [[2018:Audio Key Detection]] <TC: Johan Pauwels>
** Audio Tempo Estimation
+
** [[2018:Audio Downbeat Estimation]] <TC: Mickaël Zehren, Bientinesi, Paolo>
** Set List Identification  
+
** [[2018:Real-time Audio to Score Alignment (a.k.a Score Following)]] <TC: Julio Carabias>
 +
** [[2018:Audio Cover Song Identification]] <TC: Chris Tralie>
 +
** [[2018:Audio Chord Estimation]] <TC: Johan Pauwels>
  
* '''July 8th 2016'''
+
* '''August 11th 2018'''
** Audio Onset Detection
+
** [[2018:Automatic Lyrics-to-Audio Alignment]] <TC: Rong Gong, Georgi Dzhambazov>
** Audio Beat Tracking
 
** 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
 
** Audio Offset Detection
 
  
'''Nota Bene''': We will have about three grand UX challenges. The deadlines will be announced soon.
+
* '''August 18th 2018'''
 +
** [[2018:Drum Transcription]] <TC: Richard Vogl, Carl Southall, Chih-Wei Wu>
  
==MIREX 2016 Submission Instructions==
+
* '''August 25th 2018'''
 +
** [[2018:Patterns for Prediction]] (offshoot of [[2017:Discovery of Repeated Themes & Sections]]) <TC: Iris Ren, Berit Janssen, Tom Collins>
 +
** [[2018:Audio Tempo Estimation]] <TC: Aggelos Gkiokas>
 +
 
 +
* '''August 26th 2018'''
 +
** [[2018:Music and/or Speech Detection]] <TC: Blai Meléndez-Catalán, Emilio Molina, David Doukhan, Jan Schlüter>
 +
 
 +
==MIREX 2018 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 2016 Submission Instructions]] including both the tutorial video and the text
+
* Be sure to follow the  [[MIREX 2018 Submission Instructions]] including both the tutorial video and the text
* The MIREX 2016 Submission System can be found at: https://www.music-ir.org/mirex/sub/ .
+
* The MIREX 2018 Submission System can be found at: https://www.music-ir.org/mirex/sub/ .
 
 
==MIREX 2016 Possible Evaluation Tasks==
 
 
 
* [[2016:GC16UX:JDISC|2016:Grand Challenge on User Experience (J-DISC)]]
 
* [[2016:GC16UX|2016:Grand Challenge on User Experience]]
 
* [[2016:Audio Classification (Train/Test) Tasks]], incorporating:
 
** Audio US Pop Genre Classification
 
** Audio Latin Genre Classification
 
** Audio Music Mood Classification
 
** Audio Classical Composer Identification
 
** [[2016:Audio K-POP Mood Classification]]
 
** [[2016:Audio K-POP Genre Classification]]
 
* [[2016:Audio Cover Song Identification]]
 
* [[2016:Audio Tag Classification]]
 
* [[2016:Audio Music Similarity and Retrieval]]
 
* [[2016:Symbolic Melodic Similarity]]
 
* [[2016:Audio Onset Detection]]
 
* [[2016:Audio Key Detection]]
 
* [[2016:Real-time Audio to Score Alignment (a.k.a Score Following)]]
 
* [[2016:Query by Singing/Humming]]
 
* [[2016:Audio Melody Extraction]]
 
* [[2016:Multiple Fundamental Frequency Estimation & Tracking]]
 
* [[2016:Audio Chord Estimation]]
 
* [[2016:Query by Tapping]]
 
* [[2016:Audio Beat Tracking]]
 
* [[2016:Structural Segmentation]]
 
* [[2016:Audio Tempo Estimation]]
 
* [[2016:Discovery of Repeated Themes & Sections]]
 
* [[2016:Audio Downbeat Estimation]]
 
* [[2016:Audio Fingerprinting]]
 
* [[2016:Singing Voice Separation]]
 
* [[2016:Set List Identification]]
 
  
 +
==MIREX 2018 Evaluation==
  
 
===Note to New Participants===
 
===Note to New Participants===
Line 115: Line 93:
 
Because MIREX is premised upon the sharing of ideas and results, '''ALL''' MIREX participants are expected to:
 
Because MIREX is premised upon the sharing of ideas and results, '''ALL''' MIREX participants are expected to:
  
# 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 program(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 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)
+
# submit a FINALIZED 2-3 page extended abstract PDF in the ISMIR format prior to ISMIR 2018 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 2016 poster session at ISMIR 2016
+
# present a poster at the MIREX 2018 poster session at ISMIR 2018
 
 
  
 
===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 [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.  
+
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://goo.gl/forms/96Wndw9j9dzv4x3c2 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 2018, submissions with difficulty 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.
 
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 2016==
+
==Getting Involved in MIREX 2018==
MIREX is a community-based endeavour. Be a part of the community and help make MIREX 2016 the best yet.
+
MIREX is a community-based endeavour. Be a part of the community and help make MIREX 2018 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 2016 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 2018 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 2016, 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 2016 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 2018, 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 2018 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 2016 - 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 2018 - providing a standardised set of interfaces and output to disciplined evaluation procedures for a great many MIR tasks.
  
  
Line 146: Line 123:
 
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 - 2015 Wikis==
+
==MIREX 2005 - 2017 Wikis==
Content from MIREX 2005 - 2015 are available at:
+
Content from MIREX 2005 - 2016 are available at:
 +
'''[[2017:Main_Page|MIREX 2017]]'''
 +
'''[[2016:Main_Page|MIREX 2016]]'''
 
'''[[2015:Main_Page|MIREX 2015]]'''  
 
'''[[2015:Main_Page|MIREX 2015]]'''  
 
'''[[2014:Main_Page|MIREX 2014]]'''  
 
'''[[2014:Main_Page|MIREX 2014]]'''  

Latest revision as of 11:13, 22 August 2018

Welcome to MIREX 2018

This is the main page for the eleventh running of the Music Information Retrieval Evaluation eXchange (MIREX 2018). 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 2018.

The MIREX 2018 community will hold its annual meeting as part of The 19th International Society for Music Information Retrieval Conference, ISMIR 2018, which will be held in Paris, France, September 23-27, 2018.

J. Stephen Downie
Director, IMIRSEL

Task Leadership Model

Like previous years, we are prepared to improve the distribution of tasks for the upcoming MIREX 2018. 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 2018: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 2018 Deadline Dates

MIREX 2018 Submission Instructions

MIREX 2018 Evaluation

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 program(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 2018 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 2018 poster session at ISMIR 2018

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 2018, submissions with difficulty 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 2018

MIREX is a community-based endeavour. Be a part of the community and help make MIREX 2018 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 2018 tasks. Subscription information at: EvalFest Central.

If you are participating in MIREX 2018, 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 2018 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 2018 - 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 - 2017 Wikis

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