Release Notes June 16, 2014 FIRMWARE RELEASE NOTES (BrightSign XD230, XD1030, XD1230) BrightSign, LLC. 16795 Lark Ave., Suite 200 Los Gatos, CA 95032 408-852-9263 www.brightsign.biz
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 4.7.151 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 the following multi-touch screens: ELO 3243L, Iiyama T1731SAW, and Nitere AR150-2 True video rotation at resolutions up to 1080p60 1
New streaming server capabilities: XD players can process requests from other devices on the network and deliver media via RTP, RTSP, and HTTP. Support for chroma key and luma key video blending Support for seeking to a certain video or audio time code Support for video fading Support for the 1680x1050x60p video mode Progress bar widget Support for HTTPS streaming 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 HTML pages now display multiple JavaScript animations more consistently. Newer models of USB external hard drive (including Seagate models) are now correctly recognized by XD players. 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. 2
The colors of custom mouse-cursor icons now display correctly. Mouse-cursor icons are no longer obscured by various image and text widgets. Players now correctly display certain fonts that would previously encounter clipping issues at the beginning of the text. Some minor choppiness associated with text characters has been removed. The screen no longer flashes if a video zone transitions into or out of HDMI input. This bug only occurred if there were additional zones other than the video zone. Attempting to rapidly change channels on a DTCP-enabled RF input no longer causes the player to crash. Attempting to play an AVCHD Lite video file no longer causes the player to crash. Resizing an HTML <video> element while the page is being displayed no longer results in a single frame of video corruption. The color values of standard video elements (i.e. those added to a looping or interactive playlist) and HTML <video> elements are now exactly identical. Using an HTML widget to rotate a portrait mode (1080x1920) video no longer causes clipping problems. HTML pages no longer randomly encounter frame-rate issues if the RequestAnimationFrame() JavaScript call is being used. 3
Drawing text over an image using the JavaScript filltext()function no longer results in a blue background. This bug only occurs if the combined width and height of the HTML canvas is larger than 65536 pixels. Displaying an HTML page with the JavaScript console enabled no longer has a possibility of crashing the player. HTML pages that are published directly to the player (without an autorun script) now correctly support z- ordering of video and graphics. If the player is located behind a proxy, attempting to display a remote web page will no longer cause 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. EndOfStream callbacks no longer have a chance of creating a deadlock with rovideoplayer calls. Improvements Mouse and touch events are now much more responsive and effective on resource-intensive HTML pages. 4
Players are now better able to handle large amounts of multi-touch events in a short period of time. Mouse-cursor icon transparency is now fully supported for BMP and GIF image files. The new rovideomode.setgraphicszorder() allows scripts to determine whether all graphics should be placed in front of, behind, or between two videos on the z-axis. The SetRectangle() method has been added to rocanvaswidget, allowing scripts to resize the widget without destroying it. 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://www.example.com/stream1?vcdbsize=5000000&acdbsize=1000000"). 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 1920x1200x60p resolution is now displayed using reduced blanking mode. 5
The scroll bars on HTML pages are now disabled by default. The new rohtmlwidget.sethwzdefault() method allows scripts to set the default HWZ mode for HTML <video> elements. The new rohtmlwidget.setlocalstoragedir() and rohtmlwidget.setdatabasedir() methods allow persistent storage of webpage data (with IndexedDB or the JavaScript storage class) after power loss or network outage. The GetUserData() method can now be called on messages sent from rohtmlwidget, allowing scripts to distinguish between events from different rohtmlwidget instances. 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. The new RestartScript() global function causes a player to search for a new autorun file without needing to reboot. If a new autorun script is uploaded to the player from the Diagnostic Web Server, the player now loads the script without needing to reboot. Initiating diagnostic operations using the Diagnostic Web Server no longer overwrites the autorun.brs file contained on the local storage of the player. 6
The IP address displayed on the BrightSign splash screen now updates if the player obtains a new DHCP lease. BrightScript now supports 128-bit AES encryption through the new roblockcipher object. BrightScript now supports the PBKDF2 function through the new ropasskey object. The player no longer crashes if a character pixel size larger than 1920x1080 is passed to rotextfield during object creation. If no character pixel size is specified during object creation, the player attempts to use the largest pixel size that will fit within the text field. BrightScript no longer allows two roirremote objects to exist at once. 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. 7