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
We can probably use "devicechange". This is useful, because changing the device can have problematic performance issue, because the block size, latency and channel count can change.
The text was updated successfully, but these errors were encountered:
This would be fired when the underlying device changes, not necessarily in reaction to setSinkId(...); having been called on the AudioContext.
It might be possible to reuse the even "sinkchange". It might be desirable to be able to distinguish a sink change because of setSinkId(...) and something external though, we need to think about it.
@padenot suggested that there might be a tricky case where setSinkId() user call could happen almost at the same time of user plugging out an audio device from the system. We need to think about the order of events and how to handle this case properly.
We can probably use
"devicechange"
. This is useful, because changing the device can have problematic performance issue, because the block size, latency and channel count can change.The text was updated successfully, but these errors were encountered: