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: can''t play music w/ xplrionet AND synch info


  • Subject: RE: can''t play music w/ xplrionet AND synch info
  • From: Tony Tofts
  • Date: Wed, 31 Mar 2004 07:27:00 +0000

> i am able to boot a rio & navigate to an artist and select
> play all and then the receiver hangs. this happens all the
> time. tony, i've sent you a trace.

Looked at the trace, the rio is requesting the track, but get's no response
from xplrionet other than a command to display the status screen.

Checking the code the only obvious answer is that it's unable to open the
mp3 file...
Of course the real problem might _not_ be the obvious one!

Looks like it's time to add some debug logging to the streaming code.

Unfortunately I'm right in the middle of work on the synch stuff at the
moment (see below), but once steve has been able to confirm that the alpha
beta build I've sent him is stable I'll release a partial synch version
with
the debugging added.

Current state of play with synch stuff is that rio's can now be joined into
groups, with command/display echoed between joined units. All panel/remote
control commands and some xpl/web commands are synch'd.

Still to do on synch stuff:

A) get all xpl (and therefore web) commands working with synch

B) Add code to actually synch the music (currently it synchs by pure
chance)

C) add xpl/web commands to allow synching via xpl/web

I've had 4 rio's + 1 virtual rio all working in unison in a synch group,
and
they were pretty much in synch (except pseudo) as far as I could tell (but
purely by chance)

Regards
Tony






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.