-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I2S_SLOT_MODE_STEREO configuration in bsp_i2s_init(.) does not work (AIS-1421) #117
Comments
Ok, digging more, I found out when the AFE config is set to use
calling On the other hand, when changing the AFE config to use
and
the audio chunk size becomes 1024. I believe this is a bug. Regardless of the microphone array settings, in |
Hi @alrostami , it is not a bug. we use different algorithms for 1mic and 2mic. Those algorithms need different context. |
Thanks for your reply @feizi. I am slightly lost in understanding what AFE's feed function expects. I already know that bits per sample must be 16 (or downsample to 16 if i2s is set to more than 16). Does it expect left and right channels no matter
Essentially "The input data should be arranged in the format of channel interleaving. The last channel is reference signal if it has reference data." Could you point out documentation on this or tell me how I can find more information? |
The doc of AFE is here |
I was trying to get the speech recognition examples to work with two MEMS microphones in
I2S_SLOT_MODE_STEREO
mode, but all of the available examples are set to use a single mic inI2S_SLOT_MODE_MONO
mode. I tried it with two INMP441 and wired one as L (grounded the L/R pin) and the other as R (connected L/R pin to VDD). After a few tries, I noticed the i2s_new_channel(.) arguments are hard coded to mono and 16 bits per channel, so I modified it to stereo and set the bit per channel to 16 and the sample rate to 16000. Plus, setting the total channels to 3, the number of microphones to 2, and the number of refs to 1. When I flashed it, the wake word stopped working. I am wondering if this is a bug or it's me who is missing something here.The text was updated successfully, but these errors were encountered: