Sonos app on Mac

The Sonos interface IMO has gone through three (3) upgrade phases:

S1 > S2 > Sonos App

The latter two incarnations IMO having crossover features besides the fact that users never really adopted the moniker of Sonos App and continued to refer to it as S2.

Sonos is also culpable in the confusion as when one goes into “About Your System” it reads as S2 and not Sonos App.

As far as term “legacy” is concerned to my understanding it only refers to devices that cannot operate on the S2 (Sonos App) controller/Firmware. Furthermore I believe it has to do with memory capacity as well as system architecture that requires more efficient/powerful processors.

Edit:

Maybe some day the app may be called Sonos (App) Ultra 😂😂😂

Somehow I feel like the marketing types are actively working to make it difficult to search for Sonos answers with their naming choices. The "why?" behind their choices would be an interesting story.

The problem with that is: 

System/firmware release notes say this for S2 systems:

And I can find no mention of devices not able to run S2 being called “Legacy”.

We've implemented a new software management strategy that allows us to deliver new features and innovations to our modern Sonos players while continuing to support our older S2 "legacy" devices with essential updates.

Legacy Product Update

And of course, all that leads to the question: Why did they call the S1 Controller update in the OP “Legacy”?

Naming conventions sometimes rise to the most absurd levels.  I once was developing a process to export bar codes to a 3rd party vendor for incorporation into a promotional app.  Like most competent engineers would, I designed it to allow for multiple third party vendors, chosen via a drop down.   The 3rd party's execs flipped out, thinking they were being generic-ised due to the drop down selection being labeled as their company name (yeah, I didn't understand it either).  So I had to label the drop down as something generic, while keeping the internal parameters and output file company specific, all in order to not generic-ise their company's role in the project.

As I said, an absurd level.

It makes sense to me. As I read it Sonos is saying that some products that are S1 and S2 compatible may no longer receive updates to new features that require Sonos App compatibility based upon memory (Click the link you provided). 

In the diagram below I’ve crossed out products that are still S1 and S2 compatible which will continue to receive additional Sonos App feature/updates. For how long only Sonos knows. 🤔 The remaining products will not receive Sonos App feature/updates. * JMHO

 * I manually added Connect and Connect: Amp to match the link Legacy Product Update 

Based on device firmware versions:

S1: v57.x will never get to v58 (as that is already used for S2)

S2 “legacy”: v86.x with room to get to v89.x if desired

S2 “not-legacy”: v96.x and likely to increment way past that

The v96+ capable devices are really S3, getting new features and the like, but compatible with S2 legacy devices (unlike the S1/S2 split).

I remember I’m here in this thread earlier on. I was having trouble with having my bedroom legacy Sonos speaker play my Mixcloud uploads, as well as also my newer cellar/office Sonos speaker. Both of which needed separate Mac desktop controllers to operate, or at least to set up queues. I had to get with support who managed set me up okay—after quite a bit of effort. Today maybe things might go easier.

It was later that I discovered I was able to add all my 5000+ hourlong Mixcloud uploads randomized onto both queues separately and have them play at the touch of a button. Something I don’t know how I could do with any other system.

All I’m saying now is I’m quite happy with how my older and newer Sonos devices are working okay.

Here’s how I see it… There are only 2 controllers. S1 and S2. There are only two systems, S1 & S2. The S2 system now has older devices that are considered S2 Legacy with it’s own firmware branch.. The S2 legacy devices still use the S2 controllers and are S2 systems.

Those S2 legacy devices are not OLD S2, they got updated in the big May 2024 UPDATE. They are running the current S2 API etc. So they are S2.