Method 1. I can can change MM5 to play to my Sonos (Tools|Options|Player|Stream set to one of my Sonos units).
Then select a track using MM5, and select Play from the right click menu ... select another couple of tracks and right click PlayNext
All tracks play as expected
The usual problem with the Sonos controller when used in this mode; ie. it shows album & track name .. no art, no artist name, no visibility of the queue, not even any view of what is next ... pause and back to the begining buttons work, but not skip forward.)
Method 2. Or I can configure MM5 for sharing (Tools|Library|MediaSharing) including giving it a new server name, so I am sure that it is not the MM$ server that I am using
Open a Sonos controller, browse to the MM5 server, and play a track
Works as expected; actually I don't expect too much, as Sonos does not support DLNA servers as a source very well ... so I can queue a track, but can't queue an album, can't multiple select tracks on the mobile Sonos controllers, see no art on the Sonos controllers, but skip forward works here, I can't see the queue, but I can see what track will play next ...etc etc
It is probably not relevant, but I am on a beta version of the Sonos s/w .... am pretty sure that it is not relevant ... I don't believe that there are changes that would affect what BMF is reporting.
I don't ever see the album art on Sonos controllers ... probably because I don't have track art embbeded in my tracks ... my track art is in Folder.jpg, ie. one only file in the album folder
Firstly Sonos plays flac natively w/o transcoding.. all my tracks are flac.Ludek wrote: ↑Mon Oct 15, 2018 4:27 am If yes, then there are two possibilities for the playback error:
a) Sonos can access the file, but the file format is unplaybable on Sonos, to verify you can set auto-conversion FLAC > MP3 or try to play a MP3 file to Sonos to see whether it plays then?
b) Sonos fails to access the IP address for some reason 192.168.188.21 , go to Options > Media Sharing > Server > [Server] tab and change IP address to another choice there.
There are other possibilities.
BMF, are your Sonos units wired, or WiFi?
You get the same problem with a Sonos zone wired via Ethernet cable?
You could try rebooting your Sonos units.
The latest Sonos version made some internal changes to the way that Sonos zones are grouped and re-grouped ... I saw some third party controller people reporting this.
If no success, try submitting a diagnostic to Sonos, and ask them for assistance.
It works for you with MM4? ... or do you have the same issues with MM4?