NAS playlist skips songs often with share does not exist message

Hello ​@alan278, welcome back!

I am sorry to hear you are experiencing issues with missing tracks on your playlist from your NAS drive.

May I ask, have you tried re-creating the same Playlist? Or simply create a new one with just a few of the missing tracks for testing purposes?

You’ve already done some basic troubleshooting steps that I would have suggested.

Best course of action would be to reproduce this issue, Submit Diagnostics within 5 minutes of doing so and then reach out to our Support Team for live troubleshooting.

They have tools at their disposal to provide you with information and advice specific to your Sonos system and what it reports.

I hope this helps.

My NAS drives are slow to wake. If they’ve been sleeping when I start music play, a few tracks might be skipped.

Check for duplicate IP addresses.

Are you saying it’s always the first few tracks in the playlist that fail to play or do only certain tracks fail to play?  ​@buzz may have something there thinking the Synology is sleeping.  Maybe you could use the app “Wake Me Up” to wake up the Synology before playing music.

HI

thank you very much for the input

it is not the first few in the playlist - the first one at least (usually?) plays fine but when i hit skip eventually it starts coming up with those errors.  

i have re-created the playlist several times, but i have not tested with a subset of the playlist and will do that next.

i thought i may have had it when i found one flac it was trying to play with too-high resolution for sonos .. It looked as if once it gave the message on one that rez was too high, the rest would give the NAS error.  I converted the highest rez flac in my library to lower rez mp3 and for a while it seemed to work, but no longer. 

i’ll keep working with it and report back.  Any other ideas welcome.

Thanks again for your support.

My library does consist of many tracks above the 24/48 Sonos limit for lossless ( FLAC etc ) and 24/16 for WAV.  Not exactly sure about the WAV limit.  Anyway, I converted any tracks that were in a playlist to either 24/44.1 or 24/48 FLAC depending on the original resolution.  96 - 192 became 48 & 88.2 - 176.4 became 44.1.  I did not get rid of the originals instead I put the converted tracks into a folder called For Sonos.  Then I created playlists with the suffix ( Sonos ).  So Cello Concertos became Cello Concertos ( Sonos ).  The playlist Cello Concertos is still retained for my other systems that don’t have the Sonos sample rate limit.

Had to tweak the sleep settings on my old NAS to keep it from spinning down the drive. Set it to stay awake for a minute longer than your longest track as a first try.

For me, NAS seems fine (always on, always immediately responsive).

I made a few changes and on a spot-check, it seems to be working for now.

Mainly it was changing some things that Sonos may have had issues with like

• (A) some filenames with special characters and
• (B) high rez flac files. 

(Also turned off recycle bin on NAS so that Sonos did not pick up old playlists etc)

Once I corrected all those that were in the playlist, it appears to work ok now.

The diagnosis was difficult -:

I think the Sonos “share does not exist” error was not an accurate message.  It came up on songs that it could play individually.  I suspect maybe when Sonos hits a song it cannot play in a queue (like one with some special characters in the filename or maybe high-rez flac), it has been, for me, trying to play subsequent songs in the queue and although it should be able to, it gives that “share...” error message for them. 

Next time it happens I will run a screen recorder so I can go back and find the first error that came up (they fly by so fast and i can only see the last one) - I suspect that first one is the one that caused the error messages on what normally would be playable. 

Have you considered having your NAS filter the characters that SMB can't process?

I discussed it here, enough to get you started on your NAS I hope.

https://stan-miller.livejournal.com/650.html

Change to the [music] share configuration for just the ‘:’ to ‘÷’ mapping change since that was my only problem character.

vfs objects = catia

catia:mappings = 0x3a:0xf7

If you find you have other character problems here is the full list.

The following will map all invalid windows filename chars: # "\ / : * ? " < > |" # (plus the blank char, not always allowed with legacy clients) 

catia:mappings = 0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0

​@Stanley_4 

Some ‘ characters are also not accepted.  When I replaced them with the apostrophe on the keyboard all was well.  You can hardly tell the difference between the one that isn’t allowed and the one on the keyboard.  This issue was pretty rare.

It’s possible the recycle bin was contributing to your problem. Sonos indexes anything it finds on your share. If what it found is no longer there when you go to play it, a “can’t find” error is issued. You really shouldn’t have the recycle bin where sonos can see it. Disabling it is the right thing to do in this case.

That is the beauty of the catia vfs mapping function, you can work around SMB, Windows or Sonos naming issues without altering your original file name. I really like keeping the original file names for systems that can support them and doing on-the-fly remapping for the crippled systems use. Just have to have a character to hexadecimal table handy.

catia:mappings = 0x3a:0xf7