I've had BlueSound for three years now, and I've always had intermittent WiFi trouble and the occasional Eth trouble as well.
This has been across two different WiFi routers and multiple clients (Mac, PC, IOS devices).
The problem is simply that my players drop off the list of available players, yet they remain ping-able on the network.
Restarting the client app occasionally works, but very unreliably. Rebooting the WiFi router only seems to make things worse.
The only reliable remedy is to power-cycle the BlueSound player(s). Which is obviously tedious.
Sniffing with Wireshark suggests that root cause lies with the IP multicast processing. Since two very different WiFi routers (Apple vs. Sagem) had the same problems, I would tend to look towards the BlueSound devices, but BlueSound seems to belive the current implementation works perfectly and that the problem invariantly lies with the customer's network.
Maybe it always does, I can't rule that out in any way. But maybe BlueSound can do something to make things more resilient. Hence this proposal:
* Instead of relying exclusively on player detection via multicast, also store network-related information about recently-known devices in the client and in the players themselves, and use this as fall-back if one or more recently known players don't show up in the network scan.
Today, players have an idea about other BlueSound nodes (as seen from the diagnostics log), so that's also a source of information that the controller apps could draw on in the cases where at least one BlueSound device remains accessible.
Something like this pseudo code:
Players = <do multicast scan, timeout = X secs>
Players = set-union(Players, RecentlyKnownPlayers)
Players = select-all(Player P from Players where P is an accessible BlueSound node)
RecentlyKnownPlayers = select-all(Player P from RecentlyKnownPlayers + Players where P has been accessible within the last (day/week/month, whatever seems sensible. I'd go with week, I think) )
As it is, I've almost had it with BlueSound. I have no other network issues at all, only with BlueSound. It works well when it works -- it's just too often it doesn't fully. So please, at least give my proposal some thought before routinely dismissing it as yet another user network configuration problem.
Thanks in advance. All the best,
Please sign in to leave a comment.