Thanks for the reply. I've been using the InputAnalyzer project as a basis for my experimentations with Cinder FFT, as well as using the utility code with that sample for drawing the spectrum data.
I also have adapted the FMOD portion of this AudioAnalyzer sample project (https://forum.libcinder.org/topic/moving-audio-fft-animation) to retrieve the FFT data and draw it with the same utility/drawing code provided with the InputAnalyzer sample (with simple modifications to accomodate a Channel32 float data type (used in the AudioAnalyzer/FMOD sample) vs vector float data (used in the InputAnalyzer sample).
I'm finding the FFT data returned by ci:audio vs the FMOD methods seem quite different as the displays/rendering output for each are different visually, likely due to differing FFT window types, number of bins, window sizes, etc.
I've been playing (and need to do more playing) with the ci:audio FFT options since the FMOD FFT display appears to have a better resolution and detail/granularity for the rendered bins (I can attach a screenshot of the outputs of FMOD and ci:audio projects which will show this better then I can explain if that would help).
I see that there is a cinder::audio::dsp FFT enumeration for the different FFT windowing types but am unsure how to use/set them in a object (I've experimented with this but cannot figure it out); can you provide some insight on this?
My app is an audio differential analyzer which shows the differences between a source input and processed output. Ideally I'd like to use ci:audio methods exclusively, but am curious as to why the FMOD FFT and the ci:audio displays look as different as they do and if there are FFT options you can suggest I look into deeper.