Difference between revisions of "2006:QBSH Discussion Page"
| Line 3: | Line 3: | ||
==Data Processing Proposal by J. Stephen Downie==: | ==Data Processing Proposal by J. Stephen Downie==: | ||
| − | + | ||
Given that some folks have fancy wav/pitch vector processors and some are just MIDI folks, I propose that we take advantage of file extensions for the various programmes to decide which type of data to process. Thus, we will build INDEX_THIS directories for each task (i.e., INDEX_THIS1 (for TASK1) and INDEX_THIS2 (for TASK2). In these directories will be ALL the required files necessary for indexing. For example: | Given that some folks have fancy wav/pitch vector processors and some are just MIDI folks, I propose that we take advantage of file extensions for the various programmes to decide which type of data to process. Thus, we will build INDEX_THIS directories for each task (i.e., INDEX_THIS1 (for TASK1) and INDEX_THIS2 (for TASK2). In these directories will be ALL the required files necessary for indexing. For example: | ||
| + | <pre> | ||
INDEX_THIS1/> (this is the simplest case..all MIDI) | INDEX_THIS1/> (this is the simplest case..all MIDI) | ||
T0000001.mid | T0000001.mid | ||
| Line 33: | Line 34: | ||
[2] This one of the orignal ground truth MIDI files, hence only 1 format--should we make other versions for consistency's sake? | [2] This one of the orignal ground truth MIDI files, hence only 1 format--should we make other versions for consistency's sake? | ||
| + | </pre> | ||
Under this model, the individual programmes are responsible for filtering/selecting which files they need to build indexes/run queries. | Under this model, the individual programmes are responsible for filtering/selecting which files they need to build indexes/run queries. | ||
OK, that should do it for now. PLEASE, PLEASE comment about FATAL flaws. We can quibble a bit LATER about evaluation subtleties (even after we have begun the indexing and runs). My next message will be about INPUT/OUTPUT issues that I just thought about. | OK, that should do it for now. PLEASE, PLEASE comment about FATAL flaws. We can quibble a bit LATER about evaluation subtleties (even after we have begun the indexing and runs). My next message will be about INPUT/OUTPUT issues that I just thought about. | ||
| − | + | ||
==Comment by Christian Sailor== | ==Comment by Christian Sailor== | ||
Hi Stephen, all | Hi Stephen, all | ||
Revision as of 09:54, 25 July 2006
Introduction
This page is for discussion concerning the details of the QBSH: Query-by-Singing/Humming task. The final outcomes of our discussions will be posted to the QBSH:_Query-by-Singing/Humming page.
==Data Processing Proposal by J. Stephen Downie==:
Given that some folks have fancy wav/pitch vector processors and some are just MIDI folks, I propose that we take advantage of file extensions for the various programmes to decide which type of data to process. Thus, we will build INDEX_THIS directories for each task (i.e., INDEX_THIS1 (for TASK1) and INDEX_THIS2 (for TASK2). In these directories will be ALL the required files necessary for indexing. For example:
INDEX_THIS1/> (this is the simplest case..all MIDI) T0000001.mid T0000002.mid T000000X.mid etc. INDEX_THIS2/> (note the mixed versions for T0000003) T0000001.mid T0000002.mid T0000003.mid T0000003.wav T0000003.pv etc. The same idea will hold for the QUERY_THIS1 (for TASK1)and QUERY_THIS2 (for TASK2) directories. For example: QUERY_THIS2/> Q0000001.mid Q0000001.wav Q0000001.pv Q0000002.mid [2] Q0000003.mid Q0000003.wav Q0000003.pv etc. [2] This one of the orignal ground truth MIDI files, hence only 1 format--should we make other versions for consistency's sake?
Under this model, the individual programmes are responsible for filtering/selecting which files they need to build indexes/run queries.
OK, that should do it for now. PLEASE, PLEASE comment about FATAL flaws. We can quibble a bit LATER about evaluation subtleties (even after we have begun the indexing and runs). My next message will be about INPUT/OUTPUT issues that I just thought about.
Comment by Christian Sailor
Hi Stephen, all
in my opinion, a qbh/qbs system is a system that somehow indexes a melody data base, and then takes singing/humming, i.e. monophonic wav input to search in this database.
A closely related problem is the query by playing, where, if the input is performed on a midi capable instrument, the input to the query system is a midi file.
So now we have two (or if we also allow pv, which we should as we have them, don't we, as input, three) sensible tasks that may be compared. They are namely: 1.) Searching a melody by wav input 2.) Searching a melody by midi input 3.) Searching a melody by pv input.
Now the question of the database/indexing. We have never used anything else than monophonic midis, so I just now realised other folks would maybe like to index from other sources...
For my part, I'm mostly interested in 1.), but would also take part in 2.)
Maybe we should just compile quickly what everybody is expecting of this contest, so may be just fill that form:
-------------------------------------------------------------- | I will take part in query by | midi for indexing is | -------------------------------------------------------------- | name | wav | midi | pv | ok | not ok | -------------------------------------------------------------- | CS | X | X | | X | | -------------------------------------------------------------- | | | | | | | -------------------------------------------------------------- | | | | | | | --------------------------------------------------------------
So, I hope this was not plain stupid and may help clarify issues...
Cheers, Christian
