Avid Contributor I

dlna client absent on SONOS

16 replies
520 views
Translate All

Instead of giving SONOS a DLNA client, SONOS persists in the crazy notion of making each and every speaker a DLNA service (renderer) and placing the index to the actual music files on each and every speaker.

The result is that, as the memory of most SONOS devices is stuffed to the brim with the oversized SONOS S2 OS, they cannot index more than about 7Gb of music library. Therefore the SONOS music library feature is useless for me as my music SAMBA share is around 42Gb.

Notabene, the much smaller SONOS S1 OS allowed the indexing of the SAMBA 42Gb music share

I invite all who have similar problems to join in complaining to the ceo@sonos.com email account to ask for a DLNA CLIENT to be added to the SONOS S2 (S3?) controllers while simultaneously removing the unnecessary DLNA servers on the old and new speakers - in SONOS S2 (S3?)

As far as I know, the hardware memory is impossible to increase without breaking open the speakers - even if the OS could address more memory.

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

jgatie

After a System Update to Version: 16.5 (build 82259204) yesterday,

with my mix of PLAY1 (A101/A200), CONNECT (D102) and SONOS one (A300/A201) speakers,

WITHOUT any action to add the shared folder on my part
while it previously only gave “the music library is not reachable” errors.

SONOS S2 has today indexed the entire music library 44.0 GB (47,275,733,146 bytes), 7,737 Files, 586 Folders, size on disk 48.2 GB (51,853,131,776 bytes),

The music folder is on a SAMBA share of the SAMSUNG PSSD T7 (SSD) USB3 attached to the ASUS XT8 mesh router ---

strangely the controller apps must have had some memory of the place where the music folder was.

HOWEVER the playlist queue is behaving very strangely -

Whereas it accepts some of the folders to be added to the end of the queue, with other folders, just offers “Pin Collection to Home”
At times it jumps from one song to the next!
Also, at times it just says “something went wrong”

So it looks like a work in progress

Why do you keep repeating this post?

Translate

A

Albert_8Author

Avid Contributor I

Nonsense. The S2 music share capacity is the same as S1. 65,000 maximum tracks, which will be reduced by large tag strings or large file/path names because tags or paths over the max length will take up another index in the hash.

Also, the total size of the files matters not, it’s the number of files and the size of the tags and pathnames that determine the number of files that can be indexed, and that index size is fixed, not variable.

the memory of sonos speakers varies tremendously (https://www.reddit.com/r/sonos/comments/dip1pb/sonos_hardware_memory_chart/?rdt=37694) -

Translate

jgatie

the memory of sonos speakers varies tremendously (https://www.reddit.com/r/sonos/comments/dip1pb/sonos_hardware_memory_chart/?rdt=37694) -

So what? The static memory dedicated to the hash array for the local library is the same, so the total overall memory could be infinite and it wouldn’t change a thing. You are wrong about DLNA having anything to do with the local library capacity. Accept that and try to find out what the actual cause of your problem is instead of chasing windmills.

Translate

buzz

Grand Maestro

After a System Update to Version: 16.5 (build 82259204) yesterday,

with my mix of PLAY1 (A101/A200), CONNECT (D102) and SONOS one (A300/A201) speakers,

WITHOUT any action to add the shared folder on my part
while it previously only gave “the music library is not reachable” errors.

SONOS S2 has today indexed the entire music library 44.0 GB (47,275,733,146 bytes), 7,737 Files, 586 Folders, size on disk 48.2 GB (51,853,131,776 bytes),

The music folder is on a SAMBA share of the SAMSUNG PSSD T7 (SSD) USB3 attached to the ASUS XT8 mesh router ---

strangely the controller apps must have had some memory of the place where the music folder was.

HOWEVER the playlist queue is behaving very strangely -

Whereas it accepts some of the folders to be added to the end of the queue, with other folders, just offers “Pin Collection to Home”
At times it jumps from one song to the next!
Also, at times it just says “something went wrong”

So it looks like a work in progress

Why do you keep repeating this post?

At times it jumps from one song to the next

This is classic behavior when communication is limited for some reason. If access seems hopeless on the currently playing track, the next track in the Queue is attempted. While not the most useful diagnostic data you could check PING times to your storage device.

As has been said before, no music is stored in the SONOS controller or hardware. A copy of the library index and SONOS Playlists is stored in each player, not the controllers.

Translate

A

Albert_8Author

Avid Contributor I

-

Translate

buzz

Grand Maestro

Furthermore, if you are playing a Queue of NAS tracks, after play is initiated you could shutdown or uninstall all of the controllers without interrupting play.

A controller will pair with a player and that player will attempt to keep the controller updated with the current system status. If this communication link is unreliable, status display accuracy will suffer.

After track metadata is fetched and play starts, the track time is ticked by the controller, rather than having the player report each second of play. If the player is having communication issues, play can be interrupted (the player will mute), but the controller cannot be notified of this issue. Since the controller is still ticking off the seconds, we get reports of “silent play”.

Translate

So it looks like a work in progress

So it looks like a work in progress

Sign up

Login to the community