Hi everyone, I’m having an issue with my web-based Morse code tone generator when listening through Sonos headphones and wanted to see if anyone here has experienced something similar. The website generates real-time audio tones in the browser using the Web Audio API. On standard wired headphones connected directly to my PC, everything works perfectly. However, when routing audio through Sonos (either via Bluetooth connection or through a Sonos device using line-in), I’m experiencing noticeable delay and, in some cases, complete silence after a few seconds.
The main problem is latency. Morse code timing is very sensitive, and even small delays between dots and dashes make it hard to use for practice. With Sonos headphones, there seems to be a buffering delay that shifts the timing, even though the visual output on the site remains accurate. Occasionally, the audio starts correctly but then cuts out while the browser still shows the signal playing.
For context, I’ve tested this in Chrome and Edge, and CPU usage is low. The issue only appears when the output is routed through the Sonos ecosystem. I understand Sonos prioritizes synchronized multi-room playback, but I’m wondering if there are recommended settings (e.g., disabling audio compression, adjusting line-in delay, or specific Bluetooth configurations) that could reduce latency for real-time web audio.
Has anyone here successfully used Sonos headphones or speakers for low-latency browser-based audio applications? Any guidance on optimizing settings for real-time tone playback would be greatly appreciated.
