Tue Jun 25, 2013 5:13 pm by steelrat
Sorry to bring this thread back from the dead....
However, I recently went through and tried the configuration suggested. I'm now able to see serviio as an available WMP source in the sonos software. However, whenever I go through and try add any music, I get an error message on the sonos side. Prior to making the content change in the sonos software which is supposed to see WMP sources I never did see the serviio runing. The serviio, has always found the sonos devices, and other upnp/dlna devices on the network (samsung tv, denon avr, etc). I've already forced the serviio instance to use the new sonos profile (profile.xml)... Serviio has been working well with the samsung, and the denon from day one....
I've been trying to see if there's anything logged on the serviio side.... or if there's anything from the sonos side, but I don't have anything concrete yet.
It's accessing run-of-the-mill mp3's, and potentially some flac files.... Which have been exposed and working with the denon. The files themselves are the same as directory, as the regularly available content to sonos, so I don't think it's permission or pathing. I've tried adding a secondary directory, local disks to the serviio instance, just to be sure... same error.
I was trying to read through the other profiles, and see if there was anything else to potentially leverage for ideas. Does anything else require the serviio to act as a WMP source, vs, a DLNA?
While I don't need the functionality per-say, if I ever exceed the music count in sonos, I'd like to leverage the serviio instance I'm using for other content vs having to run another software....
Any suggestions?
