Re: [RDD] RD Scheduler codes selections
Thanks Patrick, that's good to hear that has been fixed. If you are trying to schedule say 3 sponsor carts during a break and one is a expired cart then you miss out on a scheduled spot. I know this probably should be handled by a Traffic system but I am trying to set up a very simple system that only has a maximum of 4 current sponsor cart at any one time. Kind regards Stan On 9/10/2019 11:33 am, Patrick Linstruth wrote: Your first issue is fixed in Rivendell 3. Cart expiration dates are handled during play out, not scheduling, which may or may not be the appropriate thing to do. Patrick On Oct 8, 2019, at 7:55 PM, Stan Fotinos wrote: HI all I just created a test event to select carts from a group called "spots" and have specified that it Must have code "drive". What I am finding is if I don't have any carts in the group "spots" that have a scheduler code "drive" assigned, it will still select any cart from this group. Shouldn't this event be empty considering I have no carts in this group that fit the criteria? Also I have noticed that expired carts are also scheduled, should this be part of the selection process? Kind regards -- Stan Fotinos Broadcast Engineer RTRFM 92.1 The Sound Alternative P Please consider the environment before printing my email P (08) 9260 9200 PO Box 842, Mt Lawley 6929 1st Floor, 642 Beaufort St, Mt Lawley 6050 www.rtrfm.com.au ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] RD Scheduler codes selections
Your first issue is fixed in Rivendell 3. Cart expiration dates are handled during play out, not scheduling, which may or may not be the appropriate thing to do. Patrick > On Oct 8, 2019, at 7:55 PM, Stan Fotinos wrote: > > HI all > > I just created a test event to select carts from a group called "spots" and > have specified that it Must have code "drive". > > What I am finding is if I don't have any carts in the group "spots" that have > a scheduler code "drive" assigned, it will still select any cart from this > group. > > Shouldn't this event be empty considering I have no carts in this group that > fit the criteria? > > Also I have noticed that expired carts are also scheduled, should this be > part of the selection process? > > Kind regards > > -- > Stan Fotinos > Broadcast Engineer > > RTRFM 92.1 The Sound Alternative > P Please consider the environment before printing my email > P (08) 9260 9200 > PO Box 842, Mt Lawley 6929 > 1st Floor, 642 Beaufort St, Mt Lawley 6050 > www.rtrfm.com.au > > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] RD Scheduler codes selections
Hi Stan On 9/10/19 3:54 PM, Stan Fotinos wrote: Also I have noticed that expired carts are also scheduled, should this be part of the selection process? They may schedule but they should not play regards Robert ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] RD Scheduler codes selections
HI all I just created a test event to select carts from a group called "spots" and have specified that it Must have code "drive". What I am finding is if I don't have any carts in the group "spots" that have a scheduler code "drive" assigned, it will still select any cart from this group. Shouldn't this event be empty considering I have no carts in this group that fit the criteria? Also I have noticed that expired carts are also scheduled, should this be part of the selection process? Kind regards -- Stan Fotinos Broadcast Engineer RTRFM 92.1 The Sound Alternative P Please consider the environment before printing my email P (08) 9260 9200 PO Box 842, Mt Lawley 6929 1st Floor, 642 Beaufort St, Mt Lawley 6050 www.rtrfm.com.au ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Setup Advice
Are you referring to the "aman" feature that is supposed to handle replication between two servers? (https://github.com/ElvishArtisan/aman/blob/master/README) Is it no longer recommended? Mark Murdock KAMB -Original Message- From: rivendell-dev-boun...@lists.rivendellaudio.org On Behalf Of Cowboy Sent: Tuesday, October 8, 2019 10:27 AM To: Rivendell-Dev Subject: Re: [RDD] Setup Advice On Tue, 8 Oct 2019 11:51:07 -0500 Tom Van Gorkom wrote: > My experience with the DB replication is that if he reboots one of > them, it will stop replicating until re-synced Thank you for that !! We had a "main" server fail a month or two ago, and then discovered that "replication" was at least 14 months out of date ! Methinks you just explained how that happened. -- Cowboy ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Setup Advice
On Tue, 8 Oct 2019 11:51:07 -0500 Tom Van Gorkom wrote: > My experience with the DB replication is > that if he reboots one of them, it will stop replicating until re-synced Thank you for that !! We had a "main" server fail a month or two ago, and then discovered that "replication" was at least 14 months out of date ! Methinks you just explained how that happened. -- Cowboy ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Setup Advice
I wrote two custom scripts, rsa.pl and rsl.pl, to synchronize audio cuts and daily logs from one RD stand-alone system to another. They do not synchronize the rest of the database, but they do insure that a log produced on one system will run on the other. It is possible to use these scripts bi-directionally, i.e. changes to A propagate to B and changes to B propagate to A; however, cart and log deletions do not propagate. Additions and changes will propagate, but deletions cannot, because if they did, it would be impossible to tell the difference between a deletion from one system and an addition to the other. This is a feature that I wish were included in Rivendell itself. Just the other day it saved one of my stations when the sound card in the RD system in the on-air studio went west. We switched to the backup RD system at the transmitter site, which is on the air right now with identical content pending the arrival of the replacement sound card. I can send you copies of these scripts if you think they will be useful. They will not work on RD 3.x, which I am told has a completely different database structure. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил. On Tue, 8 Oct 2019, Tom Van Gorkom wrote: I'm preparing two CentOS 7 Riv 2.19 machines for an LPFM. The owner would like a main airplay and a production machine that syncs with the airplay. I'm looking for good options that he could easily manage since he's not a Linux person. The options I think of are to make one a server and the other a client, or make them both stand-alones that have a scripted audio sync and DB replicator between them. My experience with the DB replication is that if he reboots one of them, it will stop replicating until re-synced which is going to be beyond his ability. I have not played with replication on MariaDB. Perhaps there is a way to automate this that I don't know about. Other suggestions to make this simple and somewhat foolproof? Thanks, Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 www.radioesperanza.com Director of Media Rio Grande Bible Ministries 4300 S US Hwy 281 Edinburg, TX 78539 www.riogrande.edu ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Setup Advice
I'm preparing two CentOS 7 Riv 2.19 machines for an LPFM. The owner would like a main airplay and a production machine that syncs with the airplay. I'm looking for good options that he could easily manage since he's not a Linux person. The options I think of are to make one a server and the other a client, or make them both stand-alones that have a scripted audio sync and DB replicator between them. My experience with the DB replication is that if he reboots one of them, it will stop replicating until re-synced which is going to be beyond his ability. I have not played with replication on MariaDB. Perhaps there is a way to automate this that I don't know about. Other suggestions to make this simple and somewhat foolproof? Thanks, Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 www.radioesperanza.com Director of Media Rio Grande Bible Ministries 4300 S US Hwy 281 Edinburg, TX 78539 www.riogrande.edu ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Yet more Ausioscience weirdness
I have just received from Steve at Audioscience the following message: "Some motherboards fail to recognize ASI67XX, ASI57XX, ASI58XX cards after a reboot or reset. The issue may not occur on all instances of reboots but power cycling the equipment always makes the card visible again." He goes on to say that the problem is that the drivers are not automatically unloaded during shutdown under Linux, as they are under Windows, and he adds that there is a workaround that involves using a script to unload the drivers. He says the permanent solution is to send the cards back to ASI for reprogramming. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил. On Sat, 7 Sep 2019, Rob Landry wrote: OK, so I finally got my ASI5810 cards to work, by upgrading to CentOS 7 and Rivendell 2.19.3 and then installing hpklinux-4.20.10-1.el7.centos.x86_64.rpm. However, if I reboot either machine from the command line or the desktop, the card will no longer be recognized. It will show in lspci, but Rivendell won't see it. If I shut down the machine and power-cycle it, Rivendell can see the card. Oddly, though -- and this may have nothing to do with the price of eggs -- it doesn't seem to work properly in rdlibrary. The play button causes the selected cut to play, but no audio shows on the meter display, and no audio can be heard. Have any of y'all encountered similar symptoms? ROB -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил.___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
