Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mute/unmute event on subscription not fired when muting audio #513

Open
philipgiuliani opened this issue Jun 29, 2021 · 1 comment · May be fixed by #515
Open

Mute/unmute event on subscription not fired when muting audio #513

philipgiuliani opened this issue Jun 29, 2021 · 1 comment · May be fixed by #515

Comments

@philipgiuliani
Copy link
Contributor

For debugging purposes, I have currently added the following subscriptions:

subscription.addEventListener("mute", console.debug);
subscription.addEventListener("unmute", console.debug);

subscription.stream.getAudioTracks().forEach((t) => {
    t.addEventListener("mute", console.debug);
    t.addEventListener("unmute", console.debug);
})

subscription.stream.getVideoTracks().forEach((t) => {
    t.addEventListener("mute", console.debug);
    t.addEventListener("unmute", console.debug);
})

When muting the audio channel, the subscription's event listener is never fired. We have also tried to mute the stream with the OWT Management API. We always have the same result. Muting video works, muting audio doesn't.

// subscription's listeners are called
this.publication.mute(Owt.Base.TrackKind.VIDEO);

// subscription's listeners are not called
this.publication.mute(Owt.Base.TrackKind.AUDIO);
@philipgiuliani
Copy link
Contributor Author

I also opened it in owt-server because I think it actually belongs there: open-webrtc-toolkit/owt-server#1037

Feel free to close this one.

@philipgiuliani philipgiuliani linked a pull request Jul 23, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant