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
