Please forgive me any naivety as I've yet to implement Rivendell to fully automate log generation. The only thing I can offer is how Dalet (or at least the old NT4 based version we still use!) works around this problem (not completely successfully) and the work flow of our presenters while using it.
Dalet loads logs in 1 hour chunks, with around 15minutes left of play out remaining it loads in the next hours worth of stuff. Whatever is loaded at that time is what ends up on air. At any time a presenter can force reload the log which loads in that particular hours chunk and then automatically scrolls down to where it would be if it had been playing (e.g. 20minutes into the hour). The main thing that changes for us is news reports (5minutes every hour). We leave a "please insert news" tag in the log and the presenter just adds it before the timed news block plays out. The only other thing a presenter generally changes is songs in response to song requests (or when they just hate songs less than 10 years old which is a story for another email). In most cases, I can't see any real reason why two or more people would be working on the same hour/shows log without being near each other. I can see people changing a particular day or at least different shows/hours in the day at the same time however. Perhaps it would be worth splitting the day logs into hours or making the grids show aware and splitting by show (probably assigning grid items to groups)? Theoretically sure you could have 1,000 people editing the same 5 minutes of log and you can think up ingenious ways to work around that but in reality does that really happen and if it does why have you got 3 presenters editing the same 5minutes? Of course you can argue that it could be a user mistake, why not try doing something like a wiki versioning system so that you could at least rollback changes? Regards, Wayne -----Original Message----- From: [email protected] on behalf of [email protected] Sent: Fri 13/01/2012 21:19 To: [email protected] Subject: Re: [RDD] Log Editing - Anyway to Lock? It comes to mind that maybe we're overlooking a possible option. Right now we have the option for a chain-to in our logs, we also have the ability to load up another log (either in the main log or in one of the AUX logs in RDAirplay). What about an option to merge another log into the current log (kind of like how a copy / paste does)? The workflow would be something along these lines: You've got your broadcast day where: Mary is responsible for 2-3 pm, Joe is responsible for 3-4 pm Mary creates a 2 - 3 pm log, has full editing rights on it Joe creates a 3 - 4 pm log, has full editing rights on it. Neither Mary nor Joe touch the main daily broadcast log. In your main log for the day at 2:00 pm, instead of a Chain-To or a load log into the AUX log, there's a command to merge Merge Mary's Log. At 3:00 pm it merges Joe's log. This could potentially eliminate the confusion that could arise from using both your main and AUX logs. Of course, this would not solve the question of having multiple people editing the same log while live on-air (as in the example that James brought up). And I'm sure there are situations where something like this could/would break. Another question would be whether or not the main log was set to "save" after a "merge" (which I could see potentially causing problems too). But I can also see how a "merge" command could be useful. Just a thought. Lorne Tyndale _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ####################### 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 ####################################################################################################################################################################################################################
<<winmail.dat>>
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
