2008:Audio Chord Detection - Revision history

Xinglin Zhang: /* Comments/Discussion */

2008-08-27T07:04:08Z

‎Comments/Discussion

JohanPauwels: /* Comments/Discussion */

2008-08-23T11:11:38Z

‎Comments/Discussion

JohanPauwels: /* Comments/Discussion */

2008-08-21T15:17:12Z

‎Comments/Discussion

JohanPauwels: /* Potential Participants */

2008-08-21T13:59:33Z

‎Potential Participants

JohanPauwels: /* Comments/Discussion */

2008-08-21T13:56:56Z

‎Comments/Discussion

Mertbay: /* Submission Format */

2008-08-20T20:20:49Z

‎Submission Format

Mertbay: /* Submission Format */

2008-08-20T20:20:08Z

‎Submission Format

Mertbay: /* Comments/Discussion */

2008-08-20T20:20:03Z

‎Comments/Discussion

Mertbay at 20:14, 20 August 2008

2008-08-20T20:14:11Z

Jawebada at 20:00, 20 August 2008

2008-08-20T20:00:10Z

@@ Line 240: / Line 240: @@
 Additional question:
 It's obvious that all sevenths chords, ninths and higher will be reduced to their triad, but will dim, aug, sus4 and so on all be represented as "24" in the evaluation reference?
 == Trainging Poll ==

@@ Line 238: / Line 238: @@
 Hi all, I'm a first year PhD student at Ghent University and I'm (but mostly will be) focussing on chord and key detection. The contest comes a couple of months too early for me, as I didn't plan to have a completely integrated chord extraction program working at this stage, but I'm busy hacking together some old and new code of our group so that I can jump in at short notice. I have one remark: our program doesn't need any training (since I didn't have time yet to implement it, but it's on the to do list), it just uses parameters derived from musical theory, so no Beatles data were used. I'll submit it to the pre-trained category, since it doesn't need training, but it's more not-trained. To be complete, just the feature extraction step has some optimized parameters (for the pitch tracking) which we set according to our own testset (not containing Beatles), but this wasn't evaluated in the context of chord detection and are supposed to be general parameters anyway (based on common sense mostly). Also, because of time constraints I won't be able to compile for Linux, although it should be perfectly portable C++, but I'll try to use static linking as much as possible (unfortunately, libsndfile's licence for instance prohibites this) and will send a Win32 console app. Lastly, the abstract will probably be ready August 29th the latest. I read in a mail that the sharp deadline is only 5 days before ISMIR, so that should be ok, but can somebody confirm this?
-Additional questions:
+Additional question:
 It's obvious that all sevenths chords, ninths and higher will be reduced to their triad, but will dim, aug, sus4 and so on all be represented as "24" in the evaluation reference?

@@ Line 237: / Line 237: @@
 '''Johan`s comments (August 21, 2008)'''
 Hi all, I'm a first year PhD student at Ghent University and I'm (but mostly will be) focussing on chord and key detection. The contest comes a couple of months too early for me, as I didn't plan to have a completely integrated chord extraction program working at this stage, but I'm busy hacking together some old and new code of our group so that I can jump in at short notice. I have one remark: our program doesn't need any training (since I didn't have time yet to implement it, but it's on the to do list), it just uses parameters derived from musical theory, so no Beatles data were used. I'll submit it to the pre-trained category, since it doesn't need training, but it's more not-trained. To be complete, just the feature extraction step has some optimized parameters (for the pitch tracking) which we set according to our own testset (not containing Beatles), but this wasn't evaluated in the context of chord detection and are supposed to be general parameters anyway (based on common sense mostly). Also, because of time constraints I won't be able to compile for Linux, although it should be perfectly portable C++, but I'll try to use static linking as much as possible (unfortunately, libsndfile's licence for instance prohibites this) and will send a Win32 console app. Lastly, the abstract will probably be ready August 29th the latest. I read in a mail that the sharp deadline is only 5 days before ISMIR, so that should be ok, but can somebody confirm this?
 == Trainging Poll ==

@@ Line 96: / Line 96: @@
 * Juan P. Bello (jpbello@nyu.edu)
 * Kyogu Lee (klee@gracenote.com)
 == Bibliography ==

@@ Line 233: / Line 233: @@
 Thanks for the noting this. Let`s keep everything simple. The ground truth text files for supervised learning will be kept in the same directory. So if there is a file in the train list called "/some/path/file1.wav" there will be a corresponding ground truth file called "/some/path/file1.wav.txt" in the 0-24 integer label format.
 Also the output files should be called "/path/to/output/file1.wav.txt" .
 == Trainging Poll ==

@@ Line 71: / Line 71: @@
 Where fileList.txt has the paths to each wav file. The features extracted on this stage can be stored under "/path/to/scratch/dir"
-The ground truth files for the supervised learning will be in the same path with a ".txt" extension at the end. For example for "/path/to/trainFile1.wav" will have a corresponding ground truth file called "/path/to/trainFile1.wav.txt" .
+The ground truth files for the supervised learning will be in the same path with a ".txt" extension at the end. For example for "/path/to/trainFile1.wav", there will be a corresponding ground truth file called "/path/to/trainFile1.wav.txt" .
 For testing:

@@ Line 70: / Line 70: @@
   ''extractFeaturesAndTrain  "/path/to/trainFileList.txt"  "/path/to/scratch/dir" ''
-Where fileList.txt has the paths to each file in each line. The features extracted on this stage can be stored under "/path/to/scratch/dir"
+Where fileList.txt has the paths to each wav file. The features extracted on this stage can be stored under "/path/to/scratch/dir"
 For testing:

@@ Line 229: / Line 229: @@
 '''Mert`s Comments August 20, 2008'''
-Thanks for the noting this. Let`s keep everything simple. The ground truth text files for supervised learning will be kept in the same directory. So if there is a file in the train list called "/some/path/file1.wav" there will be a corresponding ground truth file called "/some/path/file1.wav.txt".
+Thanks for the noting this. Let`s keep everything simple. The ground truth text files for supervised learning will be kept in the same directory. So if there is a file in the train list called "/some/path/file1.wav" there will be a corresponding ground truth file called "/some/path/file1.wav.txt" in the 0-24 integer label format.
-Also the output should be called "/path/to/output/file1.wav.txt" .
+Also the output files should be called "/path/to/output/file1.wav.txt" .
 == Trainging Poll ==

← Older revision		Revision as of 20:14, 20 August 2008
Line 226:		Line 226:

	Also, when we write an output file, is it to /path/to/output/file1.txt (not /path/to/output/file1.wav.txt)?		Also, when we write an output file, is it to /path/to/output/file1.txt (not /path/to/output/file1.wav.txt)?
		+
		+	'''Mert`s Comments August 20, 2008'''
		+
		+	Thanks for the noting this. Let`s keep everything simple. The ground truth text files for supervised learning will be kept in the same directory. So if there is a file in the train list called "/some/path/file1.wav" there will be a corresponding ground truth file called "/some/path/file1.wav.txt".
		+	Also the output should be called "/path/to/output/file1.wav.txt" .
		+

	== Trainging Poll ==		== Trainging Poll ==

@@ Line 84: / Line 84: @@
 * H.Papadopoulos (papadopo@ircam.fr)
-* Jan Weil (weil@nue.tu-berlin.de)
+* Jan Weil (weil@nue.tu-berlin.de), Jean-Louis Durrieu (durrieu@enst.fr)
 * Markus Mehnert, Gabriel Gatzsche (markus.mehnert@tu-ilmenau.de, gze@idmt.fraunhofer.de)
 * Yuki Uchiyama(uchiyama@hil.t.u-tokyo.ac.jp)