I've tried to understand the logistics behind the log system. The issue with my station though when it comes to logs is timing. I tried using logs before. It didn't work properly (was I doing something wrong?). The logs did not satisfy the times I specified when generating them... not even close. If I started a log at 12, it could be up to 3 or 4 hours off by the end of the day.
Secondly, the clock system seemed weird because I had to insert a new piece FOR EVERY TRACK I wanted to play... instead of inserting one piece for every "genre period, commercial period, et cetera" I wanted. And again it was not even close to staying on sync when the logs were generated. Third, I like to have random albums played, and a few tracks from each album. I have a PHP script that successfully plays random albums, and the logs are set to play not one but a few tracks from that album before moving to another random one. I'd like to keep it that way. Finally... the way I'm setting up the station to allow other churches to participate... and the groups I have to make... I have it set so only I can use up to 1000 carts for myself... so that it's divided that all churches can use up to 100 each. It also, even though you say it's better, isn't easier for me, to have one cut per cart and then have a log system. I already spend enough time as it is managing my church website... I don't really have the time to spend operating with these log rotations and clocks... and having one track of a song per cart. Now if there was another person that COULD help me with the station I probably could use logs... but the problem is... where I live right now... there is no one who can help me. Much less, there isn't anyone who would give two cents about the station and would actually be reliable when it comes to helping me out. I feel that way from experience. But regardless... I am open to you helping me understand this logging system and use it right so that it's not so off in timing... if you care to explain. I'd appreciate that. On Mon, Jan 2, 2012 at 1:18 AM, Kevin Miller <atf...@alaska.net> wrote: > On 01/01/2012 06:58 PM, Patrick Schmalstig / WRRJ Radio wrote: > > > Does anyone have any hints on how to shuffle my cuts on a per-cart basis > > efficiently? ...even if I have to use a PHP script executed on a > > schedule to make MySQL queries? > > It may have changed, but historically the advice was to have one cut per > cart. The exception was with advertisements or IDs and the like where > you might have various versions but it didn't really matter which > played, as long as one did. Usually it was just a sequential rotation. > For instance you might schedule an ad to run three times an hour - at > the top of the hour, at 20 minutes after, and at 20 till. Having three > different versions of the ad keeps it from being repetitive but you > don't really care which ad is when. > > Songs and the like only had a single cut per cart, and the scheduler > would select the cart based on group, scheduler codes, etc. See the > wiki page: http://rivendell.tryphon.org/wiki/Managing_Scheduler_Rules > for more details. > > It may be that you have a specific need for having multiple cuts per > cart, but in general I believe that having one per cart makes the system > more manageable, and I think that's how it was designed. The scheduler > program would pick the carts, presumably randomizing them as appropriate > based on criteria you specify. > > Others, more knowledgeable than me, can chime in with more advice if I'm > steering you wrong... > > ...Kevin > -- > Kevin Miller - http://www.alaska.net/~atftb > Juneau, Alaska > In a recent survey, 7 out of 10 hard drives preferred Linux > Registered Linux User No: 307357, http://linuxcounter.net > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
