readyState="muted"

[Xander Dumaine]

Can anyone clarify exactly what causes a remote stream to go readyState="muted" and muted="true"? Is it due to byte count, actively receiving, etc?

For context, we're getting streams from Jitsi with those states on the video track. And due to a chrome bug (cannot find the issue...), when the video track is muted, the audio track won't play. Trying to figure out if we're doing something wrong with jitsi, or if it's doing something wrong...

[Warren McDonald]

Sounds like Jitsi is doing something the browser is not ready for yet. I recently checked on the implementation of remote mute status and it was not supported and low pri in Chrome. Not sure about Firefox. Both sides of the peer connection would have to fully support this before it could be useful.

The support for readystate does not include muted yet or the events attached to the transition.

[Philipp Hancke]

IIRC (and the reproduction I tried confirmed) that means RTCP is received while RTP is not. You should be seeing packet loss from getStats.

2016-06-23 20:36 GMT+02:00 Xander Dumaine <xander....@gmail.com>:

Can anyone clarify exactly what causes a remote stream to go readyState="muted" and muted="true"? Is it due to byte count, actively receiving, etc?

For context, we're getting streams from Jitsi with those states on the video track. And due to a chrome bug (cannot find the issue...), when the video track is muted, the audio track won't play. Trying to figure out if we're doing something wrong with jitsi, or if it's doing something wrong...

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/a382853b-748f-49d3-8193-de86bed1ca26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vuse...@gmail.com]

Did you ever find a solution? I've run into the same issue and I'd appreciate any advice 

[V User]

For posterity, the issue I was having was that I was sending the wrong ssrc-id in my XMPP messages, so what Jitsi was expecting didn't match what was on the RTP packets. The key clue was that in webrtc-internals the connection graph (conn-audio-0) was showing bytes transferred while the audio-recv and video-recv graphs were not seeing any bytes. 

--

---
You received this message because you are subscribed to a topic in the Google Groups "discuss-webrtc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/discuss-webrtc/H9j7tAlIpX4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/3a93f04d-c301-4ce6-9706-67b8fdf781f5%40googlegroups.com.