Speaker device changes after tabbing away and back?

[bioshazard]

Even in the demo on all my devices I see this behavior: join, change audio device, ctrl-tab away and back and you see the speaker device has changed?? I am the only one seeing this?

just join in on https://demo.realtime.cloudflare.com/meeting?demo=Default

Happens with Brave and Edge and Chrome on Mac and Windows for me :(

[bioshazard]

I think I might have worked around it in my app w/ Codex. Here was the writeup:

2025-10-27 – RealtimeKit Speaker Output Reset Investigation

• Observation: Navigating away from /eg-rtkui and back produces a fresh meeting instance with a new participant ID (see [cycle-compare] logs), so the control bar remounts new media elements and loses any previously selected speaker sink.
• Evidence: Instrumented the embed to compare meeting object references and log join metadata before/after a navigation cycle; initialMeetingEqualsCurrent is false and only the participant ID changes, confirming a forced reconnect.
• Plan: Persist the selected speaker sink ID (via meeting.self.setDevice('speaker', …) interception + localStorage) and reapply it whenever the meeting becomes ready or the tab regains focus. Also, guard the hook’s roomLeft handler so transient disconnect states still trigger the sink reapply step.

[bioshazard]

But that isn't expected right? Anyone else seeing this behavior?

[ravindra-cloudflare]

Hi bioshazard,

We have noted down the bug. We will fix it in upcoming releases.

[bioshazard]

@ravindra-cloudflare FWIW, LiveKit Meet example does NOT attempt to set speaker device and defers to system device.

[ravindra-cloudflare]

Hi @bioshazard

We have rolled out the device selection & speaker switch fixes in latest SDKs. https://developers.cloudflare.com/realtime/realtimekit/release-notes/#2025-12-17.