view dsp/chromagram/ChromaProcess.h @ 298:255e431ae3d4

* Key detector: when returning key strengths, use the peak value of the
  three underlying chromagram correlations (from 36-bin chromagram)
  corresponding to each key, instead of the mean.
  Rationale: This is the same method as used when returning the key value,
  and it's nice to have the same results in both returned value and plot.
  The peak performed better than the sum with a simple test set of triads,
  so it seems reasonable to change the plot to match the key output rather
  than the other way around.

* FFT: kiss_fftr returns only the non-conjugate bins, synthesise the rest
  rather than leaving them (perhaps dangerously) undefined.  Fixes an
  uninitialised data error in chromagram that could cause garbage results
  from key detector.

* Constant Q: remove precalculated values again, I reckon they're not
  proving such a good tradeoff.

/* -*- c-basic-offset: 4 indent-tabs-mode: nil -*-  vi:set ts=8 sts=4 sw=4: */

/*
    QM DSP Library

    Centre for Digital Music, Queen Mary, University of London.
    This file copyright 2005-2006 Christian Landone.
    All rights reserved.
*/

#ifndef CHROMAPROCESS_H
#define CHROMAPROCESS_H

#include <vector>

using namespace std;

class ChromaProcess  
{
public:
    void findHistMaxMin( vector<double> hist, double* max, int*maxIdx, double* min, int* minIdx );
    vector <int> mod( vector <int> input, int res );
    vector <int> getPeaks( vector <double> chroma, unsigned int BPO );
    int findChromaBias( vector<double> chromaVector, unsigned int BPO, unsigned int frames );
    ChromaProcess();
    virtual ~ChromaProcess();

};

#endif // !defined(CHROMAPROCESS_H)