v4.0.1.52 - stable

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

v4.0.1.52 - stable

Post by radio42 » 05 Aug 2016 23:07

Version is out!

What's New?
  • New control-commands added
  • New 'Don't Repeat in X days' track restriction rule added
  • New 'Global Restrictions...' added (extended global script rules)
  • Initial FTE backtime adjustment calculation bug-fix
  • Various smaller optimizations
  • Other smaller bug-fixes
  • stable
The global song history settings can now be found in the general settings under 'Logging/History'.

New 'Don't Repeat in X days' track restriction rule added
The Track related Restrictions have been enhanced by another rule (e.g. see TAG Editor, 'Other' tab)
Don't Repeat in X days: Defines the number of days in which this track should not be repeated.

New 'Global Restrictions...' added (extended global script rules)
Beside script related Rules, you can now also define Global Scripting Restrictions - see in general settings, section 'Logging/History', and click on the global 'Restrictions...' button.
Global Restriction Rules allow you to not schedule more than a certain number of tracks all matching the same meta-data filter condition rule in a row.

Scope: If set to Global, the rule is evaluated after the actual script-line processing, meaning a related matching track might be suppressed after. If set to ScriptLine scope, the evaluation takes place during the processing and the related script-line will be executed again to find a non-matching track (up until a maximum number of retries).

Track Condition: The track condition is a mata-data based filter rule expression, which much match in order to suppress the track.

Applies To: Defined to which script-line modes this rule applies to. This allows you to exclude the rule from certain type of script-lines (e.g. FTE's, LoadFolder or Cartwall results etc.)

Count Back: The number of directly preceeding (historical) global song history entries which much also match the given track filter condition. E.g. 5 in order to check, that not more then 5 tracks in a ro do match this condition.

In addition you can also specify, that a certain track when once played will not be scheduled again the next time in the same hour.
See 'Do not play a track (the next time it will be scheduled) again in the same hour plus/minus:...':
The plus/minus hour value allows you to adjust the total time frame in which the track should not be repeated. E.g. a value of 0 means the exact hour. A value of 1 denotes a 3 hour frame, a value of 2 a 5 hour and a value of 3 a 7 hour time frame.
Note: This is a ScriptLine rule which only applies to Random or Sequential modes.

Dynamic Scripting
Even if already implemented for quite some time, I would just like to emphasize again, the dynamic scripting is also possible.
This means, that you can add rules (resp. a filter) to a script-line, which contains attributes from your last scheduled track (your previous executed script-line). Meaning you create a script-line filter condition which is based on the previous scheduled track.

In order to do so, you can simply use any standard track macros within script-line filters! Any regular track macro like for example ${genre} will then be replaced by the data of the last scheduled track.
E.g. the following filter would make sure, that the Genre of the current script-like is the same as the genre of the previous scheduled track; but the rating must be different:
~[Genre] == '${genre}' And [Rating] <> '${rating}'

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests