You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm making a small push to talk application, I'm relying on boardcast to do it. My FE has 2 peer connections 1 sendonly , 1 recvonly. Of course all connections were successful. When a person speaks, they will create a sendonly peer connection and send the track to the server to receive the track on ontrack and write it to localTrack. Listeners when joining to create a peer connection recvonly hear normally.
The error occurred when I switched the speaker to B. Before creating a sendonly connection for B, I closed A's sendonly connection. So the previous peer conenction recvonly could not hear. But peer conenction recvonly then hears normally again. One more important point is that after a few minutes of speaking, the peer connections that were previously unable to hear will be able to hear again.
Your environment.
Version: v4
Browser: chrome
Other Information - reactjs webrtc
What did you do?
I have checked that localTrack is writing data successfully. I checked the stats of the previous peer connections and did not see any change in data bytes.
What did you expect?
I want when changing speakers to write to localtrack, previously connected recvonly peer connections receive the new audio data bytes and hear them.
Thanks.
The text was updated successfully, but these errors were encountered:
https://github.com/pion/webrtc/blob/master/examples/broadcast/main.go
I'm making a small push to talk application, I'm relying on boardcast to do it. My FE has 2 peer connections 1 sendonly , 1 recvonly. Of course all connections were successful. When a person speaks, they will create a sendonly peer connection and send the track to the server to receive the track on ontrack and write it to localTrack. Listeners when joining to create a peer connection recvonly hear normally.
The error occurred when I switched the speaker to B. Before creating a sendonly connection for B, I closed A's sendonly connection. So the previous peer conenction recvonly could not hear. But peer conenction recvonly then hears normally again. One more important point is that after a few minutes of speaking, the peer connections that were previously unable to hear will be able to hear again.
Your environment.
What did you do?
I have checked that localTrack is writing data successfully. I checked the stats of the previous peer connections and did not see any change in data bytes.
What did you expect?
I want when changing speakers to write to localtrack, previously connected recvonly peer connections receive the new audio data bytes and hear them.
Thanks.
The text was updated successfully, but these errors were encountered: