Well, we don't :)

Users listening to our radio on our Icecast stream already experience a
small delay between the song change (immediately shown on the site, it
is asynchronously pushed /via/ a websocket connection) and what they can
actually hear. But it is about 10 seconds, so adding this to the low
accuracy of the times (not) sent by Rivendell, we can accomodate.

    Hoggins!


Le 28/06/2014 17:45, Thomas Churchill a écrit :
> How do you keep it synced? I am sure the answer is out there, I haven't had
> time to look yet. So far I've just written a simple updater. But when the
> audio stream slips to 20-30 seconds behind realtime, and the meta data is
> almost instantaneous it's a bit discombobulated for the viewer.
>
> TC
>
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Hoggins!
> Sent: Saturday, June 28, 2014 11:37 AM
> To: [email protected]
> Subject: Re: [RDD] About RLM fields
>
> Yep.
> In the end, I will need that.
> It is mainly for events where the transition markers are placed way before
> the real end of the event. Like a segue in / segue out marker that would
> fire before the "applauding" sequence of a live performance.
>
> Anyway, I'm using it to have a progress bar on our website, for current
> playing tunes. Here is what it looks like : http://radiom.fr.
>
> Hoggins!
>
> Le 28/06/2014 17:33, Thomas Churchill a écrit :
>> At the time you wrote the message I was actually writing a little 
>> script to pull this information from the DB. The "now" and "next" 
>> information for the metadata works well, but I wanted a little more 
>> info on one page about everything that's coming up in the next hour. 
>> Each daily log that's created is saved and updated as a table in the 
>> database. "EXT_START_TIME" holds the expected start and "EVENT_LENGTH" 
>> holds the event length surprisingly. You have to cross reference the 
>> "CART_NUMBER" with the "CARTS" table to get the title, artist etc. Perhaps
> that's what you were looking for?
>
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
>
>

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to