Actually I thin the first suggestion I made will not work now as I reread what you want to do....maybe it will, I dunno. I still think the second suggestion would be better for you. Yes I think I would go that route. Create macros to load each students(or team of students) show into the aux log, and start the playback of the aux log, and stop down the main log. Then at the end of their show it needs to have a macro to start the main log back up. I'm sure there are many other ways to achieve the same end, this is just a simplified suggestion. Timing and commercials or spots would be the tricky part, but I'm sure there is a solution.
Nathaniel C. Steele Assistant Chief Engineer/Technical Director WTRM-FM / TheCrossFM On 1/13/2012 10:57 AM, Nathan Steele wrote: > In RDAdmin under service there is a check box to enable "autorefresh" > this will update the log on RDAirplay I think whenever it is edited. > maybe that would do what you want. > > But, why not make the Airplay log with macros that load and play the > students show logs, and they create their own logs for their shows that > way no one is accessing a "shared log"? You would not even need to use > the autorefresh (which can be dangerous). just a thought. > > Nathaniel C. Steele > Assistant Chief Engineer/Technical Director > WTRM-FM / TheCrossFM > > > On 1/13/2012 10:47 AM, Aaron Horn wrote: >> Hi there... >> >> I have a bit of an issue with Rivendell... We use 1.7.2 on Ubuntu >> Studio 10.something with ASI soundcards - so far so good. I have an >> upgrade to 2x planned around Easter. >> >> We are a teaching university have have two on-air studios plus three >> satellite studios. They all share a ZFS audio share and MySQL >> database on a server. >> >> Unlike traditional radio settings, we use a highly corroborative >> approach to put together our on-air content. That is, many people put >> together the logs etc. >> >> We generate clocks but each show team comes in before their show to >> edit their section of the day log... The typical way to do this is for >> them to build their show in terms of playlist and promos in a 'scratch >> log' before copy-pasting into the main log. >> >> Our issue is that we are loosing a boat load of content, it seems that >> this occurs when the log is open in more than one location... So the >> log is being played out on RDAirPlay in Studio 1 but a user makes >> changes to the log in Studio 2 on RDLogEdit - if the user in Studio 2 >> saves all their work but then someone in another studio saves also, >> their work is lost. It's causing total frustration for my users (100+ >> of them) and I am not sure how best to go about it other than using >> the day logs only for automation and getting people to use their own >> logs for live programming (an approach I want to avoid as it becomes >> messy and difficult to manage). >> >> To me the solution is to remove the 'save' button and have any changes >> reflected live on every computer with that log open in an immediate >> sense. Either that or lock logs (e.g. 'this log is being edited at >> location xyz, please close there before editing the log'). >> >> Thoughts/help? >> > _______________________________________________ > 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
