On Tue, May 14, 2019 at 4:53 PM Patrick Linstruth <[email protected]> wrote:
> I have not used Replication. At this point in time, I'm mostly working on > the RDNexus model and have some command line utilities running. > > Dealing with the bi-directional library updates has been fairly > straight-forward, as was the "as played" info once I added some playout > notifications and timestamp data to RDNotification and RDAirplay. It is the > scheduler that has a very specific methodology based on importing a flat > file at the time the person wants to do the merge. The mere presence of a > file turns the red lights green that data is available for a merge. The > concept of the "live log" updates you mentioned doesn't seem to fit the > existing architecture. That's why I'm asking so many questions about the > logs and merging, since that's an area I have not spent a lot of time in. > > I'm going to continue working on the RDNexus glue between Rivendell and > Nexus using command line tools, and once that interface is ironed out, > start looking at the actual integration. > > At this point I'm leaning towards an rdnexusd daemon and a separate > admin/configuration from Replication to handle external schedulers. > > Hopefully we get more feedback on the subject. > Well, I don't think this will be very useful feedback at this time, but I have had some working experience with Nexus and another automation system. We liked it overall and liked the ability to run a program on multiple machines showing what was playing in an air studio in real time. (IIRC, it has been a good while now.) > > Patrick > all the best, drew -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
