Local library scan

Forum|Forum|3 months ago
June 28, 2026
20 replies
263 views

Hi

Since 2013 I have been a happy Sonos user - until the amateurish app update May 2024.

Luckily I had automatic AppStore and Sonos system updates switched off by then and have managed to stay on the S2 app (gold), which for me worked perfectly.

However, last week, in my naivety I took the plunge and upgraded my app + system to latest versions.

Now indexing my local library (living on a Synology NAS) takes forever - if it works at all. If I use the Windows app (gold), it works like a charm - as fast as the older S2 (gold) app used to.

Since 2013 I never had an issue indexing my local library, but that seems to have been destroyed by the new app/system updates.

Does anybody experince the same when local library indexing, and can anybody explain why this is happening?

I could downgrade to S1 as all my speakers are S1 compatible - but then I’d have to remain from buying new Sonos units as they will not be compatible with S1, to avoid 2 systems.

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.

Show previous replies

Stanley_4

Grand Maestro

I don't know how to tell which one is doing the indexing, but what I have done when time matters is select a newer device in the app before starting the index off.

Only really old ones are a Pair of Play 3s that are normally unplugged. Gen 1 Beams and Ones are all the newer old ones left here.

MoPac

Headliner III

I use the orange Sonos app on an old iPhone to see which is the “Associated Product”.

@Stanley_4: So you have found if you first select a speaker in the Sonos app that one becomes the one that does the index? I’ll have to try that.

Stanley_4

Grand Maestro

I think that is what happens, couldn't access the internal Sonos data to be sure.

If it wasn't 105 F in the garage I might be tempted to fire up a Play 3 and time it against my Arc.

Might also be worth checking my NAS logs to see if I can tell which Sonos is pulling data for the indexing. A task for another day.

bockersjv

Local Superstar

I may be the odd one out here! Have Synology NAS DS220plus. Zero Sync problems on S2.

I did have issues in the past with missing albums but resolved by directing sync to empty folder then back to Music Library Folder.
I did set up a dedicated SONOS user with password as I could not get Sync to work otherwise.
Sync time is fine but I do always sync from my Windows 11 machine on the Sonos desktop app.
Oldest speakers are Sonos Ones

Not sure if any of the above is relevant but just in case it may help!

User117655

Prodigy II

@Stanley_4

I don't know how to tell which one is doing the indexing, but what I have done when time matters is select a newer device in the app before starting the index off.

@MoPac I have not found speaker use/selection to have any consistent impact whatsoever on the associated product speaker... Not so say it doesn't though I have not observed it using the current/last speaker that was in use.

I would tend to think the apparent differing performance times is more down to reporting/synchronisation with the device apps (new infrastructure) vs. the older desktop apps using local implementation... maybe?

Stanley_4

Grand Maestro

If you look at the specifications of older and current devices you will see a big difference in compute performance as well as huge differences in free memory needed for faster sorting. The S1 S2 split was all about limited internal resources blocking added features. Even just looking at S2 compatible devices there are big differences. You can see that Sonos acknowledged this in S2 by the legacy split of the firmware where less capable devices are not asked to run functions beyond their ability.

kdowling

How is it that a scan for new music here takes less than 2 minutes on S1 and takes almost 20 minutes on S2. Both using the same share on a Synology DS225+. I don’t think sonos device specs can explain that. S2 is terrible with local Music Libraries compared to S1.

They need to find the developer that wrote that code in S1 and rehire him/her to completely rewrite S2 Music Library support. Feature request 😀

AjTrek1

If you think that’s strange….

Earlier in this thread I indicated that I could not scan my library on my iPhone 17 the same as another member mentioned. Today I discovered that I still can’t observe if a scan is happening on my iPhone 17 (meaning the spinning circle doesn’t appear at the top).

Unlike some I also have an android tablet for testing. Just for curiosity I decided to open my android tablet right after requesting the scan on my iPhone…much to my surprise the scan was active as I could see the spinning circle.

So is it to say…start the scan on my iPhone and open my android tablet to see it working??? That’s not good. Something’s not right.

Together Everyone Achieves More = T.E.A.M.

kdowling

Yes, not seeing that the scan started or is in progress on the mobile iOS S2 controller app has been the case for a least a couple updates. I never relied on that being accurate anyway. I can watch the lights on my NAS to see that it has started and when it finishes.

User117655

Prodigy II

Yes, not seeing that the scan started or is in progress on the mobile iOS S2 controller app has been the case for a least a couple updates. I never relied on that being accurate anyway. I can watch the lights on my NAS to see that it has started and when it finishes.

Sounds like around the time they fixed it on Android they broke it on iOS - a feature swap 😱 😂

Sign up

Login to the community