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 feature requests


  • Subject: RE: xPLRioNet feature requests
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Fri, 13 Aug 2004 05:26:17 +0100

> * A method of requesting what a rio thinks the current track time is
> * A method of requesting what a rio thinks the current/next
> track/album/artist is

I assume these are xpl requests? Can add these if so.

> * db.xql access to the music database from xPLRioNet

This can be done now in a few ways. If not already running tts_xql on the
xplrionet pc you can install it and point it at the data.mdb, or if already
running it then just create links in the existing mdb to the tables in
data.mdb?

> * A method of sending OSD messages to the rios - either en
> masse or individually

Using the rio (and slimp3) displays as osd's is on the to do list

> * Triggers on button presses for all buttons

It already sends all keys when power is off and when power is on but rio is
not in a menu. Also have added a new audio.rio command extended=lock on/off
that prevents rio actioning key presses (just sends them). Does this cover
everything?

> * A method of changing the logo, probably just an app to
> patch the rio.bin - hey we're automators, we want to change
> everything :D

Have to think about this, not too sure.

> * Syncing other units with a currently playing rio

It is not really possible to join in mid-stream, since the buffering makes
matching everything up just about impossible. It would be possible to
automatically restart a playing track into synch mode, or have the units
join in at next track change?

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.