v4.0.0.13 - stable

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

v4.0.0.13 - stable

Post by radio42 » 25 Aug 2015 23:06

Version v4.0.0.13 is out!

What's New?
  • Chat-Client Setup enabled
  • RecordOutputFolder now supports macros
  • New SaveScheduledPlaylistFile program scheduler option added
  • New default VO_StartWithCueInOrEndWithRampOfNextTrack transitoin type added
  • New MusicMaster scheduler import format template added
  • Various smaller optimizations
  • Other smaller bug-fixes
  • stable
Note: A rebuild of the .11 was needed, due to some smaller issues encountered - that's why the previous .11 was renamed to .13!


Chat-Client Setup enabled
See general settings, section 'More Stuff'. The 'Chat-Client Setup...' button was accidentally hidden.
The Chat-Client Setup enables you to send messages between multiple ProppFrexx instances (even from within the internet).
Note, that you need one logical 'server', which has the 'GPIO Ext. Service' enabled and running.
You need the credentials of that logical server (which is the IP/DNS address and its port number, as well as its general TCP/IP password.
Specify these 'server' details within the Chat-Client Setup plus give yourself a client name.

On the client side you do not need to enable the 'GPIO Ext. Service'! However, any given local command-mapping of the 'GPIO Ext. Service' will still be used also on the client side!
Now all connected clients AND the logical server can exchange messages via the ControlRooms's Message Center.
Incoming messages will then be checked against the local command-mapping of the 'GPIO Ext. Service'; which enables you to setup certain automation commands to be triggered once a certain message of a certain user arrives.


RecordOutputFolder now supports macros
Support of the ${yyyy}, ${MM} and ${dd} macros for the 'Rec. Output Path' was added (see general settings, section 'Encoding/Recording' in the Recording Settings group).
Note, that if a dynamic subfolder using these macros is used, that the automatic clean up might not work anymore and you must maintain your files manually.


New SaveScheduledPlaylistFile program scheduler option added
A new option was added for program scheduler entries: 'SaveScheduledPlaylistFile'.
If checked, the scheduled and played entries are saved in a .pfp playlist file into the standard Recording Output Folder (see above).
The naming of these playlist files is always: "yyyyMMdd_HHmm.pfp" - according to the start date and time of the related program.
This should easily allow you to repeat a previously scheduled playlist from within another program scheduler entry.

In order to do so, you might create a script with a 'LoadPlaylist' script-line entry.
In the entry of such 'LoadPlaylist' script-line you might use the ${start_yyyy}, ${start_MM}, ... etc. macros. And/or use the *[DATE] macro function to perform so calculation on it.

Example 1:
If you want to repeat in the evening a program of the day (lets say, that this is exactly 7 hours later on the same date), you can specify the following LoadPlaylist script-line entry:
C:\My Music\*[DATE:{${start}}:{hours}:{-7}:{yyyyMMdd_HHmm}].pfp

Example 2:
If you want to repeat a program which played at 10:00h, but 3 days later, you can specify the following LoadPlaylist script-line entry:
C:\My Music\*[DATE:{${start_yyyy}-${start_MM}-${start_dd}}:{days}:{-3}:{yyyyMMdd}]_1000.pfp


New default VO_StartWithCueInOrEndWithRampOfNextTrack transitoin type added
A new track insert transition type was added called "VO_StartWithCueInOrEndWithRampOfNextTrack". This is now also the new default for the "Convert to Sweeper" function.
It tries to align the sweeper track to the end of the ramp of the next track. In case the ramp time is longer than the sweeper track itself, it will be aligned to the cuein position. If no ramp position is given, the sweeper track stays into the playlist by its own and will be started normally with the next cue point of the previous track, which is also case, if the sweeper track is longer than a given ramp time.


New MusicMaster scheduler import format template added
A new Program-Scheduler Import module was added to support the import of log files create by the 'MusicMaster' scheduling solution.

Note, that you need to define an according MusicMaster export design within MusicMaster (fixed length, UTF-8, .txt extension):
- Air Date (MM.dd.yyyy)
- Spacer
- Air Time (HH:mm:ss)
- Spacer
- Artist (Keywords, 255 chars)
- Spacer
- Title (Keywords, 255 chars)
- Spacer
- RunTime (Duration, MM:ss)
- Spacer
- Type (1-character; containing the type of entry, like M, I, A, N, etc.)
- Spacer
- Cue (1-character, containing the cue mode: @=Hard-Sync, +=Soft-Sync, |=Manual, *=Ends with Ramp of Next Track, :=Starts with
Outro of Previous Track, ~=Starts with CueIn Or Ends with Ramp of Next Track)
- Spacer
- Path (255-characters, containing the location of the audio track)

(The 'Cue' field is optional).

Notes:
In case you have no idea what the "Type" and "Cue" is good for - just leave them empty (filled with spaces) or use the following default values:
EntryType = M
CueType = +

Here comes the mapping of the MusicMaster 'Type' to the ProppFrexx 'Event-Type':
M = Music
N = News
R = Local
P = Advertising
C = Commercial
A = Report
I = StationID
J = Jingle
T = Traffic
W = Weather
S = Sports
O = Miscellaneous
V = Announcement

Some special 'Type' chars are also supported:
* = DirectCommand (filename contains the control-command or an FTE or TUS helper, see below)
- = VoiceTrackMarker (Placeholder)
@ = TimeUpdateSync (the StartTime would denote the nominal sync time)
/ = SpotBreakMarker-Start
\ = SpotBreakMarker-Stop (all items in between are Overlay spots)

FTE-Helper (filename must start with ‘FTE ’):
FTE Type=<type> [Start=<mm:ss>|<hh:mm:ss>] [Dur=<approxDuration>] [<text>]

TUS-Helper (filename must start with ‘TUS ’):
TUS Type=<type> [Start=<mm:ss>|<hh:mm:ss>] [<trackname>]

And here is the full MusicMaster log-file format specification:
type="FIXED", extension=".txt", encoding="UTF-8"
<fields>
<field name="StartTime" start="0" length="19" align="left" pad=" " format="DateTime:MM.dd.yyyy HH:mm:ss">${X}</field>
<field name="Artist" start="20" length="255" align="left" pad=" " format="String">${X}</field>
<field name="Title" start="276" length="255" align="left" pad=" " format="String">${X}</field>
<field name="Duration" start="532" length="5" align="left" pad=" " format="TimeSpan:mm:ss">${X}</field>
<field name="EventType" start="538" length="1" align="left" pad=" ">${X}</field>
<field name="Cue" start="540" length="1" align="left" pad=" ">${X}</field>
<field name="FileRef" start="542" length="255" align="left" pad=" " format="String">${X}</field>
</fields>

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest