RE: [RDD] More questions

["John Handelaar" <john@xxxxxxxxxxxxxx>]

> From: owner-rivendell-dev@xxxxxxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-rivendell-dev@xxxxxxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Fred
> Gleason
> Sent: 29 July 2004 13:25
> To: rivendell-dev@xxxxxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [RDD] More questions
> 
> > Q4   For streaming (and maybe RDS), getting the 'now playing'
> >      data into an encoder is good.  Other apps often have a
> >      'watch file' which puts now and next into a plain text file
> >      which can be parsed by third-party apps.  Do we have such a
> >      thing?
> 
> Not at the moment, but it sounds simple to do.  Any particular 
> format that 
> this file needs to be in?

In RCS, for example, the file is called 'bilboard.asc' (gotta love
those Windows 8.3 filenames) and iirc it does token replacement
on a short text file from a template.  So basically you make all
the available variables for the carts in the now and next slots,
and let the end use pick a format.

Example real-world file: http://www.rfm.pt/bilboard.asc

[They're not doing much with theirs.]

Other systems vary in their customisable-ness but they all try
to do at least that.

(By the way - I understand that 'coming next' is prohibited from
use in the US by the music industry's litigation efforts.  It's 
perfectly permissible in lots of other places, including the EU.)


> You may also be interested in Dan Mills' 'airchain' project.  

Ooo.  Looks nice.  I'll have a look at that.  Cheers :-)

(You're up early today, aren't you?)


jh
-----------------------------------------------------------------------------
To unsubscribe to the rivendell-dev list, send mail to
'majordomo@xxxxxxxxxxxxxxxxxxxxxxxxxx' and put 'unsubscribe rivendell-dev'
in the message body (NOT the subject line).
-----------------------------------------------------------------------------