One thought, I have never tried anything like this before. Have the 8 hour log play out in the main log, chain to a log in the aux1 log, that log will have a timed event that will chain back to the original log in the main log, when that ends, it will chain to the log in aux1 again which will have another timed even 8 hours later that will chain back again. Could something like that work?
You may have to hand edit the chain at the end of the main log and build the aux1 log by hand. Worth a try. (Perhaps you will need to have the aux1 log stop after chaining to the main log and perhaps chaining is not the correct verb for what needs to happen. As I say, I have never messed with this sort of thing.) all the best, drew On Sun, Feb 8, 2015 at 6:19 PM, Chris Howard - CBR <c...@elfpen.com> wrote: > > I think I understand that part. > > But, when I have it create my 8 hour log it will select > the random parts from the library (this is good). > > But I want the same bits when I repeat the 8 hour block. > > Let's say this is the Sherlock Holmes show. I put > in the TOH stuff and a 45 minute selection (hard wired) > for today's Sherlock Holmes and then I fill in the rest > of the hour with system-selected library spaces. > > All of that I have working. > > The part I don't understand is how to get that exact same > show to play again 8 hours later, and yet again 8 hours > after that. > > Maybe I'm being dense.. > > Chris > > > > > > On 2/8/2015 1:33 PM, Robert wrote: > > Chris, > > Rivendell makes this really easy. > > > > You create 8 One Hour Clocks. > > > > The EVENTS will be the Top of the Hour Fol De Rol which may be 1-10 or > more seperate events, The main programme for that hour EVENT(S) and a > series of Fill events which give you more than an hours programme, with the > Top of the Following hour event pre-empting unneeded fill events. > > > > Lets call them Clock1, Clock2....Clock8 > > > > Then put the right clock in the right hour in the GRID and you have a > day/week schedule that you create a log for and thats what runs. > > > > You will need a CART for each element, and I recommend creating an EVENT > for each element, but you can stack as many as you like in an event. > > > > I suggest you plot one event per minute which gives you 60 in an hour, > and if you don't need that many plot one every 2 minutes but 1 minute > duration so you have convenient gasps for putting stuff in later on. > > > > The time you allow in the clock has no bearing on the actual running > time of the event. I have 1 minute events which vary from a few seconds to > 59 minutes in actual duration. The clock model is just an easy visual aid, > and if you are happier putting in approximate durations so you can 'see' > how your hour looks then go for it. > > > > Your fill EVENTS at the end of the hour can be selections from a GROUP > which has 1001 CARTS and you might have 5 or more at the end of the hour. > Rivendell will NOT programme out exactly to the end of the hour and if the > rollover time is critical then you may have to do some manual tweaking to > the log. You can Programme a lot of short events which fill out to the > hour, or if you have the right audio card you can have some time > manipulation for the entire hour which will deliver an exact time out. > > > > Doing the clocks is relatively easy once you have figured out the > elements. > > > > regards > > > > Robert Jeffares > > > > > > On 02/09/2015 08:05 AM, Chris Howard - CBR wrote: > >> > >> Hi everybody, > >> > >> I was pretty hot and heavy into installation and configuration a year > >> ago, right after we got our LPFM CP. But I put that aside > >> and I've been doing organizational stuff and fundraising for most > >> of the last year. > >> > >> Now our CP is winding down and I'm hoping we will have the $$$ and > >> meanwhile trying to get ready for the day when I can take shipment > >> of the equipment. So I'm back looking at Rivendell configuration. > >> > >> Our "format" is audio books. Hourly "shows" consisting of > >> a few small introductory, top-of-the-hour bits, then one > >> or more large bits (30-40 minutes long) and then usually > >> an assortment from the library of shorter pieces to fill the hour. > >> > >> We want to have an 8-hour block of this. Then we want > >> to repeat that log twice, to make our 24 hour day. > >> > >> I don't want to just record the 8 hour block and replay it > >> (although it may come to that), because I can see that we > >> might have a bit of give and take at the end of our 8 hours > >> which would then be multiplied X3 by the time we got > >> to the end of the day. > >> > >> So, I am considering how to play the log three times. > >> That would let rdairplay fill or trim as necessary. > >> > >> My current idea is to have some SQL statements which > >> will take the log table and copy everything in it two more > >> times... staying in the same table. I would generate > >> the log, run this SQL script and BAM, we are x3. > >> > >> -or- > >> > >> make two more tables logA, logB, and add two chaining events > >> at the end of the main, generated log to fire them off. > >> > >> Before I dive in I would like to know if there are implications > >> from either way, or even a better way that I have not > >> considered. My Rivendell mindset has faded a bit, I may > >> be completely off track. > >> > >> Hope you all are doing fine and I thank you for your support. > >> > >> Chris Howard > >> Classic Book Radio > >> WMFH-LP 95.5 (CP) > >> Columbus, MS > >> > >> > >> > >> _______________________________________________ > >> Rivendell-dev mailing list > >> Rivendell-dev@lists.rivendellaudio.org > >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > >> > > > > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > -- http://nakedghosts.blogspot.com/
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
