FIRMWARE RELEASE NOTES

Transcription

1 Release Notes June 16, 2014 FIRMWARE RELEASE NOTES (BrightSign HD120, HD220, HD1020) BrightSign, LLC Lark Ave., Suite 200 Los Gatos, CA

2 Updating your BrightSign Software 1. Click the Download Now button below the model number that corresponds to your BrightSign player. Note: HD and XD firmware versions are sometimes designated with the same number, but they are still different files. Make sure to download the update file that corresponds to the model number of your BrightSign player. 2. Unzip the downloaded file and copy the.bsfw file to the root directory of your SD card. 3. Insert the SD card into your BrightSign player. 4. Power on the BrightSign player. 5. Ensure that the yellow update LED is blinking during the update process. Once the player has finished updating, it will automatically delete the.bsfw file from the SD card and reboot. Changes Since Note Unless marked by a symbol, new features listed in these release notes are not available in the current beta or release version of BrightAuthor and can only be utilized with custom scripts. A feature may become available through BrightAuthor at a later date. Please use the latest version of BrightAuthor and read the release notes for all new features and functionality. New Features Support for chroma key and luma key video blending Support for seeking to a certain video or audio time code 1

3 Support for video fading Enhanced ticker with scrolling capability Universal Plug and Play (UPnP) support via BrightScript Support for setting the recovery URL via DHCP Option 43 Telnet support for BrightSign and BrightScript shell prompts Bug Fixes Newer models of USB external hard drive (including Seagate models) are now correctly recognized by the HD120, HD220, and HD1020. All remnants of a mouse-cursor icon can now be removed from a canvas. AC3 audio now plays correctly within the MP4 and MOV video containers. HLS streams containing raw MP3 audio play correctly again. Streamed.ts video files that do not contain audio data now play correctly. The colors of custom mouse-cursor icons now display correctly. Attempting to play an AVCHD Lite video file no longer causes the player to crash. If an rohttpevent instance is created by the script rather than by the rohttpserver instance, there is no longer a possibility that the player will crash. Unplugging a BP200/BP900 during a button-panel presentation no longer causes system instability. Using rodatetime to set the clock backwards (to a negative time) no longer causes problems with event messages. 2

4 EndOfStream callbacks no longer have a chance of creating a deadlock with rovideoplayer calls. Improvements While playing an HTTP stream, the roaudioplayer object now posts an "end-of-stream" event if the player does not receive any data from the streaming server for several seconds. The script can then take appropriate action, such as generating a new connection request or switching to a different URL. Streaming audio no longer fades in if playback is being looped. The video and audio buffer settings for IP streaming can now be set within the URL (for example, "rtsp:// Players can now play video streams from a Matrox Maevex 5100 encoder. Note that audio support for this series of encoders is still a work in progress. The default low-latency mode for video-only RTP streams can now be overridden by adding "buffering=true" to the stream URL (for example, "rtp://example:port/?buffering=true") DNS lookups can now be used to specify a remote host involved with an rotcpstream instance. New Video Time Code events can now be generated for a video during video playback. The file system of the player now fixes filenames that contain colons, which are not allowed in FAT systems. Since storage devices attached to a player usually need to be formatted using FAT32, this can help prevent problems caused by faulty file names. SD card failure will no longer prevent the player from rebooting. BrightScript no longer allows two roirremote objects to exist at once. 3

5 Specifying an empty byte array for the rocecinterface.sendrawmessage() method no longer causes instability with the rocecinterface object itself. The player is now better able to successfully rename invalid or corrupt.bsfw update files. The player also continues looking for a valid.bsfw update file if it detects and renames the initial update file. Placing two different arbitrarily named.bsfw update files on a single SD card no longer causes an indefinite upgrade loop. The BrightSign splash screen now disappears more crisply. 4