comparison tests/TestChromagram.cpp @ 467:1db23b9a8da4

Fix mismatch between time- and frequency-domain versions of the
chromagram process method - the frequency-domain one expects fftshifted
input and the kernel is set up for that, but the time-domain one wasn't
doing it

 vector<double> generateSinusoid(double frequency,
                                 double sampleRate,
                                 int length)
 {
     vector<double> buffer;
-    buffer.reserve(length);
     for (int i = 0; i < length; ++i) {
         buffer.push_back(sin((i * M_PI * 2.0 * frequency) / sampleRate));
     }
-
     return buffer;
 }
 
 double frequencyForPitch(int midiPitch, double concertA)
 {

 }
 
 BOOST_AUTO_TEST_CASE(sinusoid_12tET)
 {
     double concertA = 440.0;
-    double sampleRate = 44100;
+    double sampleRate = 44100.0;
     int bpo = 60;
 
     ChromaConfig config {
         sampleRate,
         frequencyForPitch(36, concertA),

              << expectedPeakBin << endl;
         
         vector<double> signal = generateSinusoid(frequency,
                                                  sampleRate,
                                                  blockSize);
-        
+
         double *output = chroma.process(signal.data());
 
         int peakBin = -1;
         double peakValue = 0.0;
 

              << (peakBin+1 < bpo ? output[peakBin+1] : output[0])
              << ")" << endl;
 
         if (peakBin != expectedPeakBin) {
             cout << "NOTE: peak bin " << peakBin << " does not match expected " << expectedPeakBin << endl;
+            cout << "bin values are: ";
+            for (int i = 0; i < bpo; ++i) {
+                cout << i << ": " << output[i] << "   ";
+            }
+            cout << endl;
         }
     }
 }
 
 BOOST_AUTO_TEST_SUITE_END()