Issue with Speaker Device Selection on Windows OS

[beaubuehler]

We’ve identified an issue with the Browser SDK on Windows devices regarding speaker device selection. Here’s what we’ve observed:

Steps Taken:

• We set the speaker device using:
  state.device.audio.speakerDevices.set(deviceId)
• After a delay of a few seconds, we log the selected device using:
  state.device.audio.speakerDevices.get()

Expected Behavior:

• Audio should play through the selected device (deviceId).

Observed Behavior:

• The correct deviceId is reflected in the logs.
• However, audio consistently plays through the Windows OS default output device.

Additional Details:

• This issue occurs only on Windows and not on Mac (tested on Google Chrome).
• We confirmed that useDefaultAudioDevice is set to false.
• Changing the default output device in Windows OS is the only way to redirect audio.

We’ve spent significant time ensuring our implementation is correct and it aligns with SDK usage guidelines. Since the SDK reflects the correct device but fails to route audio appropriately, we suspect this might be an SDK-related issue.

This is a critical issue that is significantly affecting our users. Could you confirm whether this is a known bug or if we might be overlooking something in our implementation?

We have tried the same thing on Google Meet and it does route the audio through the selected output device even if it is different from the default in Windows OS, so it should be something that is supported by our browser, web RTC, and/or our operating system.