Closed rykkers closed 2 months ago
This is expected, as the current default playback for remote tracks is via WebAudio.
There are APIs today that you can use to change volume (e.g. publication.setVolume
).
That said, we're currently planning to change the default setting to not use WebAudio in this PR which also outlines some of the reasoning.
For a quick fix for you, just set webAudioMix: false
in your room options
Ok, that's amazing thanks.
Also a reminder for myself to also look at PRs before raising an issue. Although i'm used to most PRs being attached to an "Open" issue.
Keep up the good work!
Describe the bug
Expected: Receive remote audio track, attach it using track.attach(), then use the returned audio element to be able to alter sound output e.g. volume, muting, sinkId etc.
Actual: No matter what i do with that audio element (even delete it), the audio continues to play. It's clearly being played through another audio element that hasn't been added to the DOM.
If this is a known 'feature' i'd recommend that it's added to the docs, as currently you're encouraged to add this new DOM element to the page, which is essentially useless.
Reproduction
I can reproduce on the demo app (https://meet.livekit.io/)
audioElem = document.getElementsByClassName("lk-participant-media-audio")[0];
audioElem.muted
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
No response