Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Rick
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:

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Rich Stivers
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

[RDD] Subscription to list

2019-03-19 Thread Pedro Pancorbo Arroyo
Dear Srs. I'd like to be part of this list. Thanks so much. Best regards, PP ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Cliff Osbourne
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Robert Jeffares
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Lorne Tyndale
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Patrick
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

Re: [RDD] Scheduler codes time taken

2019-03-19 Thread Chuck
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

[RDD] Scheduler codes time taken

2019-03-19 Thread Stan Fotinos
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