This message was deleted.

this is expected on the iPhone, this is because we are doing an audio mode switch to acquire the microphone. on iOS, if we had acquired the microphone earlier, it would have caused the mic indicator on the device to light up (even if it would be muted). Because of that we are postponing mic acquisition until you really create that local audio track. If you are looking for it to react faster, I would recommend acquiring the microphone yourself ahead of time, perhaps using LocalAudioTrack.create

Interesting, we are acquiring the mic earlier and then using fastConnect to enter the room. Then we just run .setMicrophoneEnabled(false) and it still takes time. But as I said, we might be doing something wrong still. Or are we maybe supposed to use localAudioTrack.mute() for a faster experience?

when you set it to false, we would turn off the recording stack in order to turn off the mic indicator. I believe that's the time-consuming part that you are seeing.

Okay, the reason this might be a problem for us is that when this is happening, all audio in the video call is turned off for the user who mutes/unmutes and then when the process is finished everything is back to normal. But since this process takes a bit of time the user experience isnt optimal

hmm that's unexpected.. so you are unable to hear others when this is happening? does the same thing happen if you called

localAudioTrack.mute

?

Yes, exactly. So its dead silent for the person doing this. My colleagues tested the other way (localAudioTrack.mute()) and it was way faster but nothing got muted. Maybe because it only emits to remote and not local users? And the only extra thing we have changed is the audioAppleConfiguration to videoChat and playAndRecord. Can't remember the exact name on the phone right now. Yes and we are building it to a native app. Everything is superfast on Chrome/web and Android App

@dry-elephant-14928 After the function

setMicrophoneEnabled

has run, all audio settings are reset to speaker. Even if headphones have been selected. There is also an issue where all audio is cut off. So for some devices we have about 500 milliseconds of all participants audio going silence when mute is toggled. Most noticeable on iOS, but all devices have this issue (Chrome, FireFox, Android and iOS).

@wide-shoe-67933 I've filed an issue for this, where the audio gets cut off when this happens. I'm unsure about @salmon-flag-32441's report about all audio is cut off on all devices. Are you saying that this behavior is present in the browser as well? but because it happens quickly, it's hard to notice?

@dry-elephant-14928 Sorry for being unclear, the same issue. This can be reproduced on Android and Chrome, but the cut off is less noticeable.