Hello again folks, We've had our Rivendell server in production since October 27th, and so far we're 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 tomorrow's 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 don't 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 I'm 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 I've opened the cart (even if I make no changes). Generating the log after viewing the cuts and causing rdlibrary to show the start/end doesn't change the behavior when generating logs, though.
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
