muting local stream seems to stop events from being generated

[fippo]

at least on chrome/linux. on windows, speaking / not speaking events are still generated.
Firefox doesnt seem to generate those events either.

[kashifshamaz21]

@fippo I believe this is a known limitation with webrtc today, i.e, when a media stream is audio or video muted, the local rendering of audio/video from that stream is also stopped.
So, muting the local stream would result in the observation you had: speaking events, volume change etc won't get triggered.
I had asked a similar question around video-mute of local stream on StackOverflow: http://stackoverflow.com/questions/29903265/webrtc-view-self-view-while-muting-outgoing-video-in-a-call/29908474?iemail=1&noredirect=1#29908474

[fippo]

If I recall correctly the problem here was that this was very inconsistent between browsers.

@legastero do you remember more than I do?

[chadfurman]

A nice 2 year old ticket. When you mute the local stream, your browser should stop encoding your local audio. Otherwise, it would exist in the browser even after you think it's muted. Most likely a security thing, would be my guess.

[ibc]

I think there is nothing to do here. If you mute a track (track.enabled = false) it produces nothing no signal. However, if you check the dBs value in "volume_change" event, you'll get interesting things:

Once the track is muted, It starts decreasing from ~ -100 to -Infinity, but it takes some seconds before it reaches -Infinity (well, this depends on the browser: #32).