v3.0.13.1 - stable

This forum will contain general news and announcements made by radio42.
Post Reply
XTended

Re: v3.0.13.0 - stable

Post by XTended » 13 Mar 2014 18:02

GREAT!!!

User avatar
sun7radio
Posts: 79
Joined: 06 Mar 2014 10:14

Re: v3.0.13.0 - stable

Post by sun7radio » 13 Mar 2014 20:51

Excellent ! Thanks!

You don't mention it but I guess the ${fix_...} macros issue has been resolved ?
(I'll test it anyway :))

Cheers,
Guy.

User avatar
radio42
Site Admin
Posts: 5561
Joined: 05 Apr 2012 16:26

Re: v3.0.13.1 - stable

Post by radio42 » 13 Mar 2014 21:56

v3.0.13.1: This fixes a small multi-select issue with the media libs.

User avatar
radio42
Site Admin
Posts: 5561
Joined: 05 Apr 2012 16:26

Re: v3.0.13.0 - stable

Post by radio42 » 13 Mar 2014 21:58

sun7radio wrote:You don't mention it but I guess the ${fix_...} macros issue has been resolved?
It's mentioned in your related Post where you raise the bug ;-)

User avatar
hdradio
Posts: 622
Joined: 10 Apr 2012 17:36

Re: v3.0.13.1 - stable

Post by hdradio » 13 Mar 2014 22:16

In addition the script history now should actually only contain effectively used entries. E.g. un-played playlist entries are now removed from the script and global history once a scheduled playlist is closed by the scheduler when a new program is started. Entries which are removed due to a script rule are now also removed from both histories accordingly.
This is not true.
I run the script. Let it play 1st song (5 more were queued). Then closed that playlist.
I went to script and click on Max History label. I see all the queued songs of the (closed) playlist.

User avatar
radio42
Site Admin
Posts: 5561
Joined: 05 Apr 2012 16:26

Re: v3.0.13.1 - stable

Post by radio42 » 13 Mar 2014 22:45

Please read above again (carefully)...
...un-played playlist entries are now removed from the script and global history once a scheduled playlist is closed by the scheduler when a new program is started.

So did you close the playlist manually or was it the scheduler as written above? Manual things can not be tracked correctly...

I just made a quick test again and it worked as expected. Just let the scheduler start one program and finish it and start another program...once the previous program/script was closed by the scheduler the un-played entries (which are those not being loaded to any DJ Player yet) are removed from the global and script history.

User avatar
hdradio
Posts: 622
Joined: 10 Apr 2012 17:36

Re: v3.0.13.1 - stable

Post by hdradio » 13 Mar 2014 22:50

So the secret here is the closed by the scheduler when a new program is started.

Yes I manually closed that playlist.
But the fact is that those entries have not played and should not be logged as played.

User avatar
radio42
Site Admin
Posts: 5561
Joined: 05 Apr 2012 16:26

Re: v3.0.13.1 - stable

Post by radio42 » 13 Mar 2014 23:46

It is no secret, that's how it works...as said: manual things can not be automated...

User avatar
radio42
Site Admin
Posts: 5561
Joined: 05 Apr 2012 16:26

v3.0.13.1 - stable

Post by radio42 » 13 Mar 2014 23:52

Version 3.0.13.1 is out!

What's New?
  • Name of Media- and Cartwall-Libs is now configurable
  • Find: allow to select multiple Media-Libs
  • Find: Save Result to Playlist option added
  • Scripts: Archive file is now independent from history
  • Scripts: new script history options and processing
  • Script: global script reload only affects non-running scripts
  • Script: new ANYOF: media library selection possible
  • Tagger and Advertising: 2 DSPs are now available in the output
  • Various smaller optimizations
  • Other smaller bug-fixes
  • stable

Name of Media- and Cartwall-Libs is now configurable
So far the name of media- and cartwall libraries have been automatically chosen by the system.
Now, you can specify your own name for each library (or just leave the default name as is).
In any case, make sure, that name is unique within all your media- resp. cartwall libraries!

This is also true for the Media Library Server. When you double-cklick on a media library entry you can edit its properties (incl. its name).


Find: allow to select multiple Media-Libs
The browsing dialog to select a media library has now been changed to allow to select multiple libs at once.
The media library selector dialog now contains checkbox allowing you to select the libs to include in your search query.
- If you checked at least one checkbox - all the checked media libs are included in your search.
- If no checkbox is ticked, but you selected a single media lib only that one is used (like before).
Use the 'x' icon button in the find bar to clear any selected media libs are to search again in ALL media libs.

In addition a new 'Find Limit' by time (in seconds) was added allowing you to specify a maximum search operation length.
Note, that there are cases, where an atomic long running operation might still take longer to actually quit.
Use this time limit option only if really needed (it is disabled; set to 0; by default).


Find: Save Result to Playlist option added
The Find window context menu has been enhanced by a new 'Save Result to Playlist...' item.
As the name suggests, you can now save your find result into a new playlist file.


Script: new ANYOF: media library selection possible
As in the Find window also the Script-Library-Editor has been enhanced to allow you to select multiple media- resp. cartwall libraries for the script-line actions 'Random' and 'Cartwall'!
- If you checked more than one checkbox: all the checked media libs are included in an 'ANYOF:' way (random within any of the selected libs).
(note: if a category is checked; all current libs underneath are automatically selected)
- If exactly one media lib checkbox is ticked (or non is ticked, but a media lib is selected): only that single media lib is chosen.
- If non is ticked but a category is selected: that 'CATEGORY:' is used (random within any of the libs contained in the category).
- If non is ticked but a lib is selected: only that single media lib is chosen.

I assume, that these options given an even greater freedom and flexibility to select random media libs and apply filters or rules to it.


Scripts: new script history options and processing
The script history was completely reworked and now contains the same options and shares the same behavior as the global history.
So far the script history (if enabled) was only checking track- resp. file names.
Now you can include the same extended checks as already available in the global history to each single script!
This includes all known strict or relaxed, Artist (X-Artist), Album or Title checks - plus the capability to keep each single script history automatically persistent (between restarts of ProppFrexx).

In addition the script history now should actually only contain effectively used entries. E.g. un-played playlist entries are now removed from the script and global history once a scheduled playlist is closed by the scheduler when a new program is started. Entries which are removed due to a script rule are now also removed from both histories accordingly.


Scripts: Archive file is now independent from history
As you are now able to keep each single script history automatically persistent; there was no need anymore to tie the archive to the song history (as before).
Now, the archive works completely independent from the script history (and is limited to a maximum of 500 entries, which should roughly cover almost one full day).
As such the little trick to use the same Archive- and Additional-SongHistory-Filename is not needed anymore!
The archive file will, if used contain the effectively scheduled.


Script: global script reload only affects non-running scripts
So far a global automatic reload of your script libs (as e.g. specified in 'General Settings - Folders/Libraries - Library Automation Options - 'also reload Script Libraries') would have affected running scripts. This was not good, as it might result to various side effects, e.g.:
a) the script history was lost
b) the script pointers was reset internally (the script would continue with the 1st script-line instead of the current)
c) the archive might have been lost
To avoid these unwanted side-effects, any running script is now excluded from these automatic script library reloads!
However, you can still manually reload any script. The side effects a) and c) have been eliminated in general, but b) would still happen.
So take care when you are manually reload a script, which is currently running ;-)


Tagger and Advertising: 2 DSPs are now available in the output
Both these two applications now allow you to define 2 optional DSPs (either a VST or Winamp DSP) for your main output in the general settings.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests