Closed jonnius closed 3 years ago
Also getting this error using the open service (https://meet.jit.si/), using chrome
Still happens on meet.ji.si, and it is very difficult to keep people from Zoom when this sort of thing is common..
Using pre-join page and there shouldn't be a problem. It needs a gesture or webrtc session before playing it is how Google changed it ... not sure about FF though.
@damencho We have a prejoin page but sometimes on chrome browser on mobile we get this error:
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) @ lib-jitsi-meet.min.js:1
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:10
(anonymous) @ lib-jitsi-meet.min.js:10
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:10
(anonymous) @ lib-jitsi-meet.min.js:10
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:10
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:17
(anonymous) @ lib-jitsi-meet.min.js:17
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:17
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
lang/countries-fa.json?r=1638779169516:1 Failed to load resource: the server responded with a status of 404 ()
[Deprecation] The ScriptProcessorNode is deprecated. Use AudioWorkletNode instead. (https://bit.ly/audio-worklet)
_initializeAudioContext @ lib-jitsi-meet.min.js:1
c @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
When this happens other participants cannot hear the participant audio.
Folks, this issue is really old, please open a new one and provide as much info as you can. Thank you!
Good day, we have a same problem. in a conference of 15 people, one or two people may not be able to hear the others, and the microphone stops working. We use own instanse Jitsi+Rocket.Chat
Hello, just wanted to inform that I'm experiencing this right now. I can't hear 2 of the 7 participants (not counting myself). Everyone can hear me. Safari version 17.0 (19616.1.27.211.1)
@jallamsetty1 ^
Hi @havaeng, can you please share more details? Is this happening on meet.jit.si or on your deployment? Were you able to hear those 2 users in the beginning and then stopped hearing them all of a sudden or did the issue exist from the moment those users unmuted themselves and started speaking? Will you be able to share the full browser console logs for the call when this issue reproduces?
Same issue.
Firefox 128.0 Jitsi stable-9457
no sound and video in Firefox. Chrome works fine.
I got error messages in console:
2024-07-16T08:38:31.726Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>: A potential problem is detected with the audio output for participant 63c60420, local audio levels: [null,null], remote audio levels: undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
2024-07-16T08:38:31.727Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>: A potential problem is detected with the audio output for participant becfffa0, local audio levels: [null,null], remote audio levels: undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
2024-07-16T08:38:31.727Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>: A potential problem is detected with the audio output for participant 3f6da3ec, local audio levels: [null,null], remote audio levels: undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
2024-07-16T08:38:31.727Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>: A potential problem is detected with the audio output for participant e3aee918, local audio levels: [null,null], remote audio levels: undefined
Could someone check that?
CAn you reproduce this consistently? Can you please share the full JS console logs?
@saghul hi, full console log in attachment.
stepps to reproduce:
if im changed browser on google chrome, evrything works fine
The link seems to be broken.
@saghul link fixed
Can you please try with the latest stable? There were some breaking changes with Firefox and DTLS 1.3 that have been addressed recently in the JVB.
yes, I can, but it will take a lot of time. The update process is very slow in my company.
Can you reproduce the issue with older versions of Firefox? If not, then the DTLS change in latest FF is the likely culprit and updating the JVB is the only option then. JVB ICE never got established as per the browser console log so it does seem very likely that its the DTLS issue.
Firefox 125 same. No sound / video. Tested on mac pro (m2) and ubuntu 22.04.
Firefox 125 same. No sound / video. Tested on mac pro (m2) and ubuntu 22.04.
Are you able to reproduce this on meet.jit.si?
meet.jit.si - works fine!
@jallamsetty1 hi! whats version of jvb server and jitsi using meet.jit.si?
That deployment is always a bit ahead of our stable releases, but in your case using the latest stable release should do it.
@saghul thank you. I think the update will solve my problem.
after update on latest stable release - firefox works fine.
Description
Sometimes some participants can't hear some other participants. Some findings:
Current behavior
There is an audio-only meeting with n>7 participants. Some participants cannot hear all other participants, e.g. participant 4 cannot hear participant 3 and 7.
Expected Behavior
Every participant can hear every other participant.
Possible Solution
Steps to reproduce
Start a Jitis Meeting with as many users as possible, only enable Audio and try to speak to each other.
Environment details
Version: jitsi-meet v1.0.4101-1 Browsers tested: Chrome, Firefox on Win10 and Ubuntu 16.04