Local library scan

Welcome to the “new” S2. There are certainly problems with local libraries. Indexing is slower. There are plenty of support articles on downgrading to S1 and/or running split S1/S2 systems. That is the approach I took. All my music playing is on S1 and home theater is on S2. But I kept one pair of Ones on S2 for testing. S2 has come a long way since the May 2024 disaster, but local music library support seems to be lacking attention. That's my opinion anyway.

My local library will not index at all and another member (in the UK) is having the same experience. iOS 26.5.1 iPhone 17.  Something may be afoot at lease with iOS. My android has no issues scanning the local Library. I’m using a Synology 925+.

On Synology too... I have also found the app (Android) to take significantly longer to complete, or at least report completion of, a library (re)index. No idea why - I stick to the desktop app if needed quickly 🤠

I've surrendered, don't even hope for a library fix after all this time and number of posts.

One may happen, be nice if it did.

My library does index, but it is slower when executed from the Sonos app on IOS.  The Windows Sonos app is faster.  Will be unhappy when Sonos dumps the PC app.

I’ve always thought than local library scans were done at the speakers, and not the controller, and as such, subject to CPU speed. Is it possible your controllers are choosing different speakers to run the process, or does it really run on the controller (display only) device?

Wasn't there something about really slow speakers handing the index task off to faster ones? Don't recall any details.

I'd sure try doing the index from my fastest device, would that be my Arc Ultra or a 300?

How do you control which Sonos device is the “Associated Product”?  All my Sonos devices are newer so probably not much difference.  Seems to me the app is  maybe not actually doing a “Scan for new content” which would take a shorter amount of time to complete compared to the scan of a new library of around the same size.  I’ll have to try both the Sonos app on IOS and the Windows Sonos app to see if they take approximately the same amount of time to complete.  Let’s see…. What music do I want to add?

The indexing takes place on a sonos device. The app just tells a device (the associated device) to scan for new music. Which device does the scan is a crap shoot as far as I can tell. The only way to guarantee a specific device does the scan, is to unplug all the others.

I, too, have always been convinced that the speakers, not the controller, will handle the indexing. Thus my confusion new mobile app vs. Windows app performance. 
For the latest 2-3 indexing the associated product in the Windows app (gold) was my Connect (gen 2)(ethernet), which indexed within a minute or so - but in the new mobile app I cannot see which speaker is the associated product. 
My other speakers are a mix of Sonos One gen 1 and gen 2 on SonosNet, plus a Move connected by wifi 

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.

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.

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.

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!

​@Stanley_4 

​@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?

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.