The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: xPLRioNet Rio Synching


  • Subject: Re: xPLRioNet Rio Synching
  • From: "rleong1" <rleong1@xxxxxxxxx>
  • Date: Thu, 22 Jul 2004 14:35:34 -0000

i don't have any suggestions, but i wanted to let you know synch works
fine for me.  one thing i did notice is if i enable random, after the
first song, all the sync'd players start playing something different.
...

--- In ukha_xpl@xxxxxxx, "Tony Tofts" <tony@x> wrote:
> Hi all,
>
> Have been looking at the rio synching (which is working fine for me)
and
> cannot see where the problem can be, other than network latency.
>
> The way it works is that synch'd units fill their buffer and signal
the
> server when they are full. Once all units in the synch group report
they are
> ready then the server sends a single udp broadcast telling the
particular
> synch groups to start playing. (By chance this is the exact same
method the
> slimserver uses to synch slimp3's).
>
> Any difference between each unit starting can only be down to when
they
> receive the start signal...
>
> All the units are doing at this point is waiting for the start
signal. This
> process is repeated at the start of each track to help maintain synch.
>
> I've considered various options on the server and client side for
> communicating the current position and bringing them into line that
way, but
> if a simple 'start' command gets delayed on a particular network
then trying
> anything more clever will just make things worse?
>
> Anyone got any thoughts/comments/ideas please?
>
> Many thanks
> Tony
>
>
> [Non-text portions of this message have been removed]




xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.