v4.3.3.4 - stable

This forum will contain general news and announcements made by radio42.
Post Reply
User avatar
Site Admin
Posts: 7533
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
v4.3.3.4 - stable

Post by radio42 »

Version is out!

What's New?
  • Upgrade to latest BASS audio engine versions
  • Downmix truncation at Fixed TUS optimized
  • TLS/SSL support for streaming
  • Updated OGG, OPUS and FLAC encoders to support ICEcast2 mid-stream meta updates
  • Optional Bitstream metadata updates for FLAC, OGG and OPUS
  • Updated of all other encoders to its latest version
  • New macro-function ${RCM:clientname|macro} to resolve remote macros
  • New macro function *[FILENAME: added
  • LoadPlaylist now always evaluates file changes, also for Overlays
  • RVT now also resolves Overlays for already created/imported playlists
  • Advertising: Billing now allows multi-period selection, plus Campaign Filters
  • Advertising: New Fix-Price per month calculation option
  • Advertising: Dynamic Slot Assignment Filters allow multiple entries
  • Bug-fix for script-line mode 'Execute' and the ResetScriptPointer option
  • Bug-Fix FLAC Encoder config
  • Bug-Fix when supressing an Overlay and resuming a Playlist
  • New UseBASS option for EncoderProfiles (might disable internal encoders)
  • New Threads setting for Mixer-Output-Channels
  • Various optimizations and smaller bug-fixes
  • stable

Streaming enhanced (e.g. ICEcast):
Beside TLS/SSL support, all encoders have been updated to the latest version. But most important is the support for mid-stream meta data updates, which require new bitstreams when using OGG, OPUS or FLAC OGG streams. This is now automatically supported.
In addition an option was added to suppress the metadata update via a new bitstream option, which is e.g. needed for the RSAS server.

Macro-function ${RCM:clientname|macro}:
Normal macro's are evaluated locally. With this new macro you can evaluate macros on a remote ProppFrexx instance.
The connection to that remote instance is configured in the Remote Control Monitor as a Remote Client. As such, the first parameter denotes the related client name. The second parameter is the name of the macro. Example...
Locally: ${cpltracknamecurrent}
Remote on MainPC: ${RCM:MainPC|cpltracknamecurrent}

New macro function *[FILENAME:
See the User Manual Appendix for examples...

Post Reply