Closed thegeminisociety closed 3 years ago
I think last i checked Safari still hasn't implemented a key component of the AnalyserNode which is used in the FFT class which might be why the values are so different. I think until Safari implements the full spec, there isn't anything we can do about it.
I am reading a buffers FFT values using the analyser and notice that I am getting slightly different values across browsers (chrome vs safari). Is this expected? Is there a way to somehow normalize this? Thanks