Warning: The 1.9.xx.xx versions are now feature frozen in preparation for a new release. During the final beta period, only bug fixes will occur in the 1.9.x branch prior to a 1.10 release. Any new feature work will now move to a new 1.11.x beta version.
Version 1.9.12.100 12/20/2024
Version 1.9.12.100 (fanless engine)
Version 1.9.12.100 (R2 Platform - 1RU)
Version 1.9.12.100 (Virtual Machine)
23709: Fix issues with friendly names displaying in logic flow trees when editing an existing link.
23953: Fixed issues with special characters in user panel and audio alarm names forcing them to underscores.
23977: Fixed issues with double quotes in certain translations in logic flows.
Version 1.9.12.99 11/18/2024
Version 1.9.12.99 (fanless engine)
Version 1.9.12.99 (R2 Platform - 1RU)
Version 1.9.12.99 (Virtual Machine)
Warning: This fix was a pretty low level change in the routing infrastructure code. If you run into any issues after moving to this version, please revert and report them.
Fixed an issue which would prevent objects from raising event changes if they were added after the system was running and were sub objects of a path that was used in a SapProperty Router. An example of the problem this version fixes would be using MemorySlots Ping property in a Sap Property Router (no we do not recommend this). After the system is running, if you add a new memory slot it was getting its primary object path switched from what it should be to a path under the SapProperty source. Only a restart would get the memory slot reporting events to the logic system and API. This version should fix the problem, but please see the warning above.
Version 1.9.12.98 11/14/2024
Version 1.9.12.98 (Fanless Engine)
Version 1.9.12.98 (R2 Platform - 1RU)
Version 1.9.12.98 (Virtual Machine)
Fixed an issue introduced in 1.9.12.97 with border colors in user panels not changing properly.
Version 1.9.12.97 11/05/2024
Version 1.9.12.97 (Fanless Engine)
Version 1.9.12.97 (R2 Platform - 1RU)
Version 1.9.12.97 (Virtual Machine)
23872: Fixed an issue where equality combiners with the RaiseOutput on Change selection would not write to the storage correctly so that on restart the combiner would be missing its inputs.
23682: Fixed an issue with the end action not executing randomly on date/time (non-recurring) timer events when in a cluster.
A single run date/time timer disables itself after start and end completes. The disable property was occurring on both nodes of the cluster and sending synchronization messages. If the secondary completes first this can cause the primary (which actually executes the actions) to get disabled before the actions execute. In this version only the primary (active) server will trip the disable state at the end of the execution.
Version 1.9.12.96 10/29/2024
Version 1.9.12.96 (Fanless Engine)
Version 1.9.12.96 (R2 Platform - 1RU)
Version 1.9.12.96 (Virtual Machine)
Warning: Version 1.9.12.95 was only available on the site for a short period of time. There was an issue where extra parameters were being written into panel css files when opened for viewing or editing. This actually broke css on pages beyond the default page. If you loaded 1.9.12.95, and have not made a lot of changes to your system it may be advisable to return to the previous bank with its unchanged panels and then update to 1.9.12.96.
Fixed an issue introduced in 1.9.12.95 that broke css for pages beyond the default page in a panel. See Warning above.
The new code does not modify the css files. Instead it interprets css in the following way in order to support backwards compatibility. If textcoloron/off is present in the panel page's css or in the inline css for the button it wil be used. If not if the color property is present in the panel page's css on in the inline css for the button it will be used. Otherwise the theme css will be used where the same color is used for both. This better supports backwards compatibility with panels that do not have the textcoloron/off but have been modified with custom color properties.
The same logic is also used for bordercoloron/off and bordercolor.
23645: Single run date/time timers were not being cleaned up (removed) according to the cleanup days value. This should be fixed in the version. It is recommended to use a value more than zero for this parameter.
23703: Device emulators would sometimes not close the client port when changing the emulator port without removing and recreating the emulator or restarting Pathfinder Core PRO.
23683.2 - Made some changes to Calendar event editing to disallow certain characters at the start of the timer name (such as _ and .) as the calendar would not present the event name properly when events were named this way.
Changed the name of the Remove Flow Control button introduced in the panel designer in 1.9.12.95 to instead be Remove Binding which better expresses what the button does.
Fixed an issue that was preventing some standard iPort style parameters from being available in ZephyrConnect. The ZephyrConnect was not using an iPort interpreter class with the additional capabailities enabled. This should be fixed in this version.
Version 1.9.12.95 10/08/2024
Removed from the site due to a problem with the panel button changes surrounding textcoloron/off and bordercoloron/off.
23458: Added a state column to the device emulators list in the UI which displays connection information.
Changed button binding in logic flows so that the binding button will turn the binding on, but turning off the binding requires selecting the field and then disabling the binding using a new button near the logic flow for the binding. This presents users from accidentally clearing an active binding.
Version 1.9.12.94 09/30/2024
This version was not released publicly and only released for internal testing. All changes in this version are also in 1.9.12.95
19651: Fixed an issue with backups where they could be taken via a hidden ajax page by non-admin users.
23279: Fixed an issue where a scene named with a forward slash in the name would be lost on a reboot. This version will change the character to an underscore if a scene name is created with a forward slash.
23355: Fixed an issue where if a memory slot is at the beginning of a scene, the following items might not display correctly when viewing the scene items in the editor. This was a display issue only.
23402: Added the startup value to the columns in the memory slots page for better visibility.
23461: Fixed an issue where Passthru combiners would not retain the RaiseOutputOnChange setting when applied via the logic flows UI.
23468: Fixed an issue where users with permission to see a panel with a clock might not see the time moving. This was do to a security restriction regarding obtaining time from the Pathfinder Server.
23503: Fixed an issue with image tools in the user panel designer where the logic flow editor might not be available after initially setting it on the image source property.
23520: Fixed an issue where renaming logic flows was increasing the consumed license count incorrectly.
23574: Fixed an issue with certain button colors and backwards compatibility due to newer properties added to the system in the last few versions.
Version 1.9.12.93 07/31/2024
Version 1.9.12.93 (Fanless Engine)
Version 1.9.12.93 (R2 Platform - 1RU)
Version 1.9.12.93 (Virtual Machine)
Fixed an issue with the fmt structure being removed with Quasar Engines when Aes67 sources are used.
Removed Engine from the check to remove the fmt structure since engine code 3.2.2 now requires the fmt structure for Aes67 addresses outside of the livewire range.
Multiple changes with Quasar Smart Key and other LCD buttons:
Fixed an issue with Quasar smart key buttons where on reconnect to the console the ForecolorOn/Off (TextColorOn/Off) state was not being pushed.
Reworked pushing state on reconnect so that it only happens from the active server in a cluster.
Fixed a situation where it could theoretically be possible for buttons states to be pushed before a successful login was completed.
Added storing the existence of SK buttons to the devices database so that the buttons can be initialized before a connection to the device is made. This allows state to be set before a connection is made if the connection is delayed.
Warning: The changes related to Quasar involved considerable reworking of the LCD and SK (SmartKeys) button state management. Please report any issues you may encounter.
Fixed a query message for Quasar Aux buss states that was so
Version 1.9.12.92 05/12/2024
Version 1.9.12.92 (Fanless Engine)
Version 1.9.12.92 (R2 Platform - 1RU)
Version 1.9.12.92 (Virtual Machine)
Fixed an issue in the new Calendar Resource Display control that was not showing the last item in the list if the list was not full.
Fixed an issue in the new Calendar Resource Display control that was not displaying the title font size option correctly.
Changed the displayed information in the Calendar Resource Display to use the following logic:
If there is a description that is not empty, use that for the event data display.
If there is a name that does not follow the default naming scheme and no description, use that.
If there is no description and the name follows the <TemplateName>_<ResourceName>_<Guid> format, display the template name only as the resource name is redundant in a control tied to a single resource and the GUID is not useful except in comparison to the API instance of the event.
Add a hover title in the Calendar Resource Display control with the full name in case it is needed.
Added new device types.
Fixed an issue when two instances of a calendar are open and more than one non recurring item was added in a single apply that would cause the second instance to show duplicate items until the browser page was refreshed.
Version 1.9.12.91 05/08/2024
Version 1.9.12.91 (Fanless Engine)
Version 1.9.12.91 (R2 Platform - 1RU)
Version 1.9.12.91 (Virtual Machine)
Added a Calendar Resource Display control to user panels. This control requires a scheduling license to function. Review the beta documentation for details on how to use this control.
Fixed an issue with Timers where the DerivedStartTime property changes were not always being raised to SapV2.
Fixed a bug where the hover tooltip on calendar items was showing the resource name when it should show either the event name or description
Version 1.9.12.90 04/26/2024
Version 1.9.12.90 (Fanless Engine)
Version 1.9.12.90 (R2 Platform - 1RU)
Version 1.9.12.90 (Virtual Machine)
Updated component licensing
Changed login state on devices page to immediately switch to None on loss of connection as this was looking incorrect.
Fixed a bug in device emulators list user interface where incoming connections to a listener were being listed in the port field. There is some usefulness to having this information in this table so we also added a ticket for a future feature change to add an additional column to display this state information.
Copyright update.
Made an adjustment to the RestApi client. If you remove the Authentication line from the header and then configure a user name and password, the client will now try to figure out the methodology for authentication. This is working for digest authentication on some test systems.
Version 1.9.12.89 04/16/2024
Version 1.9.12.89 (Fanless Engine)
Version 1.9.12.89 (R2 Platform - 1RU)
Version 1.9.12.89 (Virtual Machine)
Fixed an issue where xml data in a memory slot would not display in the memory slots data grid.
Added code to force a mouseup on user panel buttons if the mouse slides off the button while the mouse button is down. Without this, the button could get latched in the down state.
Note: This is not working inside a full console widget at this point in time.
Added an option to RestAPI devices called AllowEscapeChars which if turned on will cause header and data messages to convert standard Pathfinder escape sequences (like cr\lf\) to the requisite escaped values. To prevent backwards compatibility issues, this is an option that has to be turned on. Use the edit link in the devices page for the parfticular Rest API device.
Made changes to Aes67 message handling by device type as follows
Removed some old code relative to Vmixers that was never supported.
Changed Aes67 output addressing such that fmt is included whenever the multicast IP address is outside of the livewire range.
Added an exception check in the Router Manager during routes for when the destination device type is Engine or Powerstation which will then exclude the fmt syntax as neither of these support the fmt syntax.
Note: Fusion software must be at version 3.2.2 or later to work with Aes67 sources with this version of Pathfinder as that is the version where the fmt syntax was added. If you need this functionality in Fusion, please upgrade the software in your Fusion in conjunction with this update. Click here to download Fusion 3.2.2. https://telos-support.s3.amazonaws.com/Axia/Fusion/1601-00531-019-Fusion-3.2.2f.tar
Note: iPort classic software must be at version 2.4.4 or later to work with Aes67 sources with this version of Pathfinder as that is the version where the fmt syntax was added. If you need this functionality in iPort classic, please upgrade the software in your iPort in conjunction with this update. Click here to download iPort 2.4.8a. Please refer to this document regarding updating your iPort.
Added RecordModeStat (recmode_stat) property to the Quasar AppControl Object
Warning: This is currently configured in Pathfinder as a RW property, but is only RO in the latest version of the Quasar software. We made it RW in Pathfinder because it is slated to become RW in the Quasar software as well in the future.
Fixed a situation where if a scene item's requested value is blank, it would not get set to active after startup if the source property was also blank on startup.
Changed LwcpSs fader automix property from amix to amen for Qor, iQx, iQs, and Altus as that is what the property is in current software.
Added an Automix object and properties to act as a target for show profile amix change values. Previously this was causing a log message because there was no LwcpSs target for the property.
Changed Logic Flow removal file naming to a hash of the previous name. The removal file only gets created and used if a system is clustered, the cluster is currently disconnected, and a flow gets deleted. It holds the deletion information for future cluster synchronization. Previously it was named in a way that could exceed operating system file name size limits.
Changed the setting of CurrentChannelNumber property in Axia Audio routers such that if the requested channel number is 0, double quotes are sent to clear the route rather than sending 239.192.0.0. This is because numerous Axia devices do not see 239.192.0.0 as a valid livewire channel. That multicast address can still be used via Aes67 syntax in devices that support that syntax.
Made some changes to interval timers to prevent state fluttering when AutoReset is off and the interval time is very short (~200ms), and the systems are clustered.
Version 1.9.12.88 03/07/2024
Version 1.9.12.88 (Fanless Engine)
Version 1.9.12.88 (R2 Platform - 1RU)
Version 1.9.12.88 (Virtual Machine)
Warning: Please review all notes for 1.9.12.87 as well as this version has those changes as well.
Fixed an issue introduced in 1.9.12.77 where the simple tree in the logic flow editor was not displaying xNode mixer options.
Fixed an issue introduced in the timer changes between 1.9.12.83 and 1.9.12.87 where a timer instance might still raise events after being disabled or deleted.
Version 1.9.12.87 03/06/2024
Version 1.9.12.87 (Fanless Engine)
Version 1.9.12.87 (R2 Platform - 1RU)
Version 1.9.12.87 (Virtual Machine)Change hint type
Warning: This version makes major underlying changes to the timer system that raises interval, date/time, day of week, and calendar timers. While the user experience should differ very little, the code driving these systems has changed significantly as described below. Please report any issues you may encounter.
This version is a major rewrite of how times and calendar events are managed in favor of a number of libraries instead of custom code.
Corrects a very rare but occasional situation where a calendar based event might not fire correctly.
Corrects multiple issues with how time zones and Daylight Savings time are handled.
Each Date/Time and Recurring (DayOfWeek) event now also carries a field that holds the time zone used to create the event. The event will follow the DST rules of the time zone for which the event was created. This differs from the previous version where events were coerced into Pathfinder's time zone and followed its DST rules. In previous versions after a DST change, clock based events were updated with the new offset. Now the event does not change the offset of the underlying event but uses the time zone field accordingly.
Added the time zone field to the date/time and dayofweek event editors.
Selecting a different time zone in the calendar will also cause events created when the calendar is in the time zone to be created with the selected time zone.
Solidified the rules around what happens during DST skip forward and DST fall back times when clock as opposed to fixed mode is selected as follows:
Skip Forward Recurring (DayOfWeek) Events:
If a recurring event starts before skip forward and ends in the DST skip time, it will be displayed in the calendar with a black background and a note that the end will be skipped. Any ending behavior will be skipped when the event executes on that day.
If a recurring event starts during the skip forward time and ends after the DST skip time, it will be displayed in the calendar with a black background and a note that the start will be skipped. Any starting behavior will be skipped when the event executes on that day.
If a recurring event exists entirely in the skip range, it will be displayed in the calendar with a black background and a note saying the event will be skipped. No behavior for the event will execute.
If a recurring event spans the skip time, it will be displayed in the calendar as normal. When executed however, it will respect the start and end times meaning the actual execution duration will be reduced by the skip forward duration. For example, a 90 minute event spanning the skip forward time range will only execute for 30 minutes if the skip forward is one hour.
Dragging a recurring event onto the calendar on the skip forward day, with a start or end time in the skip forward time range will be prohibited when attempting to drop the event.
Editing a recurring event on the day of the skip forward such that the end and/or start wind up in the skip forward range will cause alerts and confirmation messages in the time event editor.
API submission - The API will not prevent you from defining illegal combinations of offsets and time zones. Incorrect combinations might cause the time to be advanced to the next hour, the event not to be created, or other ill-defined behavior. Be careful when defining events using the API.
Skip Forward standard (DateTime) events
Dragging a standard event onto the calendar on the skip forward day, with a start time in the skip forward time range will be prohibited when attempting to drop the event.
Dragging a standard event onto the calendar on the skip forward day, with a start time before the skip forward time and an end time in the skip forward time will cause the end time to bump to the same minute in the next hour. The event end will execute at that time.
Editing a standard event on the day of the skip forward such that the end and/or start wind up in the skip forward range will cause alerts and confirmation messages in the time event editor.
API submission - The API will not prevent you from defining illegal combinations of offsets and time zones. Incorrect combinations might cause the time to be advanced to the next hour, the event not to be created, or other ill-defined behavior. Be careful when defining events using the API.
Fall Back standard (DateTime) and recurring (DayOfWeek) Events
All events will execute as defined but only once. They will not execute on the repeat of the hour.
Interval events are unaffected and will continue to execute every x milliseconds.
Made disabled calendar events display with a dark gray background color.
Recurring events will now start on the day on which they were created in the calendar or editor and will not backfill to previous days.
Fixed an issue where the now time line was not properly moving if the calendar time zone was different from the system or browser time zone.
Added a clock in the left corner of the calendar to display the current time in the selected calendar time zone.
Added a window on the time page where an Administrator may define an allowed list of time zones. If time zones are moved into this list then the calendar and timer editors will only allow time zones from that list. By default (empty list), all time zones are allowed.
Fixed an issue in user panel clocks introduced in 1.9.12.81 which was not always displaying the correct time when different time zones were selected for the clock.
Fixed a disappearing flow issue when editing a flow when editing an existing logic flow with a complex value displayed in the current translation value. This was due to the event creation code including the active input and output property value as opposed to just the property name.
Improved the code in the logic flows editor to enforce quoting and encapsulation of certain fields when initializing or rewriting a flow object.
Fixed an issue with submounts under SapProperty Router sources and destinations
Version 1.9.12.83 - 1.9.12.86 1/23/2024 - 3/05/2024
Unreleased versions used during internal testing leading to the list of changes in 1.9.12.87.