I have to say as a similar feature, I would love to be able to schedule recordings in rdcatch via a macro. Currently we can start and stop the record deck with a macro, but what I'd like to be able to do is every day just before midnight run a script that will setup the next day's record schedule in rdcatch.
Here is my use case. For a community station that I work with, we have a programme grid on the website. Currently I have an audio logger that I wrote years ago that every day just before midnight it pulls the next day's programme schedule from the website and sets up cron jobs to record each show into an audio file with the show name, show id, date and time. If there are changes to the programme grid, then as long as it isn't a same-day change, then it'll be automatically picked up. I wrote the system years ago in OS/2 Warp using REXX and it just plain works. I'd love to replicate the same thing in Rivendell and RDCatch. I know with back-end scripting and the start / stop record deck macro I can achieve a lot of what I want to do, but I'd still be relying on CRON jobs (or creating a separate log in Rivendell each day which runs for the entire purpose of calling the rdcatch record / stop record macros) for the record start/stop. It would be a lot cleaner if I could just run a script every day before midnight to send RDCatch the entire record schedule for the next day, and then just let RDCatch do its thing. You'd then be able to pull up rdcatch and see exactly what it is currently recording with what is coming up next. Anyways, just some thoughts Lorne Tyndale > > > Is there a way to bulk import a bunch of RDCatch events or have a feature > in Rivendell in the next release to take a xml like sheet or a .txt file > and ingest a bunch of RDCatch events and automatically start running based > off of the day and time set in the file defined based in RDCatch? > > I am programming almost 20 shows weekly which RDCatch can grab but I am not > liking having to manually setting it up one-by-one since some shows are 2 > to 5 hours long and it's a long process. > Thanks in advance! > > Ryan<hr>_______________________________________________ > 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
