Egress.,. Session: RM_fPaP4hKVE7EK Participant: PA_zREPZGEgUvLJ

For ref, in the dashboard when this happens we notice always 2 microphones published at the same time (when we log publishing on the client we only see 1 published)

the robotic voice, when was the last time this had happened? and what bitrates are you publishing audio with? Typically this correlates with packet loss. We did however find one issue when FF/Safari users publish at high bitrates, there was some packets dropped due to server side RED support that has been fixed as of Sunday.

also we've seen Bluetooth devices behaving this way as well.

I found a few with status`EGRESS_ABORTED` at 7:45, 7:46, and 7:47am PST. Each of these received a StopEgress request within a few seconds of the StartEgress request, and the pipeline hadn’t started yet

We have some recordings (8 people) where the sound quality is really broken. To the point it's no good. However the live conversation was fine. So the EGRESS must have struggled?

The room name affected => 541670e7-c781-4063-bd6d-8610eddaf81f

Actually we have had a few recordings now, where live was fine. But the audio in the recording becomes very broken at points... this is not usable for us.

Can someone help.

It happens usually when there are a few users 8+ in a room

Sorry to load this thread up, but it may also be connected.

We are having issues recently with the recorded output, when we run through mediaconvert (AWS) it drops sections of audio) - ffmpeg seems okay.

Haven't debugged the source yet.

If we convert the output recording to (1 channel) mono audio via ffmpeg it resolves the AWS media convert issue, but obviously not ideal.

This additional issue has only recently started happening, so not sure if something has changed.