Yes, we let rdlogmanager choose .. It's set as a cron job every night, so it doesn't really matter how long it takes. But sometimes -if i have changed things- i have to do it manually, and it takes ages :)
what do you use Powergold ? The biggest issue that I have is that rdlogmanager uses -last played- as a parameter. Let's say one record A is up to be played => rdlogmanager makes a log for 4 days from now, and schedules record A. BUT tomorrow, when rdlogmanager makes a log for 5 days from now, record A still hasn't been played, thus it schedules record A And so on .. If record A is an evergreen, no problem.. But if record A is a very very low rotation record, it will stand out. And that is a problem, where i don't have a solution for. Maybe an external scheduler ? but i would prefer it to run under linux, and to be free .. And that narrows it down to nearly zero :( We are a small community radio (22k listeners), and running on volanteers Regards, Peter 2013/5/14 Rob Landry <41001...@interpring.com> > > Are you using rdlogmanager to choose songs? I have one system at a station > that doies that, and it takes 25 minutes to generate a log. On another > station that merges a separate music log, generating a log is virtually > instantaneous. > > > Rob > > On Sun, 12 May 2013, Peter Claes wrote: > > > Guys, > > > > How long does it take to generate a log on average ? > > > > 1.5 hours, would that be normal ? > > > > Regards, > > Peter > > > > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
