Broadsign Control Player 14.5.x
- [CORE-22463] Fixed an issue causing Broadsign Control Player to not download and play Broadsign Creator or Broadsign Publish content.
- [CORE-21710] When playing back HTML content in Windows with Chromium log-file enabled, a window named QtWebEngineProcess.exe will open, sometimes obscuring the playing content.
- [CORE-21716] When using scheduled reboots, Broadsign Control Player would register the resulting reboot as a false Unexpected Shutdown incident.
- [CORE-21718] While using the Realtime Audience API, if the configured URL for the Realtime Audience data is unavailable, Proof Of Plays would not be stored.
- [CORE-21488] Fixed an issue when using frame synchronization, the follower may have delays downloading ad copies.
- [CORE-21009] Fixed an issue with the “enforce orientation” feature on Windows 7.
- [CORE-21503] Fixed an issue where the external saturation file was ignored when configured with a relative path to the file.
- [CORE-21712] Fixed an issue where an under-saturated primary campaign would cause the campaign in the secondary share to play too many times.
- [CORE-21739] Fixed an issue where performing
sudo aptupdates or upgrades on Ubuntu 20.04 caused Broadsign Control Player to crash.
- [CORE-21676] Fixed an issue where a fractional saturated campaign in the primary share would be taken over by a Broadsign Creator campaign in the secondary share, after a few loops.
- [CORE-21257] Fixed an issue where trying to print multiple logs simultaneously resulted in some logs not printing.
- [CORE-21546] Fixed an issue where rotation between schedules did not take place as expected.
- [CORE-21553] Fixed an issue that caused folder synchronization files to be re-downloaded on every refresh period, in negative UTC timezones (form example, UTC-5).
- [CORE-21417] Fixed an issue that caused unsold Broadsign Reach slots in the secondary share to be replaced with pre-emptible campaigns from the primary share.
- [CORE-21418] Fixed an issue where a negative clock skew resulted in Broadsign Control Player failing to poll, and sometimes crashing.
- [CORE-21676] Fixed an issue causing Broadsign Creator content in the secondary share to get overplayed.
- [CORE-21702] Fixed a conflict between triggered content and
--play_nextflag is used twice in a row.
- [CORE-21090] Automatic resolution matching has been improved to take screen orientation into account. See Ad Copy Criteria and Resolution Matching.
- [CORE-21587] A 64-bit Windows Player is now available.
- [CORE-21111] Broadsign Control Administrator and Broadsign Control Player are compatible with Windows 11.
- [CORE-21353] Fixed an issue where Broadsign Control Player did not auto-rescale the display upon unplugging and replugging its HDMI cable.
[CORE-21625] In a 64-bit Broadsign Control Player Windows installation, the sample triggers.xml file used as a model for sending triggers via the serial port is missing from its usual directory on the player device.
- [CORE-21632] When manually upgrading from a 32-bit Broadsign Control Player to the 64-bit version, you must also rededicate the player on Windows, using Admin privileges. To upgrade multiple systems, consider scheduling remote upgrades by opening a case with Broadsign Services. See Step 5: Dedicate Broadsign Control Player on Windows.
Workaround: Create a triggers file using the sample file presented in Triggers Action.