Hi Andy, Scheduling was almost entirely re-written between v3 and v4 which meant that it's now doing a lot more work than before (not just because there are a lot more rules, but also how AutoTrack looks forward and backward when considering slots). Also because of changes with the scheduling process itself (e.g. that it's scheduling direct to the actual Myriad Scheduled Log rather than to a local file then "sent" to the studio) this changes the time taken, not to mention that it's now using SQL instead of Jet databases these can all add up! However, that all said! - what we have done with AT4 is introduce a lot of better ways to achieve the same end scheduling goals which means that some of the ways you are doing things in v3 are no longer the most efficient way of achieving that aim and that perhaps one of the other rules, or a tweak to the categorisation (types/eras etc!) will give you a massive increase in performance. You can start the diagnostic process yourself by using some of the Scheduling Reports to see why items aren't scheduling - for example the Top Rules Failed per hour report in v4.0.21 and the Tested But Rejected Items reports will often show you that most of the delay is being caused by just one or two specific rules being overly restrictive etc. After that, because every database (like every station!) is unique, the best thing to do is to drop support a line and explain so we can then investigate and take a look at your database itself and make some recommendations on how to optimise the scheduling process.
------------
Peter Jarrett, Technical Director
Broadcast Radio Ltd.Bill Bailey: No win, no fee, no basis in reality. Just a room above a minicab office in Acton and a steady stream of greedy simpletons whose delusion is only matched by their clumsiness
|