Hi,
Kind of already covered but as an alternative usage for logs.
Make your log of IDs with a stop transition after each event.
Every time the Switcher fires the GPIO pins use the Play next macro
(PN).
Stick a timed event at the end of the day to load the log up again.
To be honest as you're using a Pi, you could fairly trivially do this
with a bash script and a directory full of mp3s/wavs of IDs (WiringPI
for GPIO). But having Rivendell in there gives you scope to expand more
easily.
The way I sold Riv where I work was quite simple, "you know we have all
these emergency CDs that get scratched all the time, well we can use
this instead". From there it was "if we just do this little bit more
we'll have a full backup for when our main system dies". I managed to
automate including titles and markers an ingest of over 10,000 songs
from the old system which helped a lot.
Then luckily/unluckily in equal measure, our main proprietary system
had a complete RAID meltdown and was dead for nearly 2 weeks (long
story). So Riv stepped in and worked fine. Then it was an easy
conversation, [Manager] "how can we stop this happening again?" [Me]
"Pay lots of money to upgrade what we have to something current and not
a 1990s Windows NT based system, or just use this thing that kept us on
the air for the last two weeks"
Spell it out in terms of money or potential off air time and most
people tend to listen to alternatives.
On 2016-03-08 23:36, Sherrod Munday wrote:
Thats what I did for one of my stations. All my IDs went in one Cart,
all the :30 liners went in another, all the :60s went in another,
etc.
In the Sound Panel section of RDAirplay, set up a single button for
each of the Carts that contain the various liner types.
Then, wire up the relays from your satellite receiver to the GPI
inputs of your Rivendell computer. Finally, set up the GPIs to push
the appropriate Panel buttons when triggered.
If you have to mute the network audio, then youll need to have those
GPIs fire Macros instead of the simple audio carts. The Macros will
first need to send commands to your audio switcher to mute the
Network
audio, then they would fire the audio cart. Finally, after the audio
cart completes, the Macro unmutes the Network audio again.
You can do these things with the Panel buttons (meaning, you put the
Macros on Panel buttons instead of just putting the audio Carts), but
you could also do the same with a log. In reality, you could do them
even without a log or a panel, but then youd have a hard time seeing
what the system is doing in real-time - and an even harder time
overriding or assisting. I personally kind of prefer putting any
floating liners on the Panel buttons, because it also makes it easy
to
manually hit those same buttons if the relay closures arent connected
or firing from the network end of things.
Hope this helps.
--Sherrod
On Mar 8, 2016 3:52 PM, <[email protected] [3]> wrote:
Thats what I was trying to figure out. No it wouldnt be necessary.
Would it be simpler to put the cuts in one cart and then trigger it
with a macro? Just looking for any input. Will look into this.
Sent from my iPhone
On Mar 8, 2016, at 3:33 PM, Sherrod Munday <[email protected] [2]>
wrote:
On Mar 8, 2016 1:56 PM, "Seth Stevenson" <[email protected]
[1]> wrote:
>...It needs to have a playlist of say 20-30 IDs that rotate in a
loop. Once one is played then it needs to stop until the next
switcher command to play the next cut. The log needs to be
reloaded at midnight for the next day as well.
Question:
Is a log really necessary if the "spots" and IDs are just going to
loop and they arent paid/scheduled content?
If not, you can just use the GPIs to push Panel buttons that fire
off macros to mute the network (if necessary), play the necessary
audio, and then return to the network.
That would be simpler than worrying about log generation.
--Sherrod
Links:
------
[1] mailto:[email protected]
[2] mailto:[email protected]
[3] mailto:[email protected]
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
