Re: [RDD] Scheduler rules not followed
I followed exactly what you did, but the codes weren't added. ☹ Now back to doing it all manually (about 1200 titles). Verstuurd Van: erm...@studioplume.com Verzonden: woensdag 10 december 2014 18:25 Aan: User_discussion_about_the_Rivendell_Radio_Automation_System > It's actually rather fast: create the new scheduler code newCode, go > to > rdlibrary, select all carts having oldCode, click edit and assign them > > the new code. > I TRIED THIS AFTER YOUR TIP, BUT FOR SOME REASON IT DOESN'T SEEM TO > WORK. ☹ COULD THIS HAVE SOMETHING TO DO WITH THE = USED IN THE > INITIAL TAGS? OR IS THERE A CERTAIN ORDER TO DO THIS IN? I did a short screencast to detail the process: http://www.youtube.com/watch?v=nMCS4kPJM0Y I also tried with a scheduler code containing the "=" sign and it worked the same. . e ___ 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] Scheduler rules not followed
It's actually rather fast: create the new scheduler code newCode, go to rdlibrary, select all carts having oldCode, click edit and assign them the new code. I TRIED THIS AFTER YOUR TIP, BUT FOR SOME REASON IT DOESN'T SEEM TO WORK. ☹ COULD THIS HAVE SOMETHING TO DO WITH THE = USED IN THE INITIAL TAGS? OR IS THERE A CERTAIN ORDER TO DO THIS IN? I did a short screencast to detail the process: http://www.youtube.com/watch?v=nMCS4kPJM0Y I also tried with a scheduler code containing the "=" sign and it worked the same. . e ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Scheduler rules not followed
> But if I'm right, it's not possible to _change_ the scheduler codes, > is it? So this might mean I have to recode my complete database? > Anyway, if it solves the problem, it's worth the work! It's actually rather fast: create the new scheduler code newCode, go to rdlibrary, select all carts having oldCode, click edit and assign them the new code. I tried this after your tip, but for some reason it doesn't seem to work. ☹ Could this have something to do with the = used in the initial tags? Or is there a certain order to do this in? Verstuurd Van: erm...@studioplume.com Verzonden: woensdag 10 december 2014 12:00 Aan: User_discussion_about_the_Rivendell_Radio_Automation_System Hello, > But if I'm right, it's not possible to _change_ the scheduler codes, > is it? So this might mean I have to recode my complete database? > Anyway, if it solves the problem, it's worth the work! It's actually rather fast: create the new scheduler code newCode, go to rdlibrary, select all carts having oldCode, click edit and assign them the new code. About dayparting: the only use i have of dayparting _cuts_ is for specific IDs and for short daily and weekly shows that are either imported manually well in advance or imported "unattendedly" by a bot. To "daypart" certain _carts_ without having them scheduled, my solution is to use (yet another) scheduler code; for example "not_before22h": then in the scheduler rules of all clocks where you dont want those carts scheduled, set "max in a row" 0. About the scheduler breaking rules: (the exact way the scheduler works is still a bit obscure to me, so all this might be wild guesses) it seems to me that your "min. wait" values are too high. I remember reading 'somewhere' that the artist separation and min wait rules are the first to be broken in case the scheduler has a shortage of tracks. Hope it helps. . e > Thanks for your reply, I'll let you know if it has helped. > > Sincerely, > > Peter van Embden > Radio Capelle > The Netherlands > www.radiocapelle.nl [1] > > Verstuurd > > VAN: Robert Jeffares > VERZONDEN: dinsdag 9 december 2014 20:11 > AAN: User_discussion_about_the_Rivendell_Radio_Automation_System > > On 10/12/14 01:55, Peter van Embden wrote: >> For example: due to the Dutch festive of "Sinterklaas" (today, >> december 5), Christmas (M=KERST) songs should not be played > > me thinks Black Peter is having a say in this...!!! > > I have a strong memory that using = in the scheduler code may cause > problems in mysql. > > I avoid all punctuation and symbols like @ & % <>? () in anything that > > runs in mysql because they tend to get interpreted as something else. > > I like the energy level idea. I have a tempo scheduler code which > works > but the energy level adds a fine tuning I have been looking for. > > Changing the scheduler code from E=1 to E1 may produce a change. > > You can create a new scheduler code without the '=' and globally > change > all songs with E=1 to E1 in RDLIBRARY so not too big a pain to test > the > theory. > > regards > > Robert Jeffares > Big Valley Radio > Thames New Zealand > > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > > Links: > -- > [1] http://www.radiocapelle.nl > > ___ > 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___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Scheduler rules not followed
Hello, But if I'm right, it's not possible to _change_ the scheduler codes, is it? So this might mean I have to recode my complete database? Anyway, if it solves the problem, it's worth the work! It's actually rather fast: create the new scheduler code newCode, go to rdlibrary, select all carts having oldCode, click edit and assign them the new code. About dayparting: the only use i have of dayparting _cuts_ is for specific IDs and for short daily and weekly shows that are either imported manually well in advance or imported "unattendedly" by a bot. To "daypart" certain _carts_ without having them scheduled, my solution is to use (yet another) scheduler code; for example "not_before22h": then in the scheduler rules of all clocks where you dont want those carts scheduled, set "max in a row" 0. About the scheduler breaking rules: (the exact way the scheduler works is still a bit obscure to me, so all this might be wild guesses) it seems to me that your "min. wait" values are too high. I remember reading 'somewhere' that the artist separation and min wait rules are the first to be broken in case the scheduler has a shortage of tracks. Hope it helps. . e Thanks for your reply, I'll let you know if it has helped. Sincerely, Peter van Embden Radio Capelle The Netherlands www.radiocapelle.nl [1] Verstuurd VAN: Robert Jeffares VERZONDEN: dinsdag 9 december 2014 20:11 AAN: User_discussion_about_the_Rivendell_Radio_Automation_System On 10/12/14 01:55, Peter van Embden wrote: For example: due to the Dutch festive of "Sinterklaas" (today, december 5), Christmas (M=KERST) songs should not be played me thinks Black Peter is having a say in this...!!! I have a strong memory that using = in the scheduler code may cause problems in mysql. I avoid all punctuation and symbols like @ & % <>? () in anything that runs in mysql because they tend to get interpreted as something else. I like the energy level idea. I have a tempo scheduler code which works but the energy level adds a fine tuning I have been looking for. Changing the scheduler code from E=1 to E1 may produce a change. You can create a new scheduler code without the '=' and globally change all songs with E=1 to E1 in RDLIBRARY so not too big a pain to test the theory. regards Robert Jeffares Big Valley Radio Thames New Zealand ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev Links: -- [1] http://www.radiocapelle.nl ___ 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] Scheduler rules not followed
That's the whole point: audio is not available, because I dayparted it with RDLibrary, but outside those hours the song still gets scheduled, which sometimes causes a music shortage. Sincerely, Peter van Embden. Verstuurd Van: Robert Jeffares Verzonden: dinsdag 9 december 2014 19:58 Aan: User_discussion_about_the_Rivendell_Radio_Automation_System On 10/12/14 01:55, Peter van Embden wrote: > some songs are only available 00.00-06.00, due to explicit content The day parts get set in rdlibrary in the cut itself [double click cart;double click the cut;tweak] regards Robert ___ 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] Scheduler rules not followed
Nice pun on Black Pete, haha! I'll give it a try though. But if I'm right, it's not possible to change the scheduler codes, is it? So this might mean I have to recode my complete database? Anyway, if it solves the problem, it's worth the work! Thanks for your reply, I'll let you know if it has helped. Sincerely, Peter van Embden Radio Capelle The Netherlands www.radiocapelle.nl Verstuurd Van: Robert Jeffares Verzonden: dinsdag 9 december 2014 20:11 Aan: User_discussion_about_the_Rivendell_Radio_Automation_System On 10/12/14 01:55, Peter van Embden wrote: > For example: due to the Dutch festive of "Sinterklaas" (today, > december 5), Christmas (M=KERST) songs should not be played me thinks Black Peter is having a say in this...!!! I have a strong memory that using = in the scheduler code may cause problems in mysql. I avoid all punctuation and symbols like @ & % <>? () in anything that runs in mysql because they tend to get interpreted as something else. I like the energy level idea. I have a tempo scheduler code which works but the energy level adds a fine tuning I have been looking for. Changing the scheduler code from E=1 to E1 may produce a change. You can create a new scheduler code without the '=' and globally change all songs with E=1 to E1 in RDLIBRARY so not too big a pain to test the theory. regards Robert Jeffares Big Valley Radio Thames New Zealand ___ 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] Scheduler rules not followed
On 10/12/14 01:55, Peter van Embden wrote: For example: due to the Dutch festive of "Sinterklaas" (today, december 5), Christmas (M=KERST) songs should not be played me thinks Black Peter is having a say in this...!!! I have a strong memory that using = in the scheduler code may cause problems in mysql. I avoid all punctuation and symbols like @ & % <>? () in anything that runs in mysql because they tend to get interpreted as something else. I like the energy level idea. I have a tempo scheduler code which works but the energy level adds a fine tuning I have been looking for. Changing the scheduler code from E=1 to E1 may produce a change. You can create a new scheduler code without the '=' and globally change all songs with E=1 to E1 in RDLIBRARY so not too big a pain to test the theory. regards Robert Jeffares Big Valley Radio Thames New Zealand ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Scheduler rules not followed
On 10/12/14 01:55, Peter van Embden wrote: some songs are only available 00.00-06.00, due to explicit content The day parts get set in rdlibrary in the cut itself [double click cart;double click the cut;tweak] regards Robert ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Scheduler rules not followed
Hello! We're filling our database more and more and with that I found it was time to change the rules. But Rivendell doesn't quite listen to those rules I set. My set of rules is in this picture: http://nl.tinypic.com/r/35l6mfs/8. All clocks of the day have these rules. I actually only have 3 clocks for the day: one for 00.00-01.00, one for 01.00-23.00 and one for 23.00-00.00. This way we don't have any hiccups around midnight and still have the news floating (but that's another story, if you're interested, I'll make a seperate thread for that). The music is selected from 2 events: the first song of the hour must have code E=4 (I like to schedule music according to their energy level), the rest of the hour songs are selected from "all music", which should be done according to attached set of rules. Which it doesn't! Every two songs a jingle or ident is played, which have some codes too. For example: due to the Dutch festive of "Sinterklaas" (today, december 5), Christmas (M=KERST) songs should not be played. The rule is now set to "0" "1". That rule will be changed next sunday to "1" "25", so from monday on Christmas songs may be scheduled with approx 2 per hour. But it's playing Christmas songs already. For some reason, if you take a look at the rules, Rivendell manages to play 4 "2010s" in a row. This is not supposed to happen. And I tried to create a "20 years apart" rule, so music should vary between <1970s to 2010s. Also the rule for "current hits" (R=CUR) is broken a lot! Now set to "1" "50", this morning 4 current hits were played in one hour. A typical song has 11 codes, defining the era (songs from the 1950s, 1960s and 1970s also have the code 1900s, which is leading as you can see), level of overall enery (E=1-5), level of intro energy (I=1-5), level of outtro enery (O=1-5), language (where everything that's NOT English also has the code L=ANDERS, so I could set a rule to pick a non-English song every two other songs, but still vary in what language that can be), source (M=..., so it's easy to track where the music is from in order to be able to replace less quality with better quality if possible), and so on, you can see it in the attachment. Did I do anything wrong? Did I miss something? Doesn't our version of Rivendell support this many codes (we're running 2.6.0 for about a year now)? Help me please! In my head these are a quite perfect set of rules! And with a database of 700 songs and growing, you'd say there's plenty of room for variation. Oh, and there's another tiny issue: some songs are only available 00.00-06.00, due to explicit content (i.e. Cee Lo Green - Fuck You), but are scheduled during the day, which then leaves a gap in the schedule. Doesn't the scheduler reckon with that? And if so: why not? Thanks for reading, I hope you can help me with finding a solution for this. Sincerely, Peter van Embden Radio Capelle The Netherlands www.radiocapelle.nl Verstuurd___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev