Re: [RDD] Scheduler codes time taken
On Fri, 2019-03-22 at 09:33 +0800, Stan Fotinos wrote: > Thank you for the clarification, so all the improvements should be > already implemented in the version I am testing with 2.19.3. As > Cliff > suggested I did try a modern PC with a very fast processor and lots > of > RAM, it did reduce the time taken by 50 minutes ( it previously took > 2 > hours for 24 hrs of music) It still appears to be a long time > considering the low complexity of the set up... Thank you for the update, Stan. Please also consider opening an issue report detailing the specifics at Github ( https://github.com/ElvishArtisan/rivendell/issues) -- that way, itwon't get lost in the shuffle. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | The First Rule of Program Optimization: Don't do it! The Second | | Rule of Program Optimization (for experts only!): Don't do it yet! | | | |-- Michael Jackson | |-| ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Scheduler codes time taken
Hi Fred Thank you for the clarification, so all the improvements should be already implemented in the version I am testing with 2.19.3. As Cliff suggested I did try a modern PC with a very fast processor and lots of RAM, it did reduce the time taken by 50 minutes ( it previously took 2 hours for 24 hrs of music) It still appears to be a long time considering the low complexity of the set up... Thanks Stan On 21/03/2019 4:07 am, Fred Gleason wrote: On Tue, 2019-03-19 at 10:00 -0700, Lorne Tyndale wrote: Yes, as I recall there were some optimizations that were initially tested in V2, but then made their way into V3. From what I understand the changes make use of temporary MySQL tables when creating the log instead of doing things in arrays. The optimizations were part of the final batch of improvements submitted by Alban Peigner before Tryphon ceased operations. They first appeared in v2.12.0, and improved music scheduler performance when generating logs by an order of magnitude or more. Thus, an update to the current stable version (v2.19.3) should cure the OP's reported bottleneck. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ 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 codes time taken
Hi Rich Just the one group and one scheduler code and 20 tracks per hour. I have simplified the clocks just to see if it makes a difference, the only thing that does is if I only us groups and no codes at all. It appears from the responses that some are able to create logs with scheduler codes reasonable fast but I'm just wondering if it has more to do with hardware or the software side of things. I'll be testing on a faster system at the end of the week and I'll report back with my findings. Kind regards Stan On 20/03/2019 4:54 am, Rich Stivers wrote: Stan: How many scheduler codes do you use per clock? I have about 25 scheduler codes but I don't use all of them for any given clock. My most complicated clock takes about 5 minutes to generate a 24-hour log. Rich On 3/19/2019 04:37, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 codes time taken
Hi Cliff Thank you, every bit off information helps. Five minutes is much better than two hours. Regards Stan On 20/03/2019 3:48 am, Cliff Osbourne wrote: We use scheduler codes on Quasar and generating logs takes nowhere near that long, a matter of minutes in fact. Granted each day includes a number of pre-recorded shows and we have a pretty big library of tracks but even so.. All music is in a Group called 'Music' and each track has a code for its decade. The clocks contain events which call for tracks with a particular code but I've never had to wait more than about five minutes for a log to generate. Where using 2.19.3 on Cent OS-7 on a dual core machine with 8GB of ram. Sorry not to offer any solutions but I hope our experience offers some hope. Regards Cliff On 19/03/2019 19:00, Robert Jeffares wrote: Stan, The more options or criteria required to make a selection from the library the longer it will take. If you have 2000 songs it will be faster then if you have 20,000 2 hours for a days log is 'typical' on a computer with a basic amount of ram and an early 64 bit processor. You can make it go faster by using lots of RAM >8GB [and fast ram] and the latest Intel processor. We cut creation time by about 1/4 with a high spec machine. It cost! Most of our machines are ex lease In the normal scheme of things we run log creation 8 days in advance scheduled to commence at 1am and if it takes the computer a couple of hours I don't care as I am fast asleep! There is a system promoted by it's creator as 'faster than Rivendell' to create a log which it is, because it does not use MySQL or any other database. Personally I would rather have all the features MySQL enables. R On 3/20/19 12:37 AM, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Scheduler codes time taken
Hi Robert I will try creating a log using a much more powerful system. I am am using a library of approximately 60,000 which I did think I might have an impact but I'm only using very few options, just the one scheduler code per hour and a single group. On 20/03/2019 3:00 am, Robert Jeffares wrote: Stan, The more options or criteria required to make a selection from the library the longer it will take. If you have 2000 songs it will be faster then if you have 20,000 2 hours for a days log is 'typical' on a computer with a basic amount of ram and an early 64 bit processor. You can make it go faster by using lots of RAM >8GB [and fast ram] and the latest Intel processor. We cut creation time by about 1/4 with a high spec machine. It cost! Most of our machines are ex lease In the normal scheme of things we run log creation 8 days in advance scheduled to commence at 1am and if it takes the computer a couple of hours I don't care as I am fast asleep! There is a system promoted by it's creator as 'faster than Rivendell' to create a log which it is, because it does not use MySQL or any other database. Personally I would rather have all the features MySQL enables. R On 3/20/19 12:37 AM, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 codes time taken
One of the tools we used to improve and reduce the time generating complicated logs was mysqltuner. Optimizing mysql for which in some cases you have to increase RAM has effect.Verzonden vanaf mijn Samsung-apparaat Oorspronkelijk bericht Van: Rich Stivers Datum: 19-03-2019 21:54 (GMT+01:00) Aan: rivendell-dev@lists.rivendellaudio.org Onderwerp: Re: [RDD] Scheduler codes time taken Stan: How many scheduler codes do you use per clock? I have about 25 scheduler codes but I don't use all of them for any given clock. My most complicated clock takes about 5 minutes to generate a 24-hour log. Rich On 3/19/2019 04:37, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 codes time taken
Stan: How many scheduler codes do you use per clock? I have about 25 scheduler codes but I don't use all of them for any given clock. My most complicated clock takes about 5 minutes to generate a 24-hour log. Rich On 3/19/2019 04:37, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 codes time taken
We use scheduler codes on Quasar and generating logs takes nowhere near that long, a matter of minutes in fact. Granted each day includes a number of pre-recorded shows and we have a pretty big library of tracks but even so.. All music is in a Group called 'Music' and each track has a code for its decade. The clocks contain events which call for tracks with a particular code but I've never had to wait more than about five minutes for a log to generate. Where using 2.19.3 on Cent OS-7 on a dual core machine with 8GB of ram. Sorry not to offer any solutions but I hope our experience offers some hope. Regards Cliff On 19/03/2019 19:00, Robert Jeffares wrote: Stan, The more options or criteria required to make a selection from the library the longer it will take. If you have 2000 songs it will be faster then if you have 20,000 2 hours for a days log is 'typical' on a computer with a basic amount of ram and an early 64 bit processor. You can make it go faster by using lots of RAM >8GB [and fast ram] and the latest Intel processor. We cut creation time by about 1/4 with a high spec machine. It cost! Most of our machines are ex lease In the normal scheme of things we run log creation 8 days in advance scheduled to commence at 1am and if it takes the computer a couple of hours I don't care as I am fast asleep! There is a system promoted by it's creator as 'faster than Rivendell' to create a log which it is, because it does not use MySQL or any other database. Personally I would rather have all the features MySQL enables. R On 3/20/19 12:37 AM, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 codes time taken
Stan, The more options or criteria required to make a selection from the library the longer it will take. If you have 2000 songs it will be faster then if you have 20,000 2 hours for a days log is 'typical' on a computer with a basic amount of ram and an early 64 bit processor. You can make it go faster by using lots of RAM >8GB [and fast ram] and the latest Intel processor. We cut creation time by about 1/4 with a high spec machine. It cost! Most of our machines are ex lease In the normal scheme of things we run log creation 8 days in advance scheduled to commence at 1am and if it takes the computer a couple of hours I don't care as I am fast asleep! There is a system promoted by it's creator as 'faster than Rivendell' to create a log which it is, because it does not use MySQL or any other database. Personally I would rather have all the features MySQL enables. R On 3/20/19 12:37 AM, Stan Fotinos wrote: Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ 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 codes time taken
Thank you Lorne, it sounds like music logs will be created using a cron job until version 3 is ready. > On 20 Mar 2019, at 1:00 am, Lorne Tyndale wrote: > > Yes, as I recall there were some optimizations that were initially > tested in V2, but then made their way into V3. From what I understand > the changes make use of temporary MySQL tables when creating the log > instead of doing things in arrays. > > Lorne Tyndale > >> >> There have been some optimizations made to scheduler in Rivendell 3. I'm not >> aware of any issues with scheduler codes in the 2.x branch, but the stack >> that keeps track of carts for artist/title separation grows indefinitely >> which could severely slow down log generation. Rivendell 3 purges the stack >> during maintenance runs which helps to keep log generation quick. >> >> Our Rivendell 3 beta system creates 24 hour logs in under a minute. >> >> — >> Patrick >> patr...@scnv.net >> >> >> >>> On Mar 19, 2019, at 9:22 AM, Chuck wrote: >>> >>> We're still on v2.10.3, but yes, it takes 4 hours to create one day's >>> music log of 432 songs using scheduler codes to separate rock and R >>> We run 2 logs, one music only, the other stopsets and programs with >>> macros to switch between them. On the other hand, takes only about 2 >>> minutes to create a day's stopset log which does not use scheduler >>> codes. >>> >>> --Chuck W. >>> >>> On Tue, 19 Mar 2019 19:37:44 +0800 >>> Stan Fotinos wrote: >>> Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day?s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan >>> >>> ___ >>> 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 ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Scheduler codes time taken
Hi Patrick I have also experimented with the track separation turn completely off but the result is the same for me. But it does sound like for what you are saying that version 3 maybe addressing some issue with this. Thanks Stan > On 20 Mar 2019, at 12:49 am, Patrick wrote: > > There have been some optimizations made to scheduler in Rivendell 3. I'm not > aware of any issues with scheduler codes in the 2.x branch, but the stack > that keeps track of carts for artist/title separation grows indefinitely > which could severely slow down log generation. Rivendell 3 purges the stack > during maintenance runs which helps to keep log generation quick. > > Our Rivendell 3 beta system creates 24 hour logs in under a minute. > > — > Patrick > patr...@scnv.net > > > >> On Mar 19, 2019, at 9:22 AM, Chuck wrote: >> >> We're still on v2.10.3, but yes, it takes 4 hours to create one day's >> music log of 432 songs using scheduler codes to separate rock and R >> We run 2 logs, one music only, the other stopsets and programs with >> macros to switch between them. On the other hand, takes only about 2 >> minutes to create a day's stopset log which does not use scheduler >> codes. >> >> --Chuck W. >> >> On Tue, 19 Mar 2019 19:37:44 +0800 >> Stan Fotinos wrote: >> >>> Hi all >>> >>> I have just experimented using scheduler codes to create music >>> clocks. What I am finding is that it takes approximately 5 mins to >>> create 1 hour with 20 music tracks per hour and approximately 2hrs to >>> create to create a day?s music log. >>> >>> If I only use a group or groups with no codes it takes approximately >>> 30 seconds to create an hour clock. >>> >>> Could some one please tell me if this is the amount it should take to >>> create 20 tracks per hour? Anyone else experienced anything similar? >>> >>> Centos 7 Rivendell 2.19.3 >>> >>> Thank you >>> >>> Stan >> >> ___ >> 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 codes time taken
Yes, as I recall there were some optimizations that were initially tested in V2, but then made their way into V3. From what I understand the changes make use of temporary MySQL tables when creating the log instead of doing things in arrays. Lorne Tyndale > > There have been some optimizations made to scheduler in Rivendell 3. I'm not > aware of any issues with scheduler codes in the 2.x branch, but the stack > that keeps track of carts for artist/title separation grows indefinitely > which could severely slow down log generation. Rivendell 3 purges the stack > during maintenance runs which helps to keep log generation quick. > > Our Rivendell 3 beta system creates 24 hour logs in under a minute. > > — > Patrick > patr...@scnv.net > > > > > On Mar 19, 2019, at 9:22 AM, Chuck wrote: > > > > We're still on v2.10.3, but yes, it takes 4 hours to create one day's > > music log of 432 songs using scheduler codes to separate rock and R > > We run 2 logs, one music only, the other stopsets and programs with > > macros to switch between them. On the other hand, takes only about 2 > > minutes to create a day's stopset log which does not use scheduler > > codes. > > > > --Chuck W. > > > > On Tue, 19 Mar 2019 19:37:44 +0800 > > Stan Fotinos wrote: > > > >> Hi all > >> > >> I have just experimented using scheduler codes to create music > >> clocks. What I am finding is that it takes approximately 5 mins to > >> create 1 hour with 20 music tracks per hour and approximately 2hrs to > >> create to create a day?s music log. > >> > >> If I only use a group or groups with no codes it takes approximately > >> 30 seconds to create an hour clock. > >> > >> Could some one please tell me if this is the amount it should take to > >> create 20 tracks per hour? Anyone else experienced anything similar? > >> > >> Centos 7 Rivendell 2.19.3 > >> > >> Thank you > >> > >> Stan > > > > ___ > > 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 codes time taken
Thank you Chuck, I am happy it’s not just my setup. I do find it strange that when I use groups to seperate the music genres instead of scheduler codes the logs are created considerably faster. > On 20 Mar 2019, at 12:22 am, Chuck wrote: > > We're still on v2.10.3, but yes, it takes 4 hours to create one day's > music log of 432 songs using scheduler codes to separate rock and R > We run 2 logs, one music only, the other stopsets and programs with > macros to switch between them. On the other hand, takes only about 2 > minutes to create a day's stopset log which does not use scheduler > codes. > > --Chuck W. > > On Tue, 19 Mar 2019 19:37:44 +0800 > Stan Fotinos wrote: > >> Hi all >> >> I have just experimented using scheduler codes to create music >> clocks. What I am finding is that it takes approximately 5 mins to >> create 1 hour with 20 music tracks per hour and approximately 2hrs to >> create to create a day?s music log. >> >> If I only use a group or groups with no codes it takes approximately >> 30 seconds to create an hour clock. >> >> Could some one please tell me if this is the amount it should take to >> create 20 tracks per hour? Anyone else experienced anything similar? >> >> Centos 7 Rivendell 2.19.3 >> >> Thank you >> >> Stan > > ___ > 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 codes time taken
There have been some optimizations made to scheduler in Rivendell 3. I'm not aware of any issues with scheduler codes in the 2.x branch, but the stack that keeps track of carts for artist/title separation grows indefinitely which could severely slow down log generation. Rivendell 3 purges the stack during maintenance runs which helps to keep log generation quick. Our Rivendell 3 beta system creates 24 hour logs in under a minute. — Patrick patr...@scnv.net > On Mar 19, 2019, at 9:22 AM, Chuck wrote: > > We're still on v2.10.3, but yes, it takes 4 hours to create one day's > music log of 432 songs using scheduler codes to separate rock and R > We run 2 logs, one music only, the other stopsets and programs with > macros to switch between them. On the other hand, takes only about 2 > minutes to create a day's stopset log which does not use scheduler > codes. > > --Chuck W. > > On Tue, 19 Mar 2019 19:37:44 +0800 > Stan Fotinos wrote: > >> Hi all >> >> I have just experimented using scheduler codes to create music >> clocks. What I am finding is that it takes approximately 5 mins to >> create 1 hour with 20 music tracks per hour and approximately 2hrs to >> create to create a day?s music log. >> >> If I only use a group or groups with no codes it takes approximately >> 30 seconds to create an hour clock. >> >> Could some one please tell me if this is the amount it should take to >> create 20 tracks per hour? Anyone else experienced anything similar? >> >> Centos 7 Rivendell 2.19.3 >> >> Thank you >> >> Stan > > ___ > 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 codes time taken
We're still on v2.10.3, but yes, it takes 4 hours to create one day's music log of 432 songs using scheduler codes to separate rock and R We run 2 logs, one music only, the other stopsets and programs with macros to switch between them. On the other hand, takes only about 2 minutes to create a day's stopset log which does not use scheduler codes. --Chuck W. On Tue, 19 Mar 2019 19:37:44 +0800 Stan Fotinos wrote: > Hi all > > I have just experimented using scheduler codes to create music > clocks. What I am finding is that it takes approximately 5 mins to > create 1 hour with 20 music tracks per hour and approximately 2hrs to > create to create a day?s music log. > > If I only use a group or groups with no codes it takes approximately > 30 seconds to create an hour clock. > > Could some one please tell me if this is the amount it should take to > create 20 tracks per hour? Anyone else experienced anything similar? > > Centos 7 Rivendell 2.19.3 > > Thank you > > Stan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Scheduler codes time taken
Hi all I have just experimented using scheduler codes to create music clocks. What I am finding is that it takes approximately 5 mins to create 1 hour with 20 music tracks per hour and approximately 2hrs to create to create a day’s music log. If I only use a group or groups with no codes it takes approximately 30 seconds to create an hour clock. Could some one please tell me if this is the amount it should take to create 20 tracks per hour? Anyone else experienced anything similar? Centos 7 Rivendell 2.19.3 Thank you Stan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
