[RDD] Has now/next behavior changed recently?

Rob Landry 41001140 at interpring.com
Wed Jul 22 11:41:55 EDT 2015


No, the problem turned out to be something much simpler: I'm an idiot.

I was running another copy of Rivendell on a different machine atthe same 
time. It was running a couple minutes ahead of the one I was looking at, 
and talking to Live365. Oops!


Rob

On Tue, 21 Jul 2015, Hoggins! wrote:

> Hey Rob,
>
> This might be completely wrong, and you might have checked that already,
> but I ran in a similar situation where there was a huge buffer between
> the source and the streaming server : the audio was buffered for like a
> minute, whereas the metadata was udpdated instantly. It eventually led
> to such a "inverse delay" while displaying the current title, as I had
> checked by sniffing the packets that there had been no "leak" of the
> /next/ song before the /now/ one.
>
> Cheers !
>
>    Hoggins!
>
>
> Le 21/07/2015 06:23, Rob Landry a écrit :
>> I have a client who uses Rivendell to run an Internet-only stream via
>> Live365. I am using rlm_live365 to send metatata to Live365, and also
>> to a "fake" Live365 running on our own machine that keeps a log of
>> every song played.
>>
>> Since upgrading from 2.5.2 to 2.10.3, Live365 is suddenly displaying
>> the information for each song 2 - 3 minutes before it plays. Has
>> something changed? Is there a new configuration setting I need to look
>> at?
>>
>>
>> Rob
>
>
>


More information about the Rivendell-dev mailing list