Skip to main content
Enthusiast I
October 28, 2025

Just putting it out there. Hope option for Front speakers happen soon.

  • October 28, 2025
  • 67 replies
  • 1866 views

Like the topic title says, Just putting it out there. Hope option for Front speakers happen soon.

New CEO really seems to finally care about customers wishes and wants. Hopefully this is one first things that comes out very soon.

After this happens, love see DTS;X finally arrive.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

67 replies

Smilja
December 23, 2025

So if the signals aren’t going through your router, and aren’t going out via SonosNet, how exactly are they getting from the Arc to other speakers?

 

In “Station Mode” (WiFi)? By taking advantage of a SonosNet feature called “Direct Routing”. 🤓

»And the world is like an apple whirling silently in space, Like the circles that you find in the windmills of your mind.« (›Windmills Of Your Mind‹ [1967]. Music by Michel Legrand ; English lyrics written by Alan & Marilyn Bergman)
Trending Lyricist II
December 23, 2025

OK….everyone. Let’s not turn this into a one-sided debate with ​@JesterIzDead 😂. If the SonoSequencr works in their setup then all well and good. As far as WiFi is concerned ​@JesterIzDead seems to have no issues. Besides as we all know trying to get people in general to agree on proper network settings is an exercise.

All said until Sonos decides that the configuration suggested in this thread is feasible or even good business sense all discussion is IMO an exercise in futility.

So Happy Holidays everyone and enjoy your Sonos!

I think everyone has done a fine job not straying into ad hominins. I’m fine if the conversation appears a “one-sided debate” with me. The point of a forum is to engage in dialogue and we don’t all have to agree, merely disagree respectfully. I, for one, have gratitude for this thread as I have learned much more than I knew before, and it would seem there may be more to learn, still. I appreciate your attempt at moderation, but I think the conversation’s been just fine.

jgatie
December 23, 2025

Sounds like that only applies to SonosNet, when one device is connected to your router via Ethernet, thus creating a private 5G mesh network for the rest of the devices to connect via. I was unaware of that, so glad we had this conversation! While my Wi-Fi network is not currently stressed, never a bad idea to get traffic off of it when possible.

 

Nope.  The connection between a soundbar/Amp and a sub/surrounds is a direct private connection created between the transmitting device (soundbar/Amp) and the receiving devices (sub/surrounds).  There’s no mesh involved, and the connection exists regardless if you are using Sonosnet.

This connection is required because even if you connect the subs/surrounds via Ethernet, passing through the router still creates too many hops to keep up with the video, and stuttering occurs.  It is only via the direct route private 5 GHz connection can the low latency required for video sync be reliably sustained. 

Even with this connection, the buffer used is on the razor’s edge of being detectable by those sensitive to lip sync errors, which makes adding the bandwidth for two full channel front speakers to the already strained connection that much more difficult.

Trending Lyricist II
December 23, 2025

Sounds like that only applies to SonosNet, when one device is connected to your router via Ethernet, thus creating a private 5G mesh network for the rest of the devices to connect via. I was unaware of that, so glad we had this conversation! While my Wi-Fi network is not currently stressed, never a bad idea to get traffic off of it when possible.

 

Nope.  The connection between a soundbar/Amp and a sub/surrounds is a direct private connection created between the transmitting device (soundbar/Amp) and the receiving devices (sub/surrounds).  There’s no mesh involved, and the connection exists regardless if you are using Sonosnet.

This connection is required because even if you connect the subs/surrounds via Ethernet, passing through the router still creates too many hops to keep up with the video, and stuttering occurs.  It is only via the direct route private 5 GHz connection can the low latency required for video sync be reliably sustained. 

Even with this connection, the buffer used is on the razor’s edge of being detectable by those sensitive to lip sync errors, which makes adding the bandwidth for two full channel front speakers to the already strained connection that much more difficult.

Thank you! That helped me configure a good query to AI that got me additional clarification on that. I have to admit, though, I’m a little disappointed you didn’t take an opportunity to make a “tester” joke ;)

jgatie
December 23, 2025

Thank you! That helped me configure a good query to AI that got me additional clarification on that. I have to admit, though, I’m a little disappointed you didn’t take an opportunity to make a “tester” joke ;)

 

Never bought into the adversarial relationship between development and testing, not on my side at least.  I had a tyrant of a boss who tried to foster that type of relationship, but he never really succeeded because he was the product of the Peter Principle and we mostly ignored him. 

By the way, it’s come a long way, but AI when it comes to Sonos is still more wrong than right.  It only has existing info to scrub and most of that existing info is garbage.  

Enthusiast II
December 23, 2025

​@JesterIzDead if you are looking for more discussion on similar topic 

 

https://www.reddit.com/r/sonos/s/qxKQwRdwab

 

https://www.reddit.com/r/sonos/s/V0maAuVLSl

 

 

Airgetlam
December 23, 2025

Despite our best attempts ;)

Bruce