Skip to main content
Skip table of contents

RetailPlayer Firmware V6.3.0

Release Notes

This document describes the Change Log of the V6.3.0 of the RetailPlayer Firmware 

Release Date

 

Change Log

New Features

  • Support for RetailPlayer Firmware on M400. New PN available for order at Barix: 

    • 2020_9318_RetailPlayer M400 EU Package

    • 2020_9319_RetailPlayer M400 US Package

    • 2020_9320_RetailPlayer M400 UK Package

    • 2020_9321_RetailPlayer M400 NoPSU Package

  • Ability to play RTP streams with dynamic payload by manually specifying format, channels and rate in the Priority URL scheme:

    • formats: mulaw, alaw

    • channels: 1 or 2

    • sample rate: 8000, 11025, 16000, 22050, 24000, 32000, 44100 and 48000

    • Allows integration with multiple paging sources as priority URL 

    • Example of Priority URL to play a stream from an RTP multicast group with the following known format: mulaw, 1 channel (mono), 24kHz

      • rtp://224.0.0.56:12345?format=mulaw&channels=1&rate=24000


  • Support for installation of custom CA certificates (ability to integrate in environments with non-public PKI) 

Changes/Improvements

  • Improved remote diagnostics capabilities

Fixes

  • Rare lockup of the player could occur when switching streams

  • Incorrect handling of fallback tracks after they player at least one time and were removed afterwards

  • When playing an RTP stream with unsupported audio format the player doesn't behave as expected, it doesn't change to another working channel anymore with the risk of being silent if failover tracks are not uploaded

Known Limitations / Issues

  • Ethernet interface must be kept in DHCP mode to allow Wireless LAN operation

  • WLAN interface is not identified by Discovery Tool

Deployment

Date

Recipient / Environment

Software Package / Version - Download link

 

Made available in production portal.

update-core-image-barix-audioplex-6.3.0.tar

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.