BrightSign HD222 Player Firmware 6.1.76 Download

Posted at December 22, 2024 by PCI-DB Team

BrightSign HD222 Player Firmware 6.1.76 Description

Changes Since 6.1.37

Limitations
• (4Kx42) USB3 Super Speed (XHCI) support has been disabled.
• (4Kx42, XDx32) DTCP encryption/decryption support has been disabled.

End-User Notes

New Features
• Support for storage devices with sizes up to 1TB
• Multi-touch support for the NEC OVL-V463 touch screen Improvements
• (4Kx42) The Diagnostic Web Server (DWS) now reports when a connected 4K display supports the following HDR protocols: BT2020 RGB, BT2020 YCbCr, SDR EOTF, ST2084 EOTF.
• The Log page on the Diagnostic Web Server (DWS) now contains a link below the log output for saving crash dumps.
• The Diagnostic Web Server now displays the WiFi signal if the player is connected to a wireless network.

Bug Fixes

• HDMI-input playback via HTML has been fixed.
• Playback of portrait-mode HD video (1080x1920) has been fixed.
• (4Kx42) MJPEG video windows now display correctly with 4K video modes. • (4Kx42) Players now correctly output the max luminosity of HDR 4K videos. • (4Kx42) HTML pages that download numerous high-resolution images no longer cause the player to crash.
• HTML pages are now responsive to mouse inputs at the edges of the page.
• Playing an HTML video that has 44.1kHz audio no longer causes the screen to go blank momentarily. This issue would occur the first time after presentation start or after playing a video with 48kHz audio.
• RTSP streaming video now plays correctly when preceded by an HTTP streaming video.
• Time-server configuration no longer fails if the specified URL for the NTP server contains a trailing slash (e.g. "ntp://time.brightsignnetwork.com/").
• When downgrading firmware versions on a player, the progress bar is once again displayed on screen.
• The Logitech Wireless Presenter R400 works with BrightSign players again.
• DVB subtitles now display correctly.
• Multichannel AAC is supported again.
• HDMI-input audio passthrough no longer fails on some Blu-Ray players when switching from a disc with ATMOS audio to a disc with DTS audio.
• HDMI-input passthrough of Dolby Digital Plus audio no longer exhibits breakups with some Sony and Marantz Blu-ray players.

Developer Notes

New Features
• New roBtManager and BSBtManager objects, which allow players to transmit using USB BLE beacons
• WebRTC support for HTML widgets

Improvements

• The roRtspStream object is no longer required to play a video stream; streaming URLs can now be played directly using the roVideoPlayer.PlayFile() method, as shown in the following example: v.PlayFile({url:"http://172.30.1.37/file.ts"})
• The roVideoPlayer object now generates event 30 (MediaError_NotStarted) when a video fails to start. For backwards compatibility, event 16 (MediaError) is generated as well.
• New allow_seamless parameter for roVideoPlayer.SetLoopMode() makes it possible to configure video playback to loop non-seamlessly in all cases, as shown in the following example: v.SetLoopMode({enable:true,allow_seamless:false})
• (4Kx42) The roVideoMode.GetEdidIdentity() method now returns the following values related to 4K HDR support: bt2020_rgb_support, bt2020_ycc_support, hdr_st2084_support, sdr_eotf_support, hdr_eotf_support.
• (4Kx42) New roVideoMode.OverrideHDMIDynamicMastering() method allows you to override the HDR mode set by the video content.
• The roUrlTransfer.AsyncMethod() method now accepts the output_object parameter, which enables processing of a downloaded HTTP body before passing it to an object.
• New roKeyStore object allows you to add client certificates to HTML widgets.
• (4Kx42) The roHtmlWidget.EnableSecurity() method now accepts an associative array with websecurity and camera_enabled keys. This allows a webpage access to a USB camera connected to the player.
• Players now ignore the "viewport" parameter in the <meta> tag of an HTML page. This behavior is equivalent to desktop browsers.
• The roHtmlWidget.SetHWZDefault() method now accepts "on" and "off" values when there are other parameters in the string. In this case, "on" is equivalent to "z-index:1" and "off" is equivalent to "z-index:0".
• The roVideoPlayer.GetStreamInfo() method now returns the framerate of the current video.
• (XDx30) The maximum instantaneous bitrate for Media Server RTSP streams has been increased.
• PTP packets are now marked as DSCP EF (46).

Bug Fixes

• HWZ-enabled <video> elements now support scale() and translate() CSS animations.
• Clearing the src of an HTML <video> element now stops playback of HDMI input.
• A long HTML video in a playlist will no longer play twice periodically.
• JavaScript now correctly generates an ended() event when a network dropout causes an HWZ HTML <video> element to stop streaming.
• Widgets generated using AngularJS now respect the SetTransform() orientation of the parent HTML widget.
• If a video zone displaying HDMI input causes Mosaic Mode resources to be over-allocated, the player will return the appropriate response in JavaScript/BrightScript (rather than crashing).
• A Mosaic Mode video window will now display correctly when it has an odd width and/or height and is located at the edge of the screen.
• Players no longer crash when taking a screenshot of a video that is scaled down by a factor greater than 16.
• The roVideoPlayer.GetStreamInfo() method now correctly reports the VideoColorDepth of video files that have a 10-bit color depth.
• The Diagnostic Web Server now appropriately sets the TTL when querying remote PTP servers.

Updating BrightSign Player Firmware

Follow these steps to update the firmware of a player with an SD card:
1. Click the Download button on the download page that corresponds with the model number of your BrightSign player.
Note: Firmware versions for different model families are often designated with the same number, but they are different files. Make sure to use only 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 orange “update” LED is blinking during the update process (except on LSx22 models). Once the player has finished updating, it will automatically delete the .bsfw file from the SD card and reboot. 

Troubleshooting Updates

If the firmware update process does not work, ensure the following:
• The update file is in the root directory of the SD card. For example, if Windows designates your SD drive as G:, then the directory for the update file will be G:/<*-update>.bsfw.
• The SD card contains only one file with a .bsfw extension.
• The SD card is formatted using FAT32. You can check the formatting of your SD card by right-clicking the card in Windows Explorer and selecting Properties.

Updating with Rescue Mode

If the firmware update process has been interrupted, or if the firmware file has been corrupted, you may not be able to update the player using the above methods. In these cases, you can perform an update using Rescue Mode:
1. Copy the .bsfw update file onto the root directory of the SD card.
2. Power down the BrightSign player.
3. Insert the SD card into the BrightSign player.
4. Using a paper clip or pen, press and hold the SVC button located on the side of the player.
5. Power on the player while holding the SVC button. The orange “update” LED (available on all models except on the LSx22) may turn for a moment at boot: Hold the SVC button until the orange “update” LED stays on.
6. Allow several minutes for the firmware update to complete. Once finished, the player should reboot and display the BrightSign logo along with the new firmware version of the player.

About Media Player Firmware:

Installing a firmware update for your Media Player improves the general user experience by adding new features, fixing bugs, and enhancing the compatibility of your device, in order to play various formats of audio and video content.

By updating your Media Player, you can actually prolong the device’s life because, this way, it will be in sync with the new industry standards for content creation.

However, the process of updating your device is a risky one if not done according to strict instructions, such as: make sure that the firmware you have downloaded is compatible with your device, and don’t interfere with the player during the update process.

The most common method of upgrading your Media Player is by using a USB stick or update DVD. Although this process is very straightforward, each device has certain particularities that you must take into account.

If you consider using this update for your Media Player, feel free to click the download button, install the firmware and enjoy. Check out our website as often as possible to keep your Media Player up to date with the latest software and firmware.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related BrightSign Drivers