On 7/14/21 6:29 PM, Fred Gleason wrote:
On Jul 13, 2021, at 11:33, Alejandro olivan Alvarez <[email protected] <mailto:[email protected]>> wrote:

A curious case is when I schedule a macro cart in the log that stops the log machine and switches to an external audio source, the idea is to do a last now&next update so the resulting Icecast2 stream will display something like 'foo - is now live from bar' ... I can see the 'SN now 1 10000X' on the machine, but the pypad never 'catches' the update.

The PAD for the current ‘default Now & Next cart’ that the ‘SN’ macro sets is emitted only when the referenced log machine stops-down completely. It will not override the PAD sent by currently playing cart(s).

Hi! thank you so much for your help!

It's not entirely clear to me the 'machine stop-down completely' (probably still not enough radio/Rivendell jargon in my mind) maybe I'm wrong, but, translating it to me as 'completelly ending the current playback', that would somehow explain the behavior I experienced.

With that interpretation, the machine has to be running (well, what I think of 'running'.. executing the log... i mean, no PS), so, the SN cart that I execute NOW, will be sent to the server after/once the current song on the machine ends (and, therefore, it is time to send a new metadata to the streaming server).

Adding PS on the MACROs in my tests, seemed to do the trick... Now I explain that as those PS gave time to completely end the current song, and then update the streaming Server, and then, even issue a PS afterwards.

Best regards


Cheers!


|---------------------------------------------------------------------|
| Frederick F. Gleason, Jr. |             Chief Developer         |
|                           |             Paravel Systems         |
|---------------------------------------------------------------------|
|           Beware of Programmers who carry screwdrivers.       |
|         |
|                                             -- Leonard Brandwein   |
|---------------------------------------------------------------------|


_______________________________________________
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