Hello, We're already operating Rivendell with GSelector. While you can get quite far with Rivendell's built-in scheduler, things like high/mid/low rotation in categories, artist data linking (e.g. Paul McCartney was part of the Beatles and Wings, Michael Jackson was in the Jackson 5) and even the ability to apply music rules with an ID in between gave us reason to jump.
Anyway, on to your questions... > 1. RCS is going to convert the existing data to GSelector data but > they require time in mm:ss format. It looks like the time is calculated in > milliseconds?? Anyone know a shortcut (or a formula to convert to mm:ss > format in a libreoffice / open document spreadsheet?) Google hasn't been > much help with this one. Right now, I'm entering the times manually -- > using the the "Segue Start" parameter to specify the length of each cut > -- and will continue to do so unless someone has a better idea :-) > > When I took the SQL dump out of Rivendell, I calculated segue time minus the start time. That was then converted to MM:SS format in the spreadsheet using a formula. > > 1. Since Title and Artist info is saved to the CART table and > RDAirplay plays carts with multiple cuts, it seems logical to me that > RDAirPlay only cares about CARTs not CUTs as far as log generation is > concerned. Is it correct to assume that the (CART) table holds the > critical info for external music scheduling software log generation? > > When tying together most music scheduling and playout systems, you generally use the cart ID to match. Rotating cuts is handled by the playout system. It's the way they do it at $dayjob with GSelector and Genesys. > > 1. I can't find any kind of Rivendell music log in a text format, only > in the SQL database. Does RDAirPlay read it directly from the SQL DB? Or > does it generate a text file somewhere? > > Rivendell does have a text file import option but that's then used to generate the SQL log. > > 1. Which begs the next question... When you merge music in > RDLogManager, is it actually importing your third-party log into SQL for > RDAirPlay to read from? > > Yup, just like a lot of other playout systems do. > > 1. Just finished reading this Wiki > <http://rivendell.tryphon.org/wiki/Importing_External_Logs_into_Rivendell> > and > this wiki > > <http://rivendell.tryphon.org/wiki/Importing_External_logs_into_Rivendell_-_Music_and_Traffic> > on importing music from external software. Right now, in Rivendell, I > specify a Timed(MakeNext), scheduler EVENT on my top of the hour IDs, which > seems to do a pretty good job of keeping me on time and dropping songs and > their associated imaging if I'm running over. All of my Rivendell Events > have "segue" as the default transition. Should I let my pre-merge Rivendell > Clock handle the Top of the Hour ID with the hard start time and drop it > from the first position in my GSelector clock/log to keep things working > the same way? Or can you achieve the same behavior with an external > scheduler? > > We schedule the TOH (clock start at XX:59:40) through Rivendell with the rest of the hour pulled from the GSelector logs in one go. > > 1. What are the absolute required fields from the Rivendell database > for an external music scheduler, like GSelector, to generate a proper > program log for Rivendell to read? Right now, I'm planning on sending: > NUMBER, GROUP, TITLE, ARTIST, ALBUM, LABEL, COMPOSER, and LENGTH -- which > I'm entering manually. > > We only send start time, cart ID, name and length. The latter two are probably not 100% necessary though. > > 1. Does Rivendell have a mechanism for reconciling played music logs > back into GSelector to maintain proper rotation and keep actual play > history vs. scheduled history? > > It's likely there is a mechanism but we don't use it. > > 1. Not using any macros yet, but if/when I do, how is that handled > with an external scheduler? Do they work like carts? Build them in > Rivendell, assign a cart number and schedule the cart with external > scheduler? > > Yup, just match on cart ID again. Hopefully that helps. Regards, Marc.
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
