Davidelvig
Well-known member
I've seen this from time to time in my app - and have rearranged code... related to timing and delays...
It has subsequently returned true.
Now it's persistently false, again, and I can't see why.
The code is long, and I could try to simplify, but...
1) What is (available() = false) telling me literally?
2) How are collisions (or overlaps) handled between interrupt-driven-FFT-bin-filling and concommittant calls to AudioAnalyzeFFT1024.read()?
Thanks for your help!
Dave
It has subsequently returned true.
Now it's persistently false, again, and I can't see why.
The code is long, and I could try to simplify, but...
1) What is (available() = false) telling me literally?
2) How are collisions (or overlaps) handled between interrupt-driven-FFT-bin-filling and concommittant calls to AudioAnalyzeFFT1024.read()?
Thanks for your help!
Dave
Last edited: