No.  The index is copied to every player on the system.  If your library is less than 65,000 tracks but still hitting the limit, you can free up more space by decreasing your tag/filename/path lengths.  Long tags and filename/paths will use up additional indices to store the overflow, making the actual max number of tracks less than 65,00. 

If you submit a diagnostic and call Sonos they can give you the status of your internal storage (we users can't see it) and you can use that to work out a solution.

If it is tag space, not track count:

Something I've done is keep a master copy of my music with all the original tags, then made a copy and edited tags to make them work better with Sonos. 

Remove the master from your Music Library and add the modified copy there followed by a manual reindex.

While I don’t think that you could build a Playlist this large if you have any very old units in your system, because old units have less memory, but here is a large playlist that I’ve loaded into the Queue. I kept metadata trimmed for these tracks.

Thank you all for your comments. 

I will start trimming the metadata.  Although this will be a long job it seems like the best solution until Sonos develops a relationship with a 'Plex like' supplier that works well with Classical Music.

BTW, it is not a play list I'm working with but rather my entire music collection!

Buzz, you mention old components v new components in terns of memory capacity, so what is the track capacity of the Sonos Port?

The design limit for the library is 65,000 tracks, but the amount of memory actually required for the index depends on the library metadata. Long file names, track titles, artist names, etc. might exhaust the allocated space before reaching 65,000 tracks. Then there is the space required for Playlists and the Queue. Older players have less memory.

I’ve seen reports of users reaching a Queue or Playlist limit at a few thousand tracks. As you can see, this has not been my experience when using recent players.

There is a PORT in my system.

Thanks. I've started deleting meta data but Classical Music inherently has more and having two or more recordings of the same work by different performers doesn't help!

This is close to the limit for my system and library

 I started building the Queue with a 60,000 track playlist.

A block of library index storage is allocated for a track. Additional blocks are used for a track if its metadata overflows the allocation. The maximum number of blocks is 65,000.

At one point I caught a ripper inserting the whole first stanza of an opera track into its track name and most of it into the file name. In my opinion this is excessive.

Not sure how well it works for Classical but you could try upload some files in iBroadcast.com then add that to your Sonos system and see how well it works for you.

A good automatic/mass tag editor can be a huge time saver, one should allow you to clear a tag or multiple tags in one passof your library.

Which OS do you use so folks can suggest ones thye like.0

The track and data limits have long been a disappointment - particularly for collections involving a large proportion of classical tracks.

I tried the Sonos version of Plex, which was very limited - nothing like the full Plex functionality. As mentioned above, there’s also the option to hack out large chunks of metadata - but then you end up with two large datasets to maintain - the Sonos one not much use for anything else.

Personally, I no longer regard Sonos as a suitable option into the future, so keep a sub-set of music maxing out the Sonos limits and also keep a seperate full set of music. This can be accessed via a casting program to chromecast compatible devices (CCA into line-in to a Play 5 and an AV receiver in another room).

If/when I come to a decision for the future, at least I’ll still have the main data set available and can just drop the smaller Sonos one.