v4.0.2.14 - stable

This forum will contain general news and announcements made by radio42.
Post Reply
User avatar
radio42
Site Admin
Posts: 4761
Joined: 05 Apr 2012 16:26

v4.0.2.14 - stable

Post by radio42 » 03 Jan 2017 17:10

Version v4.0.2.14 is out!

What's New?
  • Event Import bug-fix
  • updated UI lib version
  • updated Audio lib version
  • New 'Look-Back' global history option
  • new Scheduler Start options added
  • Amazon WebService updated
  • optimized Scheduler DayLightSaving handling
  • Various smaller optimizations
  • Other smaller bug-fixes
  • stable

New 'Look-Back' global history option
See general settings, section 'Logging/Histrory' and click on the Global History 'More...' button...

Look-Ahead 'Back-To-The-Future':
Tracks are so far added to the history and checked against the history at the time when they are scheduled. For any pre-scheduled (e.g. voice tracked) playlists this is the time when you prepare (voice track) them - which might be a couple of days or hours in advance.
This also means, that when a regular program/script now runs right before such a pre-created program/playlist; its entries might not be checked against those contained in the sub-sequent, pre-created one. This is what I would call a 'back-to-the-future' scenario.
If this option is checked the look 'back-to-the-future' is enabled:
When the scheduler is running, a next program is determined anyhow. This next (forthcoming) program will now be examined further (resp. its related script).
If that next script contains any 'LoadPlaylist' script-line(s) - as any pre-created (voice tracked) playlists would be - these will now be resolved and its contained tracks are then added to an internal additional history collection.
As such, any current global history check (as performed by a current playlist) would then automatically be checked also against the forthcoming playlist entries (even if they have been created days ago).

Look-Back 'Back-To-The-Future':
Tracks are so far added to the history and checked against the history at the time when they are scheduled. For any pre-scheduled (e.g. voice tracked) playlists this is the time when you prepare (voice track) them - which might be a couple of days or hours in advance.
This also means, that when a regular program/script now runs right after such a pre-created program/playlist; its entries might not be checked against those contained in the sub-sequent, pre-created one. This is what I would call a 'back-to-the-future' scenario.
If this option is checked the look 'back-to-the-future' is enabled:
When the scheduler is running and a current program is started, the current playback history tracks are then added to an internal additional history collection.
As such, any current global history check (as performed by a current playlist) would then automatically be checked also against the last played entries (even if this was a pre-prepared playlist and was created days ago).


new Scheduler Start options added
The following new 'Scheduler Start Options' have been added (see general settings, section 'Scripts/Scheduler').

ResetProgramScheduler: If checked, the program scheduler will be reset to trigger an already triggered program again, but only, if there is no future scheduled program playlist open.

ResetOverlayScheduler: If checked, the overlay scheduler will be reset to trigger any already triggered overlay again, but only, if there is no future scheduled overlay currently open.

Note: These options are ignored on initial scheduler AutoStart.

In addition 2 new Script Options (see the Script Library Editor when editing a script):
SuppressGlobal/TrackRestrictions: If checked the global scripting resp. all track specific restrictions and rule-set checks will be suppressed for this script.


Amazon WebService updated
AWS changed its API, so the Lookup service was broken the last days. It is now working again.


Optimized Scheduler Daylight-Saving handling
The behavior for Reminders, Programs and Overlays has slight be changed, it they fall in the Daylight Saving Time shift (a non-existing time interval on the Daylight Saving Time start date, usually between 2:00:00 and 2:59:59 AM).
The new behavior is now as followed:

If for a Program Scheduler entry (or Reminder) the 'Start Time' falls into the non-existing time interval, the program is triggered at the end of the Daylight Saving Time shift. Meaning it is directly triggered and executed after the DST shift (so far those programs have been dismissed).

If for an Overlay Scheduler entry the 'Start Time' falls into the non-existing time interval, the overlay is completely dismissed (not triggered; like before).

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests