Bugzilla – Bug 1564
Syncing 2 SB1 syncs with a delay (-> echo)
Last modified: 2009-09-08 09:25:38 UTC
Syncing 2 SB1 (graphics display, wired) works, but the music has a delay of about 0.5s between the two SBs. This worked perfectly (without delay) with older SlimServers (I update SlimServer quite frequently but do not use syncing very often so I'm not shure on which older versions it worked, but I think version 5.4.1 was OK). Remarks: - First SB1 connected via Ethernet - Switch - Firewall - SlimServer - Second SB1 connected via Ethernet - PowerLine - Switch - Firewall - SlimServer (This configuration worked fine with previous SlimServer versions, see above). SB1 firmware: 40 PowerLine: http://www.devolo.co.uk/uk_EN/produkte/dLAN/mldlaneth.html
Pascal: Can you try to connect the players directly via ethernet and see if the problem goes away?
Hi Dean (sorry for the delay answering your question). Connecting directly sometimes does shows the delay too. I tested with a new configuration: - First and second SB1 connected via Ethernet - Switch - Firewall - SlimServer (on the same ethernet switch) - Third SB1 connected via Ethernet - PowerLine - Switch - Firewall - SlimServer (All SB1, graphics display, wired) Result: - Syncronizing all three SB1s shows different delays on all three SB1s (even the 2 directly connected to the switch are not playing synchronously). - Skipping forward (>>) and backward (<<) will randomly change the delays (in the range from almost good to really out of sync more than one second!). - Taking out the third SB1 (PowerLine) from the synched group improved the situation, but I still had the situation of delays sometimes. But this I was able to reproduce 2 times only. I hope this informations helps you to find the problem.
Vid, is it possible we're not flushing the TCP socket?
I've just checked in a large patch to the SlimServer 7 sync code, thanks to Alan Young. Please retest this issue.
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.