Web Audio API Policy affecting sound playback?


Is Jitsi meet impacted by this: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio?

I had this in my js console, I have users struggling to get audio some times…

[modules/browser/BrowserCapabilities.js] <new u>:  This appears to be chrome, ver: 71.0
LocalStatsCollector.js:22 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
(anonymous) @ LocalStatsCollector.js:22


So since the beginning of the month I’ve been having problems with audio randomly not playing in chrome. My general setup is a webcast with one user speaking and playing video, and the others muted and listening / watching. Listeners who join before the presenter joins hear the audio fine, but those that join after do not - if they are using chrome. Firefox is not affected. I was just wondering if the web audio api policy was the reason for this and if so what the work around is.


chrome://flags/#autoplay-policy - set to ‘No user gesture is required’


I don’t think this is the problem.
It can be the problem sometimes to not hear some sound (joining sound), but the webrtc part, is not affected. For me it is more the latest chrome update, we had few reports for such behaviour, losing media/audio in the middle of a call (after offer-answer, which is done on people joining/leaving). We will be investigating this in the following weeks. If you have a 100% reproducible scenario this will help us a lot identify the issue.


I’ve just spent the whole day trying to work out why audio on chrome was not working - changing the autoplay-policy appears to have fixed it.


Thanks for confirmation, maybe its a different issue than the one I was thinking.


Hi damencho. There’s a further chrome issue now. For many users the player starts muted (50% of chrome users on my conferences have experienced this). You have to right click on the play, select ‘Show controls’ then try to unmute the sound using the button that now appears in the same place as the Jitsi player task bar. Or install a chrome extension such as this: https://chrome.google.com/webstore/detail/volume-control-volume-boo/lhhgpflelfbhnihnbjigpgdbahgkbghp/related?hl=en

I think both these issues mean that more audio management needs to be built into the player so this works out of the box on Chrome.


Is this on meet.jit.si or on a custom deployment? If it is a custom deployment, do you have any jitsi-meet modifications, other than branding?