morgane8191

I am trying to use the zsa.mfcc~ object but I have some questions.

First, I use the easy_mfcc abstraction and whatever the FFT window size and overlap factor I specify, I got the same numbers of lists at the output. I mean my signal is around 2.36s, the FFT window size is 1024 with an overlap factor of 2 so I should obtain a list of coefficients every 512 samples (11.6ms) (right?), so at the end of the signal around 200 lists of coefficients (sorry for the imprecision) but I got only 105. And I got those 105 lists whatever the window size and overlap factor!

The second question is how to store efficiently those output lists? Because as soon as there is a signal in input (I mean as soon as the adc is on) there is a list in output but I would like to detect a bang or something each time the values into the list are changing. For now I collect everything in a text object, the problem is I continue storing the same list again and again once my signal ends and same before the signal starts.

Hi there!
I am trying to use the zsa.mfcc~ object but I have some questions.
First, I use the easy_mfcc abstraction and whatever the FFT window size and overlap factor I specify, I got the same numbers of lists at the output. I mean my signal is around 2.36s, the FFT window size is 1024 with an overlap factor of 2 so I should obtain a list of coefficients every 512 samples (11.6ms) (right?), so at the end of the signal around 200 lists of coefficients (sorry for the imprecision) but I got only 105. And I got those 105 lists whatever the window size and overlap factor!

The second question is how to store efficiently those output lists? Because as soon as there is a signal in input (I mean as soon as the adc is on) there is a list in output but I would like to detect a bang or something each time the values into the list are changing. For now I collect everything in a text object, the problem is I continue storing the same list again and again once my signal ends and same before the signal starts.


zsa-mfcc-problems

In the help file, with scheduler in audio interrupt on (in the Audio Status), I get a fixed 5.80 ms which corresponds to the window size divided by the overlap. If scheduler overdrive off and scheduler in audio interrupt disabled the timing won't be synchronized with the DSP calculation.

You can't disable the output at the moment, I'll add this as a feature request. In the meantime you can disable the object by using the enable message (enable 0 will disable the dsp and output of the object).

zsa.mfcc~ problems