On Tuesday 21 May 2013 10:51:20 Fred Gleason wrote: > On May 20, 2013, at 18:27 35, drew Roberts wrote: > > Let's call this modified now and next feature "full now and next" and it > > will be now and next for every audio event that goes on air and perhaps > > we will need some non-playout audio events to handle live reads for > > instance. > > How about an RML, something like: > > PD <mach> <cart-num>! > > Send PAD data, where: > > <mach> - The originating log machine [1= Main Log, 2 = Aux Log 1, 3= Aux > Log 2] <cart-num> - The cart from which to take the PAD to be sent
Either I was unclear in my explanation (very possible) or I do not understand your answer (again very possible)... Isn't PD the DUCK PANEL BUTTON? PD <panel> <column> <row> <level> <fade> [<mport>]! Web searching makes me think you might have meant RLM rather than RML. http://lists.rivendellaudio.org/pipermail/rivendell-dev/2012-August/016650.html New Rivendell Loadable Module. An 'rlm_padpoint' RLM has been added that can be used to send PAD data to a PadPoint processor system. https://github.com/tryphon/rivendell/blob/master/rlm/rlm_padpoint.c * This is a Rivendell Loadable Module. It sends Now&Next PAD data via * UDP packets to one or more PadPoint PAD processors as specified in the * configuration file pointed to by the plugin argument. So, if you meant something like this, do we currently have the ability to define multiple Now and Next setups for the same station? The normal one which sends only say when music plays and an everything one like I am speaking of for every "audio event" in the log? all the best, drew _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
