macOS: Choppy mic audio and routing issues with GoXLR (Telegram vs Telegram Lite comparison) #252
Description
I use Telegram to talk with friends and acquaintances. I am on macOS with an M4 Mac, and I’m experiencing some issues. Here is what I observed during my tests.
First, regarding the microphone: the audio is choppy and cuts out during calls, similar to what you would hear with a network issue. I suspect this might be related to the audio sample rate, possibly because Telegram is using 44 kHz instead of 48 kHz.
Second issue: I believe the audio routing may not be handled correctly. We noticed that if I play a video or any other sound on my system, it sometimes gets picked up by the microphone in Telegram, even though the routing should not send that audio to the mic. My assumption is that Telegram might be reading from multiple channels without properly distinguishing them.
For comparison, I tested another client called Telegram Lite from the App Store, and it works perfectly without any of these issues. Because of that, I wonder if this could be related to CoreAudio handling (I may be mistaken about the exact component).
Another question (I’m not sure if it should be a separate issue): I make music and mainly use Arturia VSTs in standalone mode. In those applications, I can see all audio channels by default, which is great. However, in FL Studio I only see the GoXLR device. I know that I can use Loopback to recreate a similar setup, but I was wondering if it would be possible to make both applications behave the same way regarding channel visibility and routing.