On Friday, 24 April 2020 12:13:53 BST Jorge Almeida wrote: > On Fri, Apr 24, 2020 at 11:39 AM Michael <[email protected]> wrote: > > Applications can be rather particular regarding bitrate, bit sample > > formats, channel configuration and other options. I understand Firefox > > wants to have 48000Hz or it won't play. So, even if your DAC can do > > 96000Hz, you may need to specify a lower bit rate in the above config. > > > > The mic may also need specifying a particular endianess format and this > > may > > need to be different if you are using some websocket in FF, Vs the discord > > app directly. You could try S32_LE or S16_LE and various bit rates. > > > > The idea being to force alsa to use whatever format and rates the > > application may need/want, rather than passing through whatever the > > hardware is capable of. > > Will keep trying, but I believe the explanation is simple: they > (discord, slack,...) don't care about linux. I found people > complaining about the behaviour of discord even for pulseaudio users. > > thanks > > Jorge
I understand discord also offers a webRTC service, which ought to work with a browser - so it should be down to the browser to communicate with Alsa. Assuming of course the webRTC implementation by discord/slack/et al., broadly follow the standard. The problem with all these proprietary apps is many tend to do their own thing, breaking interoperability on the way.
signature.asc
Description: This is a digitally signed message part.
