At the time you wrote the message I was actually writing a little script to pull this information from the DB. The "now" and "next" information for the metadata works well, but I wanted a little more info on one page about everything that's coming up in the next hour. Each daily log that's created is saved and updated as a table in the database. "EXT_START_TIME" holds the expected start and "EVENT_LENGTH" holds the event length surprisingly. You have to cross reference the "CART_NUMBER" with the "CARTS" table to get the title, artist etc. Perhaps that's what you were looking for?
TC -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Hoggins! Sent: Saturday, June 28, 2014 9:01 AM To: [email protected] Subject: Re: [RDD] About RLM fields Answering to myself once more. Nevermind, I figured out how to deal with new timestamps. It might be useful to have those new variables, though. Have a nice week-end ! Le 28/06/2014 12:36, Hoggins! a écrit : > Also, as part of these fields, is there a way to get the event length > until transition ? It might be quite different from the actual event length. > > Thanks a lot ! > > Le 28/06/2014 12:12, Hoggins! a écrit : >> Hello, >> >> I'm looking for a value, and I don't know if it's available as part >> of the RLM fields. >> I use rlm_udp with great success, everything works fine. >> >> I would like to know if there is the possibility to have the >> timestamp an event started at. >> Currently, I'm retrieving this information simply by looking at the >> current timestamp on the receiver side of my UDP packet sending, but >> it's not accurate, because sometimes Rivendell will send this packet >> when my event is still playing, and I will get a new timestamp. >> >> Looking at the doc >> >> ; %n %N The Rivendell cart number >> ; %h %H Event length (in milliseconds) >> ; %g %G The Rivendell group name >> ; %t %T Title >> ; %a %A Artist >> ; %l %L Album >> ; %y %Y Year >> ; %b %B Record Label >> ; %c %C Client >> ; %e %E Agency >> ; %m %M Composer >> ; %p %P Publisher >> ; %u %U User Definied >> >> We could have : >> >> ; %x %X The time an event is fired / next event is supposed to fire. >> >> That would be soo helpful to me. And maybe it already exists but it >> is not documented yet ? >> >> Thanks ! >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
