Skip to content

Changelogs

Updates to labels and secondary colours

1.16.0

Updates to primary, secondary, and label colours

One of the most requested improvements was better readability of the default colours used for labels, along with improvements to how and where the secondary colour was used in projects. We are pleased to announce improvements to both of these features!

First, labels on gear and connections will now either be black or white, depending on the background colour they are on. This means you no longer need to manually manage label readability through the secondary colour option.

As such, the secondary colour is now used to control the border colour of your gear and your connection labels. By default, it will be a slightly brighter version of your primary colour but you may change it to anything you like. If you want to revert it back to the default, a new button next to the secondary colour allows you to 'Base on Primary Colour'. This is accessible from either the Layer Manager or the edit colour dialog when right clicking on a gear or connection.

Please note that these changes will go into effect on new items in your drawings. Existing items will update to this new colour system as you interact with the project or the next time you update your colours. The first save of an existing project after this update may take a little longer than usual as the colours are updated.

Dataton, ioversal, VYV, Modulo Pi, Pixelhue, Shure, Yamaha, and more items added to the default library!

We have added over 100 new library items, most of which have been direct requests. Check out the updated library in the app, with the highlights being:
  • Dataton WATCHPAX
  • ioversal Vertex
  • VYV Photon and Tachyon
  • Modulo Pi Kinect, Player, and more
  • Pixelhue F, P, and Q series
  • Yamaha DM series
  • Shure Axient Digital, ULXD and related accessories

Improvements

  • When the background sync runs, it now handles non-destructive changes automatically, only prompting you if it cannot safely resolve a sync conflict
  • You can now choose to ignore errors when manually importing a project; this can be useful to allow the project to load, and then run a server sync once opened to clean up any project issues

Bug Fixes

  • Fixed older projects not importing when they used categories or signal types that have been depreciated; they are now upgraded to their new versions during the import
  • Fixed the following ports from missing unique colours in the drawing:
    • RS422
    • Hirose 10 Pin
    • Phoenix 10 Pin
    • All PowerCONs
    • All NEMA ports
    • Stage Pins
    • Socapex

1.15.2

Improvements

  • A new project hard load option has been added; this will bypass loading the project from your most recent version history and instead load the latest version of the project directly from the server
    • Activate it via the new 'Hard Load Project' button on the Projects Page or by holding CTRL when clicking on a project
    • Note that this will be slower compared to the default load option but this can be helpful in the event of any compatibility issues with the most recent version history

Bug Fixes

  • Fixed a rare edge case that could prevent a project from upgrading to the latest app version when brand new gear was used in the project, but a version history was not saved, and then the project was re-opened

1.15.1

Improvements

  • Added TTL Sync as a signal type
    • It is compatible (with a signal warning) with Framelock signals
  • Added Antenna Cascade as a port category

Audio mics and equipment categories added

1.15.0

Audio mics and audio equipment added as new categories

Two new categories have been added to support some upcoming library additions. Audio equipment also supports gear level IP addresses, and both support last week's release of port level IP addresses.

Increased server capacity

We have increased our server capacity to handle more concurrent users at once for a faster app experience. We will continue to monitor performance and plan to increase capacity even further over the coming weeks.

Improvements

  • Added View Ports to the right click menu when selecting gear, to open the gear's ports for faster access
  • Moved Remove to the bottom of the right click menu, to help prevent unintended clicking

Bug Fixes

  • Fixed connections being removed incorrectly when they were moved between gear of different categories
  • Fixed retrying after a server connection loss from getting stuck in a loop in some situations

IP addresses added to ports!

1.14.0

IP addresses added to ports, along with duplicate IP validation!

You can now add IP addresses and subnets to network based ports (RJ45, etherCON, etc). This is in addition to IP addresses at the gear level you previously were able to do on switches and PTZ cameras.

All gear categories other than switches support this feature, and will be selectable for any network based port in both the View All Details dialog table, and port reports.

In addition to being able to set IP addresses, the system will also validate in real time if you have entered a duplicate IP and warn you if so. This not only checks across all your gear and ports, but is VLAN aware as well! Meaning you can set the same IP address on two different ports, so long as both ports are ether on, or connected to, different VLANs.

Note that gear level IP addresses (as set in General Settings) do not have VLANs so these will be checked against all gear and ports.

The warning you receive will display the duplicate gear's label, as well as the port's label and VLAN's name if applicable. You may ignore this warning as it will not prevent you from setting a duplicate IP, as there may be cases where this is desirable so it will simply warn you instead.

Lighting distributions now support IP addresses at the gear level

In addition to port IP addresses, the lighting distribution category can now set IPs and subnets at the gear level, in the General Settings pane. These will benefit from the IP validation logic described above.

Bug Fixes

  • Fixed IP addresses and subnets' server validation not checking for IP address values specifically
  • Fixed being able to edit connection colours in Reports, even when the report was locked