Sonos integrates many services, yes, but they do it in a very simplistic way. Services are not fully integrated with or blended into your library. Each lives in its own ghetto, and you can browse them with a very basic list-based mechanism.
Our approach–seamlessly blending your content with content from services, and allowing for the same ownership-like experience for streaming and local content–is significantly more ambitious.
It is important to us to line up at least one other streaming service, so that we are not solely reliant on TIDAL. It will have to be lossless to make sense with such a quality-focused product–which limits the options. This is an area where we’re actively working, but not a fast process. The technical/data pre-requisites that are required to accomplish our style of integration are more than these companies are accustomed to providing, plus many of the most popular streaming companies (Spotify, Pandora notably) do not like to work with others on stuff like this at all.
We don’t share ETA’s until work on a project is substantially done and into alpha testing. Too many variables or opportunities to change plans or re-prioritize. It just leads to disappointment.
Don’t see it as a systemic Android problem, might be a galaxy S5 problem. After reading your posts I put a Note 3, a Note 4 and a Note 5 and a desktop in a group and played them for 6 hours straight with no syncing issues at all.
I run Roon core on a Windows 10 computer, and not much else (Plex, anti virus, etc). Media is ripped from CDs and stored as FLAC files. I use a Samsung Galaxy S7 Edge, Samsung Galaxy Tab Pro, Windows desktop to control Roon playback. My endpoints are a Bryston BDP-2 and the above listed devices as well as the Samsung Galaxy S5. Everything is stock (no rooted phones, alternative boot loaders, etc.) Everything that can be connected via wired ethernet is. The wifi router is within 10 feet and 2 walls of everything in question, providing quite a good signal. The local network is 5GHz in 802.11AC with little other traffic and excellent signal strength.
Please let me know if you need other info. I’ll try to test this again with one of my other wired devices early next week in case the issue is localized to the S5.
An interesting experiment would be to try putting only the two or three samsung galaxy devices in a group, playing the audio out the devices speakers (ile not restreaming to a bluetooth speaker), and see if they stay in sync. Which is what I did,.
I’ve been experimenting with multi-room playback of ‘regular’ audio files: flac and mp3 format files (44.1 kHz / 16 bit) with mixed results.
In my home I’ve set up a ‘downstairs’ group as follows:
Windows 7 running Roon core and playing via ‘system output’ thru a Behringer USB DAC into a stereo amp and speakers
Windows 7 running Roon remote and playing thru a Cambridge Audio USB DAC
RaspberryPi 3 with HifiBerry DAC+ running their 1.0.4 Roon image
 and  are connected to different inputs on a stereo amp.
Positioned in the sitting-room with the door open, so that I can hear the kitchen audio too, when listening to:
 &  the two Windows systems are in perfect sync,
 &  the Windows and RaspberryPi are out of sync
I was initially delighted by the first result  &  which is something I’ve been unable to achieve with JRiver zones, but the promised land of  &  seems still out of reach: sending synched music to a dumb, cheap, dedicated endpoint.
I’m just a novice with Roon, but it would seem that:
the poor syncing between  and  is a function of device-specific implementation differences rather than network latency
the specific solution for getting my RaspberryPi in sync with Windows is either:
a) correcting any implementation error in the HifiBerry Roon image. If the HifiBerry DAC+ is
‘unable or unwilling to accurately report downstream output delays’
then is that a bug that the HifiBerry DAC+ Roon image maintainer can fix?
b) adjusting the timing of this particular node in the setup of the Roon ‘group’ – and I understand that this kind of timing adjustment is a planned feature.
I hope this is helpful as, for me at least, reliable multi-room playback is a critical feature.
I have two pi3s and a Windows 10 PC all running Roonbridge and they sync ok. I have a few times found them getting out of sync but a reboot solved things.
Try Roon bridge on the Windows 7 machine if you are not already doing that. Seems like you are past the time for the free upgrade to Windows 10. I don’t have any firm evidence but I think this has been better since I took the plunge and upgraded from win7 to win10 recently. My core is on another machine like yours that has been running Windows 10 for a while so I did have two different versions of Windows for a while.
I would add that I am getting (after an hour or two) instances of tracks stopping playback, and Roon skipping to the next track. Playback remains in sync across all zones - it’s just that Roon is reporting “Too many dropouts” in the stream, thus it stops the currently playing stream and moves on to the next track, e.g.:
@Geoff_Coupe: thanks for your feedback. The only real differences I see in our experiments are:
Windows 7 at my end vs. Win 10 in your system. But as @philr says I’ve missed the boat for that free Win 10 upgrade!
I have the HiFiBerry DAC+ on a RP3 as opposed to your RP2
@philr: are you suggesting running Roon Bridge on  the machine running Roon Core? That might improve the synchronisation between it and the RaspberryPi? Or perhaps you misunderstood my issue? The sync between the Windows machines  & (Core and Bridge) is good. It’s between the Windows machine running Core and the RaspberryPi running Bridge  &  which is problematic…
@Geoff_Coupe: regarding the skipping after prolonged playback, that is certainly not my issue. The sync issue I have is consistent: it’s there from the get-go. When I pause I hear the kitchen play on for maybe 1/4 sec before pausing. When I resume playback the delay is there again.
I’m on the road at present but once I’m back home tomorrow I will have another play…
I believe that you hit it on the nail and that it is a Windows 10 issue.
Roon is a network driven streaming program and is very good at it. However there are many stories out there about the amount of Network Traffic that Windows 10 adds to any network. As a matter of fact the more that there are Windows 10 PC’s on a network the more congested network activity there is.
Windows 10 is constantly phoning home to over 30 different servers for what that say is telemetry reasoning. Also Windows 10 Updates have been changed from the normal Direct from you to Windows Update Server to a Torrent Update Service. Bottom line, Windows 10 is network hog.
Er, except that Ed was having sync problems with Windows 7, and I’m not with Windows 10, so rather the opposite to what you seem to be suggesting.
I don’t doubt that Windows 10 is more chatty, but I don’t think this is an issue, particularly over a wired home network.
Where there does seem to be an issue is RAAT running over 802.11n WiFi. I’m consistently seeing skipping and dropouts here (with a RPI3, and with no other Windows 10 system using WiFi). Running RAAT over 802.11ac is much better, and wired endpoints carry on regardless…
To follow up, now that I’ve had a chance to play around a bit more I can confirm that I can reliably reproduce the issue: Win7 <-> Win7 players sync correctly but I have a lag between Win7 and RP3-HifiBerry+
Other possible experiments: I could:
try Win10 rather than Win7 on the Core machine. A bit of an expensive test.
try an RP2 with a USB wireless adapter rather than the RP3 with its built in wireless. Anyone in the UK able to lend me RP2 for a quick test?
try the IQAudIO Pi-DAC+ on my RP3 rather than the HifiBerry DAC+. Anyone in the UK got one spare I could borrow for a test?
@RBM thanks for this, but actually I think my tests suggest the opposite – that it’s not network latency. I have two Roon Bridges set up next to each other in my sitting room:
Windows 7 over wifi
RP3 with HifiBerry DAC+ over wifi
The Windows 7 Bridge  works perfectly: the audio in the kitchen is reliably in sync with the audio in the sitting room. Whereas the RP3 Bridge  is reliably out of sync with the kitchen. It’s consistently about 1/4 of a second ahead of the Core machine in the kitchen, producing a nasty ‘echo’ effect.
So I think my original question stands: is this either:
a) a bug in HifiBerry’s implementation which it is reasonable or realistic to expect them to fix, or
b) is it a function of inevitable differences in hardware which it is only possible to overcome with a Roon work-around in the form of configurable timing adjustments to individual nodes in a zone or ‘group’?
@Ed_Davey, it appears as though (for both myself and @RBM) an RPi with a HiFiBerry Digi+ is in perfect sync with all other endpoints, but that an RPi with a HiFiBerry DAC+ is not. That seems to me to point to a strong possibility that it’s an issue with the HiFiBerry software…
Wiring it all up is just a quick little test to rule out any unpredictable nasties WiFi may cause. It never hurts.
As for a): have you tried installing Raspbian + Roon Bridge manually? (Little guide if necessary). This may (or may not) rule out any weirdness in the Hifiberry image (I2S DACs are not expected to have any latency).
And for b): I very much doubt whether the DAC+ should need a delay, but a future Roon release will have timing/delay setting for endpoints that cannot/will not convey this information to Roon core themselves.