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
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context
What did you do?
What did you expect?
that ontrack event on addTranceiver side fires as intend
What happened?
when i do the following code in ontrack event
e.transceiver.direction = "sendrecv";
e.transceiver.sender
.replaceTrack(localStream.getAudioTracks()[0])
this doesn't trigger ontrack event in yourConn side the caller
there is nothing received in the other side yourConn also that mean yourConn seem to not triggerd there
yourConn2.ontrack = (e) => {
remoteVideo = document.getElementById("wbrtcremote");
transceiversRemotePeer = new MediaStream([
e.transceiver.receiver.track,
]);
remoteVideo.srcObject = transceiversRemotePeer;
console.log(
`kind of this track that has arrived to remote peer is ${e.transceiver.receiver.track.kind}`
);
console.log("transceiversRemotePeer.receiver.track.onunmute");
// remoteVideo.srcObject = e.streams[0].getAudioTracks()[0];
//send backTrack
e.transceiver.direction = "sendrecv";
e.transceiver.sender
.replaceTrack(localStream.getAudioTracks()[0])
.then(() => {
//check Tranciever
let senderList = yourConn2.getSenders();
let recieverList = yourConn2.getReceivers();
console.log("recieverList in remotepeer is ", recieverList);
console.log("senderList in remotepeer is ", senderList);
console.log("Track replaced on transceiver's sender");
console.log(
"current direction in remotPeer after changing it is ",
e.transceiver.direction
);
});
};
but with addTrack used it's triggers theres on yourConn side yourConn2.addTrack(localStream.getAudioTracks()[0]);
configuration code for yourConn side to send and receive is :
yourConn after the call is done or connection is established just as fine
yourConn (the caller ) can send audio but not recieve
yourConn2 (the calle) can receive audio but can't send
ontrack event for yourConn => not triggered
ontrack event for yourConn2 => triggered
The text was updated successfully, but these errors were encountered:
Your environment.
What did you do?
What did you expect?
that ontrack event on addTranceiver side fires as intend
What happened?
when i do the following code in ontrack event
e.transceiver.direction = "sendrecv";
e.transceiver.sender
.replaceTrack(localStream.getAudioTracks()[0])
this doesn't trigger ontrack event in yourConn side the caller
there is nothing received in the other side yourConn also that mean yourConn seem to not triggerd there
but with addTrack used it's triggers theres on yourConn side
yourConn2.addTrack(localStream.getAudioTracks()[0]);
configuration code for yourConn side to send and receive is :
behavior that happend with modified transceiver
yourConn after the call is done or connection is established just as fine
yourConn (the caller ) can send audio but not recieve
yourConn2 (the calle) can receive audio but can't send
ontrack event for yourConn => not triggered
ontrack event for yourConn2 => triggered
The text was updated successfully, but these errors were encountered: