Skip to main content

Version 2022.8

Release Date: 2022-12-20

🎄 🎅 🎁 May your holiday season be filled with good cheer, good food and the occasional ugly sweater party. 🎂 ❄️ ⛄️

Features​

Let's explore what's new:

  • SBS-897: Documentation
    Some areas of the documentation have been automated to ensure that up-to-date information is always displayed
  • SBS-1131: Restore Deleted Items
    Deleted items can now be restored on the detail page
  • SBS-1824: Item Status as Boolean Value in Ember+ Provider
    We have added the item status as boolean value to the Ember+ Provider. This allows connected Ember+ consumers to easily determine whether an item is active or inactive within the system.
  • SBS-1863: Item Parameter Description
    For the individual parameters of the items, the GUI now displays additional help texts
  • SBS-1864: Item Parameter Placeholders
    For the individual parameters of the items, the GUI now displays whether these support placeholders
  • SBS-1886: Export to JSON
    We have added the possibility to export one or more elements to a JSON file. This can be useful if you want to save a copy of your data for backup purposes, or if you want to copy specific elements to another Broadcast Suite installation.

Improvements​

These things are much better now:

  • SBS-1892: Request Timeout for Sound4 Devices
    The Sound4 device has now a new parameter called Request Timeout. This allows to change the previously hardcoded timeout of 1 second.

Installer​

  • SBS-1890: Service Recovery Options
    The Windows installer does now set the automatic service recovery options. This will ensure that any services that may experience failures will be automatically restarted, improving the overall reliability and stability of the system.

Bugs​

This should never happen again:

  • SBS-1891: Fixed an issue where the dim state of VisTool MF-Keys was occasionally not visible on web panels
  • SBS-1816: Update Order
    Fixed an issue that during a new installation or update, a project (Core, API or GUI) could not start because one or more other projects were trying to update the database at the same time. Now, projects are updated sequentially - one by one. The order is Core => API => GUI.
    This means that the GUI waits with the update until the API has finished the update and the API in turn waits until the core has finished the update. This all happens fully automatically.
    If it should be however necessary that e.g. the GUI must make the update first, the argument -m or --mainProject can be given as start argument start, with which this project is updated first.
  • SBS-1885: Fixed an issue where tabs displayed scroll buttons unnecessarily even when the viewport width was sufficient

Panels​

  • SBS-1895: Fixed an issue with Skaarhoj panels where the button would always revert to its default value as soon as one of the triggers changed to off, if several triggers had been assigned to a button on a Skaarhoj Panel device.