Incoming bluetooth data rate #366
-
I have written the following function in my ad2f application:
When I run the sketch the read_data_stream callback prints the following output: fft interval = 4 I am trying to understand what this means. The sketch reports a bluetooth sample rate of 44100 which I expect, but the interval between data packets as reported by the read_data_stream callback indicates a packet length of 5632 bytes with an update rate of 4 ms. I am assuming that each sample takes up 4 bytes (2 channels of 16 bit data each). So that the data array consists of 1408 data samples. But this doesn't appear to make sense in that by receiving 1408 samples every four milliseconds this equates to 352000 samples per second instead of the 44100 samples per second I would expect. I was hoping that someone could enlighten me about where I am going wrong in my understanding. Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
A2DP sends the data as fast as possible: It just gets throttled when you output the data e.g. to I2S. Since you don't throttle the speed anywere you get this crazy rates! If you want to do FFT I suggest to use my AudioTools library: here is a simple fft example |
Beta Was this translation helpful? Give feedback.
A2DP sends the data as fast as possible: It just gets throttled when you output the data e.g. to I2S. Since you don't throttle the speed anywere you get this crazy rates!
If you want to do FFT I suggest to use my AudioTools library: here is a simple fft example