Hi,
Sorry I'm a bit confused by your 1200 scheduler codes so I'm not really
sure what you're trying to do.
I'll take a guess but I could be wildly off. Try to make your events
generic and you won't need to mess with the scheduler very often.
For example, music doesn't need too much messing just add a get me
music event and let Riv sort it out. Or if you wanted add codes for
A/B/C List to carts and have events for Get me A List Music etc.
The only time I would daypart a music cart is if a track had a sweary
version and a clean one. You could put both cuts in the same cart and
daypart the clean for 6am - 9pm and the sweary one for after.
The main thing I use dayparts for is so I can schedule a "play quiz"
and every day/week/whatever we import a new cut and set the times for
when its valid. The scheduler never changes but as long as we keep
importing cuts and setting dates, the quiz changes as often as it needs
to.
We also use it for show highlights, a random weekly drama thing and
probably others (I'm the tech guy I don't really get involved in the
format wars).
If I was trying to make sure I wasn't scheduling death metal during the
Sunday worship times I find it easier to stop that by having "get me
death metal" events and simply not putting them in the clock that has
worship stuff in it. You could also put restrictions on the death metal
code in the clock that deals with this time but I'm not sure if you can
stop it that way (its been a while since I played with the scheduler).
Be aware that the only way to be sure not to get a cart with the wrong
code is to move it to a different group. Rivendell will respect the
scheduler code if it can but if you fall victim to artist separation,
code rules can and will be broken, so you could end up with unexpected
things playing.
Regards,
Wayne
On 2013-11-08 00:30, Rick wrote:
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
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
