Thanks for the info. What I understand from others... using this system will cause carts to be randomized... from the ones I select to be played during that specific time slot on the clock? Is this a correct assumption? Or will carts be played in sequence?
On Mon, Jan 2, 2012 at 7:42 AM, Wayne Merricks < [email protected]> wrote: > Hi, > > From what I've read I don't understand why you are scheduling specific > songs/carts in the logs manually if what you really want is a generated > log. RDLogedit lets you manually create playlists and is only really used > as an exception to the normal logs for example if you have a one off live > OB show (or you can use it to edit the generated logs). > > You really want to start from rdlogmanager and set up your events. > > This website was really helpful and I think was linked in the wiki: > > > http://thebrettblog.wordpress.com/2009/12/31/rivendell-how-to-schedule-music/ > > First of all create your events, such as rock, pop, top of the hour, > bottom of the hour. For rock etc you would just select music from the > rock cart group. You can then edit the scheduler rules for this event so > that you can increase/decrease artist separation or maybe have a don't > schedule after any songs with the fast scheduler code etc etc (this is > really up to you to plan out the codes and groups so they make sense). > > The way you make sure your logs are on time is to over schedule (maybe 2 > or 3 extra songs so there will always be enough for 1 hour) and then use > the top/bottom of the hour events as hard timed to start on the hour (or > half hour). You can add fade out macro carts to make the transition more > pleasing on the ears. > > Once you've done that you build clocks from the events and grids from the > clocks. Make sure you add auto append chain to next days log. There has > been discussion on the list recently about how best to do this to avoid > scheduling problems where a day is skipped so please refer to that for > best practice. > > I'm not sure exactly how you would play songs from the same album unless > you had macros that did it? You might be able to use scheduler codes if > you can get creative, you might have to tweak the artist/album > separation. Plus I think you'd end up with tons of codes so you could > keep album tracks together. > > My advice is read the web page link and get your head around the > scheduler, most of what you're asking can be done using that and tweaking > rules. > > Regards, > > Wayne > > On Mon, 02 Jan 2012 06:30:18 -0000, Patrick Schmalstig / WRRJ Radio > <[email protected]> wrote: > > > 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. > > ####################### > Scanned by MailMarshal > ####################### > > > #################################################################################################################################################################################################################### > > Attention: > > The information contained in this message is confidential and intended for > the addressee(s) only. If you have received this message in error or there > are any problems, please notify the originator immediately. > The unauthorised use, disclosure, copying or alteration of this message is > strictly forbidden. Christian Vision or any of its subsidiaries will not be > liable for direct, special, indirect or consequential damages > arising from alteration of the contents of this message by a third party > or as a result of any virus being passed on. Please note that we reserve > the right to monitor and read any e-mails sent or received by the > company under the Telecommunications (Lawful Business Practice) > (Interception of Communications) Regulation 2000. Christian Vision is > registered in England as a limited company 2842414 and as a charity 1031031 > > > #################################################################################################################################################################################################################### > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
