On Wed, 6 Apr 2016, Tom Van Gorkom wrote:
1. Regarding those that need to play out sequentially, what is the best way to load them in the library and play them so that only those that should playout on a given day do? Dayparting doesn't seem to prevent the log generator from selecting what ever is in the group whether it is playable or not. Some only play only once per weekday and others play the exact same one in the series twice each day at different hours and the next in series the following day, etc. Currently we put them in a teaching group, assign a code to identify the author/program series. We created events for each of the specific teaching/pre-recorded programs and put them in the corresponding clocks throughout the day.
I would assign each program a cart number, and each episode of a program becomes a cut. Each cut can be marked with a start date, an end date, a daypart, and one or more days of the week it is allowed to play.
If more than one cut is eligible for a particular date/time, the cut that airs will be selected at random from the eligible cuts.
When you schedule the cart number corresponding to the program, the episode that airs will be determined by the date and time the cart is scheduled to air. You can have as many as several hundred cuts in a cart, although I've never used a cart with more than a few dozen cuts.
2. Managing the library - with so many teaching programs that expire after they air but with the habit of saving them in case downloads fail (some are sporatic), I have been thinking that they import them into the play group desired but when finished, move them to a reserve group.
You've got 999,999 cart numbers available. If you assigned, say, 100,000 to the group for teaching programs, do you really expect to run out of numbers?
Rob -- Я там, где ребята толковые, Я там, где плакаты "Вперёд", Где песни рабочие новые Страна трудовая поёт.
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
