tnx Wayne.
I'm working on this also right now, looking at an explosing of blocked
audio in airplay, so I will have to add 6 scheduler codes (5 day parted
and 1 all day in my case) and in the grid I will have to put day parted
clocks based on events getting these codes?
So in stead of one autodj for the day and one for the night I will have
to create five clocks, this seems to make setting the time in a cart a
bit redundant unless you part it somewhere in the day part of course,
which I don't.......... we've just set 1200 times in
dayparting.......... starting with 1200 scheduler codes .....
Wayne Merricks schreef op 8-11-2013 0:49:
Hi,
This confuses the guys where I work quite often. The way to think
about it is a cart is always valid to be scheduled as long as it is in
the right group with the right scheduler code (and adheres to the
artist/title gap).
As you noticed, the CUT check only happens during air time. So the
easiest way to do it would be:
Create 1 BAND PROMO cart.
Put in cuts for:
Super Band A
Mediocre Band B
OMG The horror C
Seriously who chooses these D?
Then daypart the cuts for whatever days/weeks you want.
Then create an event for Band Promos and drag in the BAND PROMO cart
into pre or post schedule (I normally use pre).
Shove that event in the clocks whenever you want it to play.
Then schedule away to your hearts content.
Now to make your life easier, create a drop box that imports direct to
the BAND PROMO cart (you can date offset here too I think). Just
remember you only have 999 cuts before you run out unless you set it
to purge expired cuts.
Regards,
Wayne
On 2013-11-07 22:38, Nate Hartmann wrote:
Hello again folks,
Weve had our Rivendell server in production since October 27th, and so
far were loving it.
The short version of my question is: what is the best way to scheduled
content to go into rotation at a future date?
The long version of my question is...
I have cron jobs set up to generate tomorrows log every day. I have
created some carts which contain cuts which should not go into
rotation until the following week (based on their air date/time
settings). For example, songs by a band which we plan to start
promoting next week. [1]
Those carts are included in events using the "Import From" feature.
When I generate logs for today/tomorrow, those carts are included in
the generated log. When I load the log into rdairplay, those carts
appear in red with "No Audio Available", and they dont play.
This is all OK, except that the generated log assumes that the
(unplayable) cart will take up a certain amount of time, when in
reality it will take up no time at all. As a result, I run the risk of
running out of music before the hour is up (I believe this is referred
to as "underscheduling"?).
The workaround that comes to mind is to overschedule more to
compensate - the extra tracks will get dropped by events with hard
start times, no harm, no foul.
However, I have to wonder if Im misunderstanding the correct way to
set air dates/times. Is this something I should be setting per-cart,
rather than per-cut? Or is there another, better way to schedule cuts
to go into rotation at a future date?
I did see something odd in rdlibrary, probably not related but worth
mentioning[2].
Thanks for your insight,
Nate "DJ Homebody" Hartmann
[1] I created these carts using rdimport --log-mode
--create-startdate-offset=7 --create-enddate-offset=15 --single-cart
MUSIC *mp3
[2] Although my rdimport command correctly sets the air date/time for
each cut, rdlibrary does not show the start or end times in its main
view until Ive opened the cart (even if I make no changes). Generating
the log after viewing the cuts and causing rdlibrary to show the
start/end doesnt change the behavior when generating logs, though.
_______________________________________________
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
