PF Release Notes

Version 5.30 Release (PathfinderPCServer, PanelDesigner, PathfinderClient, PathfinderMini) 05/27/2015

1. Compiled as 5.30 Release.

2. Reorganized the zip file into sub folders to help direct where and when items should be installed.

Version 5.20 RC21 (PathfinderPCServer, PanelDesigner) 05/05/2015

Pathfinder_V5-20RC21.zip

PathfinderPCServer5-20RC21.msi

PathfinderPCClient5-20RC21.msi

PathfinderPCMini5-20RC21.msi

1. Added logging options for memory slot changes.

2. Added logging options for hardware button messages. Added two additional log messages, one in ServerEvents (for received messages) and one in ServerActionSent (for sent button messages).

3. Fixed a bug with hardware mapping. When any panel is resaved, the hardware map file is resaved and its version is updated. PFS re-ingests the hardware map. In previous versions it would then recreate the mapping internally. However when it was doing this it was clearing an internal register rather than inheriting the previous state. This internal state would only get pushed out to the hardware if there was a loss and gain of connection. The result in some cases can be a default state from the panel file on the hardware panel rather than the states altered by the stack events. This version synchronizes the state from the software panel ram states and we keep the old object whenever possible instead of recreating. It has been designed to be more intelligent regarding the changes in the hardwaremap file.

Reproduce steps are as follows:

- Set a panel up with a hardware map

- Change the colors/text to something other than defined in the panel file using a stack event

- Edit the panel file (or any other panel file) and change something and resave

- reboot the element or panel or otherwise force a loss of connection and reconnect

- PFS will push out the default state rather than the actual state of the software panel.

4. Added a push of synchronized hardware button state to the hardware for any newly encountered hardware map in the xml file.

5. Removed the gradient from the stack event editing backgrounds in order to generate faster displays on machines with less gpu power.

6. Fixed a bug in PanelDesigner that caused the scroll bar next to the property list to not scroll to the bottom of the list.

7. Increased the default width of the property panel in Panel Designer when the application opens.

8. Compiled all applications as 5.20RC21. Client and Mini did not change since 5.16RC17. We just recompiled to get all the versions in line.

Version 5.19 RC20 (PathfinderPCServer) 03/24/2015

PathfinderPCServer5-19RC20.msi

1. Added an additional safety check to make sure a stack event is truly missing in the file system before marking it as deleted in the clustering database.

2. Fixed a bug where copying a stack event from the main PathfinderServer application would not update the version stamp inside the copied file. This could cause a file not to synchronize in clustering under the following scenario: Create a stack event. Copy the stack event. Then after the copy synchronizes, delete the stack event and let the delete synchronize. Then copy the original again with the same copied name. The new copy will have the original file's version stamp which is older than the delete stamp and therefore the secondary server will consider the delete more recent and current. This has been fixed so that the copy process updates the version stamp in the newly copied file.

Version 5.18 RC19 (PathfinderPCServer) 03/20/2015

PathfinderPCServer5-18RC19.msi

1. Fixed a bug in the probel general switcher protocol. If messages were retrieved from the serial port in such a way that they were split in the reception after the 4th byte, it is possible the message could be dropped. This has been fixed.

2. Fixed a bug in the generic translator that was occasionally stripping an extra character out of the buffer during analysis.

3. Fixed a bug in the generic translator and stack events. If two matches for a protocol translation qualifier came in together (virtually same packet), the event would only fire once. But it might then fire erroneously if more data comes in within 5 seconds of the original data. This has been fixed. It now fires twice immediately and the buffer is properly cleared up through the second instance of the data. Warning - this could potentially be a breaking change if anyone is pushing double commands. You can still push double commands for serial safety sake by moving the action into delayed actions and issuing a short (100ms) timeout. When the second message is analyzed, if the countdown timer is already counting it will not run the second time.

Version 5.17 RC18 (PathfinderPCServer) 03/09/2015

PathfinderPCServer5-17RC18.msi

1. The timer which looks for panel changes would update the date modified cache whether or not it could read the version stamp from the xml. This could potentially cause a file that was still in the progress of being saved not to send a cluster update message until the next time it was updated. This is a theoretical possibility. We have not actually been able to observe this behavior. But it might explain the one panel update issue at one site. This version will not update the file date modified cache until it is able to successfully extract or insert a version stamp to/from the xml.

2. If a router was transitioning existence/delete states it is theoretically possible that the routes table might get updated but not the XCoord or YCoord during a cluster synchronization after the update. Through a great deal of testing we have not been able to reproduce this issue, but the code appears that it is a possibility and it might explain an issue at one site where they had a router table with an update but the other two tables were not updated.

3. Added a Clustering logging option that will log clustering information. If this is needed, it should be enabled on both servers to be useful as its primary use is to track clustering changes between the servers. This will not log memory slot and panel control clustering states as that could cause an excessive io load. It will log panel file, stack event file, and router definition changes as they traverse the cluster. If this is on, it could generate a lot of messages during startup and converging.

4. Found that the table versions message if on a delete was not updating the date/time in the b server. This appears to be a benign issue but it has been fixed.

5. Fixed a benign system error trap message that can occur with silence alarms if the alarm is deleted and cleared after the OS has already raised a timer tick but before we have processed it.

6. Fixed a bug with TableVersions Delete Table that was sometimes causing the first item in the table to be marked as deleted instead. Since this is always ServRouters and it cannot be deleted, this appears to be benign but has been fixed

7. Added a fix function on startup that makes sure certain tables that should never be removed are marked as active. This overrides any past possible inconsistencies with these tables states.

Version 5.16 RC17 (PathfinderPCServer, PathfinderPCClient) 03/04/2015

PathfinderPCServer5-16RC17.msi

PathfinderPCClient5-16RC17.msi

1. Fixed a benign issue that was causing system error trap log messages with certain protocol translators where no error should be posted.

2. Increased the timeout for the hardware panel to 20 seconds with 2500ms pings. This is to make sure we do not drop the connection to the panel under higher load situations.

3. Increased the timeout for the master timer to 10 * timeout value if over 10000. This should reduce master timer failure log messages under higher load situations.

4. Fixed a bug in the client where after selecting a destination to be included in a scene, that destination is still available to be selected for the scene again, but the one below it is not.

5. Fixed a bug in the client where minimizing the scene editing window causes the client to crash.

6. Fixed a bug in server where when a full table update on the standard events table takes place via clustering (as opposed to a single record change in an existing cluster) the visible recordset was not being updated to reflect the change. So for example if B server was shut down, and standard events were added to A, when B was started up again the changes from A would get written to the underlying file but were not being updated in the visible active recordset because a refresh on that recordset was not being called. That would mean that a client connected to B would not see those events and when adding new records might overwrite existing records on A since B would accidentally reuse ids. This has been fixed.

Version 5.15 RC16 (PathfinderPCServer, PathfinderPCClient, PathfinderPCMini, PanelDesigner, SAMeterServ, AllFiles package) 01/13/2015

Pathfinder_V5-15RC16.zip

PathfinderPCServer5-15RC16.msi

PathfinderPCClient5-15RC16.msi

PathfinderPCMini5-15RC16.msi
Help_500.pdf

1. Fixed a bug where if an IO on the Audio router was hidden, and Automatic Addition was turned on, it could reappear a duplicate time in the database.

2. In SAMeterServ, added a method so that -1000,-1000 peek values are ignored the first couple times they are seen consecutively. This can cause a slight delay of showing no level during the fadeout of a song, but fixes a problem with the XNodes where the xnodes may occasionally return an incorrect -1000,-1000 peek values in the middle of legitimate audio causing the meters to flicker off momentarily. Still may be an occasional flicker until the XNode team has a chance to confirm and fix or provide alternate query methods.

3. SAMeterServ subscriptions from a client were not being removed if the client disconnected without first unsubscribing. This should be fixed in the version.

4. SAMeterServ is compiled as 1.08.

5. Fixed a bug in client and mini that was still causing some metering flickering. It was writing data from the PFServer every few seconds to the meter which should be ignored when using the SAMeterServ.

6. See notes for version 5.14RC15 and 5.13RC14 as they were not made available on the site and were internal only. But the change notes apply to this version as well.

Version 5.14 RC15 (Internal only) (PathfinderPCServer, AllFiles package) 11/19/2014

PathfinderPCServer5-14RC15.msi

Pathfinder_V5-14RC15.zip
Help_500.pdf

1. Added support for the Fusion Console

2. Added stack event support for the Fusion Soft Buttons in the monitor section and on each fader.

3. In the stack event UI, changed the name of Element Profile to Console Profile.

4. Fixed a bug where if a function was used to assign a caption value in a stack event (i.e. funct:MemorySlotValue(Hello)) and the result of that function was a blank string then the caption would not get cleared from the previous value.

Version 5.13 RC14 (Internal only) (PathfinderPCServer, PathfinderPCClient, PathfinderMini, PanelDesigner) 11/18/2014

PathfinderPCServer5-13RC14.msi

PathfinderPCClient5-13RC14.msi

PathfinderPCMini5-13RC14.msi

PanelDesigner5-13RC14.msi
Help_500.pdf

1. Changed the label control in PanelDesigner, PathfinderPCClient, and PathfinderMini for panels to support multiple lines. Lines may be split using the \n character in the same way they are split for buttons.

2. Added a SetPanelProperty command to SapV1 on port 9500. This allows you to set panel properties via port 9500. Example:

SetPanelProperty Panel2.MyLanel2.Caption=Hello\nThere

Version 5.12 RC13 (PathfinderPCServer) 10/28/2014

PathfinderPCServer5-12RC13.msi

1. Fixed a bug where adding a daily event to standard events would cause other events that had already executed that day to show pending instead of completed successfully in the time events list in the client.

2. Added code to send memory slots that have been cleared but were at one point set to the other server during cluster synchronization.

3. Fixed an issue with the deletememoryslot command from port 9500. It would not work if using 0 (for memory slot 0). It only affected that slot from the port 9500 not from stack events. This has been fixed.

4. Added code to clear any and all memory slots of a given name instead of just the first one when a delete memory slot command is used from port 9500 or from a stack event. This will handle any rogue name duplications in the slot list if it exists.

5. The memory slot issues described above fix an issue where in certain rare situations a duplicate named memory slot can be created. This happens most easily in a cluster if one of the servers is set to remember memory slots and the other is not. The extra memory slot is now harmless as the program will only ever use the first in the list by that name. However if the logic deleted the slot and depends on the slot being deleted it could theoretically have caused an issue prior to this version because the slot would still exist. Therefore this version will delete duplicates when a slot is cleared. It also adds some clustering code to virtually eliminate duplicate memory slots being created in the first place. However, there are still certain situations especially with a misconfigured remember memory slot state in a cluster where a benign duplicate slot could exist. If you wish to delete this slot manually simply login to port 9500 and call deletememoryslot and the number of the duplicate slot rather than the name. (i.e. deletememoryslot 34).

Notes:

- After upgrading to this version on both servers and verifying that remember memory slots is either on or off on both servers (as opposed to mismatched), if you wish to clean up any harmless duplicate slots that might exist from the prior version use the following commands after logging into port 9500:

getmemoryslot au (lists all used slots)

deletememoruslot <number of second duplicate slot> (review output above to find any duplicates)

- It is important to consider whether the remember memory slots option should be used. If the stack events may be designed in a way to initialize the slots as needed and/or on startup, this will be a cleaner solution than using the remember memory slot option. It will also reduce the cpu load slightly because we do not have to write slot changes to the disk (database). However, using this option is fine as well and the impact is minimal, but in almost all situations both servers should be set the same for this option. It is important to note that the slots do not get written to the database immediately. In an effort to complete the mission critical work as fast as possible, slot changes are written to the database in a batch approximately 500ms after the change request.

Version 5.11 RC12 (PathfinderPCServer) 10/20/2014

PathfinderPCServer5-11RC12.msi

PathfinderPCClient5-11RC12.msi
Help_500.pdf

1. Fixed an issue with SA_MeterServ where if a client connected and tried to subscribe to a meter using a PathfinderId before the service had contacted PathfinderServer to obtain the PathfinderId to IP/Port lookup table, the meter would not work. Restarting the client or mini would get this working again. This could possibly happen in rare situation during a server restart. This version does not open the meter subscription port for clients until it has successfully obtained the lookup list from PathfinderServer.

2. Modified the SA_MeterServ service to catalog the NCHN parameter (Number of Channels) from the device. If the number of channels is 0 the service will output -1000,-1000 to subscribing clients. If the number of channels is 1, then the service will copy the left parameter of the MTR response into both Left and Right being sent to the subscribers. If the number of channels is 2 it will clone exactly what MTR returns. This should make meters look correct with Xnode if the channels are in mono.

3. Fixed a bug where if a stack event clears a memory slot (using the clear check box in the stack event memory slot config), that clear state would not get replicated in the secondary server of the cluster. This could lead to incorrect data in a slot on the secondary server during a failover. This only affects memory slots when the stack event uses the clear option.

4. In Pathfinder client when looking at the time based event grid, changed the Time column to default to military time. It can be switched to AM/PM by right clicking on the header of the time column.

5. In Pathfinder client fixed a sorting issue where date time values in the time based event grid were sorting the times alphabetically rather than by actual time. This would lead to 3AM appearing after 2PM in the sorted list. This has been fixed.

Version 5.10 RC11 (PathfinderPCServer) 8/25/2014

PathfinderPCServer5-10RC11.msi
Help_500.pdf

1. Fixed a bug with router editing. If you start editing a router and click to a different router while the editing window for the previous router is open, the software may overwrite the wrong router. This has been fixed.

2. Fixed a bug with copying a complete stack event group from the main Pathfinder window. The copy was not taking all parameters in some cases. This has been fixed. It was reproducible by creating a stack event with a Axia console change action. Then once the stack event group is complete and the stack event editing window is closed, copying that group from the main Pathfinder window using the copy button. When you edit the copy parameters in the xonsole change would be missing.

Version 5.09 RC10 (PathfinderPCServer) 8/14/2014

PathfinderPCServer5-09RC10.msi
Help_500.pdf

1. Fixed a bug with stack event silence and audio present qualifiers. Timeout values longer than 32 seconds would not fire the actions. This has been fixed.

2. Fixed a bug in the stack event editor with numerical value fields. The lowest and highest setting in the field would write correctly to the xml file, but when the qualifier or action was opened again it would display a default 0 value instead of the selected value. For example if you set the fader_gain to -80 which is the lowest allowable setting and then moved to a different qualifier/action and came back the value would display as zero. This is fixed.

Version 5.08 RC9 (PathfinderPCServer) 7/1/2014

PathfinderPCServer5-08RC9.msi
Help_500.pdf

1. Fixed an issue with the Gpio by pin router. If the incoming source pin change to low and back to high involved in a pin route happens very fast or is processed close together due to server load, the destination pin could be left in the first state. This is because the message which has been sent to the device to switch to low has not returned yet. The server therefore was thinking the destination was already in the second state (high) and was therefore not sending the second change request into the debounce function. This has been fixed.

Version 5.07 RC8 (PathfinderPCClient) 7/1/2014

PathfinderPCClient5-07RC8.msi
Help_500.pdf

1. Fixed a graphics bug with chart view. Maximize a chart window. Then open another maximized router. Then close the newly opened router. The original maximized router does not redraw correctly and remains small with cutoff blank space. This can be fixed by closing and reopening the router or sometimes by making the window state normal and then maximized again.

2. Fixed a graphics bug with chart view that can cause the chart dots to become stuck in scrolling or unable to draw properly. Fixed this by adding some disposal code to the graphics objects and also using a reuse pool of objects.

3. Added a warning message if the chart drawing encounters an error. This will alert the user that a charting error has been encountered and the router and/or client application should be reopened in order to trust the charting results. Please alert support to instances where this message appears so that we may fix the issue. The goal would be for this message to never appear but we decided it was preferable to alert the user to the potential problem rather than continue and possibly present bad information.

4. Added a validation function when the take button is pressed that compares the take panel parameters and make sure they make sense in correlation with selected lines in the currently focused chart view and or names/ids in the currently focused list view. If the validation function fails the user will be presented with a message alerting them to the discrepancy and suggesting that they reselect the route points and retake the route. They are offered the option to continue with the take anyway. This message also ideally would never appear, but we decided it was better to alert the user to the possible discrepancy rather than completing the take.

5. Fixed a situation where occasionally when expanding a new chart the newly loaded lines would be loaded blue rather than black giving the impression that multiple sources or destinations were selected.

6. In previous versions the source in the take panel would return to the currently routed source after 60 seconds of inactivity. This means that user could not preset a take more than 60 seconds in advance of the change. That has been removed in this version. The take panel will remain on the selection indefinitely until the user selects something else.

7. Related to item 6 above there was a bug in chart view where after the 60 seconds when the source fell back to the original source the destination might also move to the selection currently selected in the hidden list view rather than the one last selected in chart view. This has also been fixed both in the code and as part of the removal of the 60 second timer.

8. Fixed an issue where when switching between routers the take panel would still sometimes show the IO number and name from the previous router. This could be different than what was actually shown as selected in the list or chart. This could leave to incorrect routes because the wrong id was in the take panel when the take button was pressed. This has been fixed.

9. Fixed a bug where is the description field in chart view was visible when switching to list view the field would still be visible over the top of the list. This has been fixed.

10. Fixed a bug where right clicking on cross points or x-y labels in chart view was not always bringing up the correct IO's meters.

11. Fixed a bug where the selected IO lines were moving on the non-focused router when making router changes on the focused router when both were open in chart view. This probably only existed in versions since 5-01 RC3.

12. Fixed a bug where the lock state was not displaying in the chart view when changing destinations using the chart y labels. It was also not updating the route information panel correctly. This is also probably only a problem since 5.00.

13. Fixed an issue where switching from list view to chart view was not selecting the destination in chart view that was selected in list view.

14. The take panel now gets blanked out when a router window is not selected as the foreground window. If no routers are open or if a user panel or meter window is foreground, the take panel will be blank so there is no confusion as to what router the take panel is addressing.

15. Fixed a bug that could yield a negative offset on the scroll bar and therefore cause the newly created ChartRoutes failure message.

16. Fixed an issue with the >> button with a maximized router that did not need to have any scrolling. There is still some internal debate as to how this button should function in chart view so there may be additional changes to this button's functionality in chart view in the future.

17. Fixed a display issue. Maximize a chart view and then open another router maximized. Close the second router window and the first router window would not redraw correctly. The crosspoint dots were not reloading properly in this case. This should be fixed in this version.

Version 5.01 RC3 (PathfinderPCClient) 6/11/2014

PathfinderPCClient5-02RC3.msi
Help_500.pdf

1. Fixed an issue with retaking existing routes on routers whose id numbers are not sequential. There was a bug that if a router's numbers were not sequential an incorrect source value could get entered into the fallback field of the pending route object. If no route change was returned from the server this would mean that the visual display would fallback to the incorrect source. The root of this problem related to taking the source value from the ordinal position in the list rather than based on the id number. In the case where the same route change is taken again as is often the case with a scene change this could mean erroneous results and routes that visually appear to spontaneously switch even though the audio does not switch. Reopening the router in the client would fix the problem. This has been fixed in two ways. First, the correct information is now entered into the pending object. Second retakes (route changes of a source and destination that are already routes) do not end up creating a pending object since the route already exists.

2. Fixed a display issue. Maximize a chart view and then open another router maximized. Close the second router window and the first router window would not redraw correctly. The crosspoint dots were not reloading properly in this case. This should be fixed in this version.

Version 5.01 RC2 (PathfinderPCClient) 5/30/2014

Pathfinder_V5-01RC2.zip
Help_500.pdf

1. Fixed an issue with chart view in PathfinderPCClient. Double clicking anywhere in the chart would take the selected crosspoint even if that selection was nowhere near the current mouse location. Now the software will check to make sure the mouse is over the selected crosspoint before issuing the Take command.

Version 5.00 RC1a (SAGpioNode) 5/26/2014

Pathfinder_V5-00RC1a.zip
Help_500.pdf

1. SAGpioNode at one point had some rudimentary multicast capabilities but that has largely been replaced by the multicast gpio node service. However by default the config file enabled multicast causing a conflict if this service was installed on the same machine as the multicast gpio service. This has been fixed so that the config file now by default uses 0.0.0.0 in the LocalMulticastIp field which effectively disables the multicast in SAGpioNode. If the service has already been installed, this problem may be fixed by shutting down SAGpioNode, changing the config file LocalMulticastIp field to 0.0.0.0 and then restarting both the multicast gpio service and SAGpioNode.

Version 5.00 RC1 (Server, Client, Mini, VmixControl) 4/06/2014

Pathfinder_V5-00RC1.zip
Help_500.pdf

1. Fixed the default min pulse length of PFSRemote routers from 5000 to 100ms. This only affects PFSRemote routers that were pre-existing before an upgrade and therefore have blank data in the Other field.

2. Adding snapshot rows - column header said Source when it should have said Destination.

3. A connection failure in certain situations was not tripping the device failure state and therefore not tripping stack events relying on that. This seemed to be most noticeable with XNode but might intermittently fail to report device failures in other equipment as well. This has been fixed.

4. Removed the old help system and made help and f1 in all projects (except mini) open Help.pdf. Removed the .chm file from the install builder and added help.pdf including a shortcut.

5. Added MulticastGpio service to the version 5.00 applications. Help file is updated to discuss this service. May need to manually start the service or reboot after installing. Pay attention to the manual regarding required versions of .net for this service.

6. Created a zip file with all applications for version 5.00 release candidate.

Version 4.99p (internal release only) (Server) 2/04/2014

PathfinderPCServerBeta4-99p.msi

1. Fixed a bug where the stack event disable from the PFS server main page would not always actually disable the event in the code and the event would continue to fire despite being marked as disabled.

2. Fixed a bug in the stack event editor where if you disable an event in a group without opening the event's qualifiers and actions, it might take 30 seconds to enable/disable after applying.

3. Fixed a bug in the stack event editor where the iport icon was not displaying.

Version 1.07 (internal release only) (VMixControl) 2/03/2014

VmixControl1-07.msi

1. Fixed a bug that was causing the name fields on the faders to show data from a previously selected vmix group if the field should be blank. This only occurred when working with certain engine software versions.

2. Engine ADDR field of 255.255.255.255 is now displayed as an empty route in the same way as a blank ADDR field.

3. If the engine reports an address with no name a name of (No Name) is shown.

Version 4.99o (internal release only) (Server) 1/30/2014

PathfinderPCServerBeta4-99o.msi

1. Fixed a bug when creating a new translator. If certain options were selected during the sync the translator might write those options to the data but not start those options automatically. This has been fixed. This was due to the function trying to pull those few fields from the viewer's current record rather than the actual new record when starting the translator.

Version 4.99n (internal release only) (Server) 1/27/2014

PathfinderPCServerBeta4-99n.msi

1. Fixed a the same space issue below when a single new translator was being synchronized in clustering rather than the full table.

Version 4.99m (internal release only) (Server) 1/23/2014

PathfinderPCServerBeta4-99m.msi

1. Fixed a potenetial issue with the master timer if a silence alarm was in progress at the 24 day loop point. Never reported as an issue but the code indicated it could potentially be one.

2. Fixed a benign system error log message.

3. Disallowed a blank space as a sleep/wake command in protocol translators. If this is needed use a regex or escaped hex command.

4. Fixed a bug where when a full table sync of the protocol translation table was taking place it was possible that a space would get entered in the sleep command at the receiving end potentially allowing the translator to go to sleep when a space was received.

Version 4.99l/j (internal release only) (Server/Client/Mini) 1/18/2014

PathfinderPCServerBeta4-99l.msi

PathfinderPCClientBeta4-99j.msi

PathfinderPCMiniBeta4-99j.msi

1. Fixed an issue where the GPIOByPin router was polling large amounts of route and gpio status data every 30 seconds from the main gpio router. This could cause thousands of messages to have to be analyzed by the pin router every 30 seconds causing a load on the cpu for both generation and analysis. This has been fixed.

2. Increased certain iterator maximums to handle larger trees in the GPIOByPin router tree.

3. Fixed a bug with VMIXers larger that 8 when the engine as the IOStat command that allows changing of the VMIX name.

4. Fixed issues with the VMIX Software Authority protocol translator commands with VMIXers above 8.

5. Added a minimum pulse length option to the GPIOByPin router.

6. Added a status priority for main SAPort and protocol translators. Selecting HighPriority (default) means GPIO and route change status changes are sent immediately instead of put into a lower priority queue. Selecting LowPriority means it works more like it previously has where GPIO and Route change status change messages are placed in a queue and sent 10ms or more later. This can be changed for the main SAPort under the Master TCP Socket settings dialog and in the individual protocol translator dialogs for other protocol translators.

7. This version compiled on new build server virtual machine.

8. Added the ability to unsubscribe and subscribe to route changes and gpiochanges on port 9500

subscribe routechanges all

unsubscribe routechanges all

subscribe gpiochanges all

unsubscribe gpiochanges all

subscribe routechanges 1

unsubscribe routechanges 1

subscribe gpiochanges 1

unsubscribe gpiochanges 1

By default all connections default to All for both Gpiochanges and routechanges to support backwards compatibility.

So if you only want to see route changes, connect, login, and send:

unsubscribe gpiochanges all

Or if you only want to see gpiochanges from a specific router send something like:

unsubscribe routechanges all

unsubscribe gpiochanges all

subscribe gpiochanges 1

9. Changed the RemoteByPin router to unsubscribe from route changes so that those changes are not sent and it does not need to parse those changes.

10. Added log messages in ProbelRouter protocol translator for

Probel Nak received

Probel Nak send

Probel Timeout resend

11. Added a column to the device list to show connection state and used a 1000ms timer to poll that state for any connections that are in the current view.

12. Added a button to the device list to push the init commands again to the selected device connection.

13. Added a button to the device list to drop and reconnect the specific device connection. After dropping it will wait 5 seconds and then reconnect.

14. Fixed a bug with the loop inhibitor. The loop point where gettickcount went from positive to negative had a bug in its analysis which would cause stack event actions to stop running for the duration of that day. It could be gotten working again by resaving the stack event group or by restarting the server. This has been fixed in this version.

15. Added additional error trapping code to prevent a loop inhibitor analysis failure from preventing the actions from executing.

Version 4.99d (internal release only) (Server) 10/09/2013

PathfinderPCServerBeta4-99d.msi

1. Added the ENGINEACL device type for the vilor blade based engines so that VMIX can be used with this device type

2. Temporarily added version 0.1.0e2 as a VMIX enabled version for device type Engine until Gints can change the device name of these blade engines to ENGINEACL

3. Moved the ip address in the VMIX responses for subscriptions and the VMIXState command to the end of the command response lines instead of the beginning

4. Fixed a bug where the subscribed VmixState response was returning VMIX.SUB#1 rather than SUB#1 to match the other VMIX state commands

Version 4.99d (internal release only) (Client) 10/08/2013

PathfinderPcClientBeta4-99d.msi

1. Fixed a bug where the last destination in the router would not display description information when moused over.

Version 4.99c (internal release only) (Client) 10/08/2013

PathfinderPCClientBeta4-99c.msi

1. Fixed a bug where the chart would jump back to the currently selected item on any data update after scrolling to another place.

2. Fixed a bug in the list view where if a sort was in place and you scrolled beyond the selected item, the list would jump back to the selected item.

3. Fixed a bug where the double click of the source and destination names to jump through the routed points related to that source or destination would not work if the list had been sorted prior to going into chart view.

Version 4.99b (internal release only) (Server) 10/08/2013

PathfinderPCServerBeta4-99b.msi

1. Fixed an issue related to IDC receivers. Since they only have sources and not destinations, the device scanner was not picking them up and adding them into the system. This has been fixed.

2. Added the ability to delete multicast Gpio points when used with the MultiastGpioManagement service from the Liveiwre Gpio router wizard. Expand until you get to the channel source or destination under the MulticastGpio device and select the source or destination and then click remove. To entirely remove the channel you must remove it under both sources and destinations.

3. Added some unlisted commands to the SapV1 port 9500 help (?) reponse.

4. Alphabetized the response to help (?) in SapV1.

5. Added vmixstate and vmixgain as arguments to the subscribe command in SapV1 (i.e. subscribe vmixgain) (i.e. subscribe vmixstate)

6. Added the IncludeIp option to the SapV1 VmixState command

7. Example:

>>VMIXState 172.16.1.60 1

SUB#1.IN#1 ON -0.5 db 1.0 Secs 5.0 Secs

SUB#1.IN#2 ON -0.5 db 1.0 Secs 5.0 Secs

SUB#1.IN#3 ON -0.5 db 1.0 Secs 5.0 Secs

SUB#1.IN#4 ON -0.5 db 0.0 Secs 0.0 Secs

SUB#1.IN#5 ON -0.5 db 0.0 Secs 0.0 Secs

>>vmixstate 172.16.1.60 1 IncludeIp

172.16.1.60 SUB#1.IN#1 ON -0.5 db 1.0 Secs 5.0 Secs

172.16.1.60 SUB#1.IN#2 ON -0.5 db 1.0 Secs 5.0 Secs

172.16.1.60 SUB#1.IN#3 ON -0.5 db 1.0 Secs 5.0 Secs

172.16.1.60 SUB#1.IN#4 ON -0.5 db 0.0 Secs 0.0 Secs

172.16.1.60 SUB#1.IN#5 ON -0.5 db 0.0 Secs 0.0 Secs

Version 4.99b (internal release only) (Client) 10/08/2013

PathfinderPCClientBeta4-99b.msi

1. Fixed a bug in the chart view that was causing the routing dots to sometimes be off center.

2. Fixed a bug in the chart view that was causing the bottom of the form to cover up some of the destination names - especially in virtual routers. Names over 14 to 16 characters may have the end of the name cut off but mousing over them will display additional information as described below. This is by design for screen real estate reasons.

3. Fixed a bug in the chart view that was sometimes not displaying the grid lines for the bottom few sources in the router.

4. Right clicking a source name in the chart view will now open the source's meter.

5. Right clicking a destination name in the chart view will now open the destination's meter.

6. Right clicking a cross point bubble in the chart view will now open the corresponding source and destination meters

7. Mousing over source and destination names in the chart view now shows the description information of the source or destination at the bottom of the grid.

8. Double clicking on a destination name in the chart view will scroll to the source routed to that destination if there is a source routed to that destination

9. Double clicking on a source name in the chart view will iteratively jump to the next destination that source is routed to if the source is routed to any destinations

10. Double clicking entries in the search form will now scroll to that source or destination in the chart view.

Version 4.99 (internal release only) (Server, Client, Mini) 10/01/2013

PathfinderPCServerBeta4-99.msi

PathfinderPCClientBeta4-99.msi

PathfinderPCMiniBeta4-99.msi

1. Used a memory table for puid lookup and generation during the GpioByPort and GpioByPin router creation finish rather than multiple database calls in order to greatly reduce CPU load and time of completion when editing these routers. With a large router which we were testing with, this completion was spiking the CPU for upwards of 90 seconds. Now it completes in less than 2.

2. Also found a bug that may have been causing the PUID table not to be synchronized between cluster nodes in all cases.

3. Changed the command analysis loop counter in the client and mini to handle more inbound commands (from integer to long) to handle very large panels with very large numbers of controls.

4. If a virtual router database has a duplicate id which should never happen except in the case of very rare manually edited database corruption, the system will continue to load the rest of the ios.

5. Crafted a new destination watch list for route mapped buttons and script route monitoring. It uses keyed (indexed) collections on both the control name and the router_Dest in order to find watches without having to loop through all watches. Also remarked out a few calls to check the watch status which appeared to be redundant and just causing extra CPU load and noise. This reduces the CPU load starting large panels with large numbers of route mapped controls.

6. Added the SystemErrorTrap log message. This allows function error traps to be directed to the log. This option is not enabled in the logging by default in this version. This logs code error trps.

7. Added code to retain the silence, clipping, and hidden database states after adding/removing equipment in the AxiaAudio and AxiaGpio routers. Also modified the lookups for this information during the rebuild to use a key rather than a loop to increase performance during the router creation.

8. Increased the messages in the client and mini that will cause a restart of the connection timeout. This helps to prevent the client from timing out during large panel or router loads.

9. Known Issues:

1. GpioRouterByPort and by pin is CPU intensive when populating the selection tree.

2. In the client, if the router is sorted by one of the columns and a record is selected and you scroll beyond that record, it will sometimes spontaneously scroll back to the selected point.

3. The cross point matrix in the client has some graphical issues that need to be addressed when working with large routers. Occasionally the dot is slightly offset from the cross point rather than centered precisely over the line crossing. The vertical destination names can get cut off. And occasionally the grid does not show the bottom most destination lines. These are long time issues that have been around for a while and will be addressed shortly.

Version 4.98 (internal release only) (Server, Client) 09/18/2013

PathfinderPCServerBeta4-98.msi

PathfinderPCClientBeta4-98.msi

1. Fixed a bug with remote by pin/port routers where when adding and/or removing IOs from the router it would reset all route states. Now it will retain the previous route state for any destinations that were in the router previously.

2. Fixed a bug that was not allowing the sorting of the source list when editing a virtual point using the ellipsis button. This was fixed in both the server and client.

3. Fixed a clustering bug. During the initial cluster sync where you are first pulling the data from the other server, the newly updated system would be left in a state where the newly added server would only present the IOs for the last router of the routers in the system to the client and 9500 for any router requested. It would appear to the user like the last router is cloned to all router numbers if the client was connected to that new server. Restarting that server after the initial sync would fix the problem as a workaround. I found a database recordset that was improperly used leaving a pointer at the wrong recordset to a static router number when initializing the newly created routers. That incorrect recordset pointer was causing the problem. This is fixed.

4. Known Issues:

1. GpioRouterByPort and by pin is CPU intensive when adding or removing IOs to/from the router when the router gets rewritten. We should look at optimizations for this but in the meantime care should be taken as to the time when editing this router type takes place if there are critical operations taking place.

2. In the client, if the router is sorted by one of the columns and a record is selected and you scroll beyond that record, it will sometimes spontaneously scroll back to the selected point.

3. The Hidden IOs field and silence/clipping override field which are a new feature as of 4.97 do not get retained after adding equipment to the router and have to be re-hidden/set up. This is probably the most critical issue that needs to still be addressed in this version.

4. The cross point matrix in the client has some graphical issues that need to be addressed when working with large routers. Occasionally the dot is slightly offset from the cross point rather than centered precisely over the line crossing. The vertical destination names can get cut off. And occasionally the grid does not show the bottom most destination lines. These are long time issues that have been around for a while and will be addressed shortly.

5. With very large panels (200+ controls). the panel may not be displayed by the client. This is due to the number of commands that are sent from the server to initialize the state of all properties on each control. The buffer which handles these commands is limited to 32000 commands. This will be fixed in the next version. There is a hard limit to the number of controls at about 245 controls.

6. With very large panels with hundreds of route maps (200+ buttons each mapped to a route point on a single panel), there is a heavy multi-second CPU hit on the server when the panel is first opened as the map points are set up. The cause of this hit is now understood and an optimization plan is in place to greatly reduce this cpu hit in the next version.

Version 4.97 (internal release only) (Server, Client, Mini, SAMeterServ, PanelDesigner) 09/09/2013

PathfinderPCServerBeta4-97.msi

PathfinderPCClientBeta4-97.msi

PathfinderPCMiniBeta4-97.msi

PanelDesignerBeta4-97.msi

1. Added control points to the Axia Element Console Change stack event qualifier and action for Element 3.0. This requires Engine software 2.6.4z25 or later.

1. Added Qualifiers:

1. Preview

2. Talk To Studio

3. Talk To Preview

4. Talk To Control Room

5. Talkback

6. Control Room Mute

7. Control Room Dim

8. Studio Mute

9. Studio Dum

10. External Preview

11. Monitor Talk to External

12. Monitor Talk to Control Room

13. IFB Livewire Channel

14. IFB Engaged

2. Added Actions:

1. Preview

2. Talk To Studio

3. Talk To Preview

4. Talk To Control Room

5. Talkback

6. IFB Livewire Channel

7. IFB Engaged

2. Added a Zip One Stack Event Qualifier and Action (Requires software version 1.8.0r or later).

1. ZipOne Qualifiers

1. Call State

2. ZipOne Actions

1. Connect To (Phonebook entry)

2. Drop

3. Loop

4. Codec Profike

5. Codec Mode

6. Codec Min Bitrate

7. Code Max Bitrate

8. Codec Recv Buffer Min

9. Codec Recv Buffer Max

10. Audio Input Source

11. Analog in Left

12. Analog in Right

13. Audio Microphone Gain

14. Audio Transmit Mode

3. Added support for an alpha version of a multicast gpio service. This service allows PathfinderServer to read and write multicast gpio triggers.

4. Fixed a bug with PFS Remote by GPIO pin routers. If a source is routed to a destination and the source pin changes, both servers in the cluster would send the closure to the destination potentially causes double pulses.

5. Added a watchdog to the master silence alarm timer to make sure it is ticking, restart it if necessary, and log any restarts of the timer. Also added a System stack event qualifier that can be used to monitor the master silence alarm timer for testing and debugging purposes.

6. Added stack event qualifiers and actions for Iport Mk II. The requires IPort version 1.8.0alpha13 or later

1. IPort Qualifiers

1. Encoder/Decoder number

2. Main Output A

3. Main Output B

4. Additional Output A1

5. Additional Output B1

6. Additional Output A2

7. Additional Output B2

8. Additional Output A3

9. Additional Output B3

10. Additional Output A4

11. Additional Output B4

12. Encoder Enabled

13. Decoder Enabled

2. Iport Actions

1. Encoder/Decoder number

2. Main Output A

3. Main Output B

4. Additional Output A1

5. Additional Output B1

6. Additional Output A2

7. Additional Output B2

8. Additional Output A3

9. Additional Output B3

10. Additional Output A4

11. Additional Output B4

12. Encoder Enabled

13. Decoder Enabled

7. Added Iport mpeg routing abilities to the mpeg router to handle the backup streams and unicast routing as well. The requires IPort version 1.8.0alpha13 or later.

1. ToDo: Need more details here as the documentation for Iport changes are introduced.

8. Modified the PointsWatched code to use a lookup table that greatly reduces CPU load when looking up stack events involved in Gpio, Audio, and routing.

9. Increased the buffer size on Probel protocol translator to allow a larger simultaneous block of commands.

10. Changed the default VMIX size from 8 to 16

11. Fixed a bug where large GPIO devices such as the iport with 128 virtual gpios was not getting all of them discovered because the discovery process was moving on after the first few received.

12. Added the following Probel Switching commands to the probel protocol translator

1. Command 7 which responds with Command 8

1. (Status) Currently outputting a single byte 0 in the message block indicating no faulty blocks/modules.

2. Command 43 which responds with Command 44

1. (IO parameters interrogate) Currently outputting all requested IOs as normal stereo

3. Command 65 responding with command 67.

1. extended interrogate

4. Command 66 and 69 responding with 68 and 70

1. Extended Connect and Extended Connect On Go

5. This change sends out route change messages with command 4 or command 68 depending on whether the change is using SRC/DST below 1024 or above.

13. Added a pending cache to Probel translation to prevent double returns when route changes are made and to make sure the return is the correct type.

14. Made some changes to Panel Designer to begin allowing it to interact with Pathfinder Core Pro including a connection menu and a file that remembers the last connection target. Also added a state label for showing the connection state when PanelDesigner is connected to a Pathfinder Core Pro.

15. Fixed a bug where Iport was not showing up in the available list of targets for VMIX changes in stack events.

16. Added VMIX logging

17. Fixed a bug in PathfinderClient where when typing in the IOs in the destination drop down, it would sometimes not select the ID number and therefore would still be pointing at the incorrect destination.

18. Fixed an issue in PathfinderClient where occasionally if the client launches in chart view, it might only display a single source and destination if the display code runs before the server sends down the route list.

19. Adding and removing equipment from the Axia Audio and Gpio routers will no longer cause all devices to be disconnected and reconnected. This version intelligently analyzes the list and only drops and/or adds connections as needed leaving the others intact.

20. When adding and/or removing equipment from the router, this version disables the client connection from accepting additional client connections while the router is being rebuilt to save CPU cycles. It is re-enabled as soon as the router regeneration is completed.

21. Fixed a bug that was causing the virtual route details not to display when the virtual route was other (multiple base points only one of which were connected)

22. Modified the virtual routers so that they can do Audio follow-me. Essentially you can now marry multiple base sources/destinations from the same router into the virtual package and all will get routed. So for example you could create a virtual source and destination that contains 8 audio points underneath and all would get routed with the single virtual route point change.

23. Made sure changes to any parameter that should be stored in the Server.inf file gets written out as soon as the change is made so that it is retained in the case of a power outage or crash. These include settings such as logging on/off, memory slot remembrance on/off, password mode, Axia SRC/DST additions state.

24. Added a way to force a system level lock off via the SAPV1 port 9500. YOu have to be logged in as an Administrative user to do this. If you add the word Force to the end of the setlock command, it will force the lock change even if it is a system level lock. This allows the clearing of an erroneous system level lock.

1. setlock 1 33 False Force

2. note: If the item should be system level locked, it will get relocked the next time the IO is polled and the device returns the system:locked parameter.

25. Pathfinder Client had a restriction that only the first 5 routes could be manipulated in demo mode. This has been remarked out. The 2 hour time limit on the server is an adequate demo restriction. Also upgraded the number of routers limit to 5 from 2 in Demo mode.

26. PanelDesigner now writes a version stamp into the hardwaremap.xml file.

27. Deleting a panel from the server window will now also delete corresponding entries for that panel from the hardwaremap.xml file.

28. Cluster Synchronization of HardwareMap appears to be working now. On an upgrade from a version that does not support cluster synchronization of hardwaremap files an old date (1/1/1950) will be applied to both files. So if they are not in sync already they will not be synchronized until a panel designer change is saved that updates the file. This is because we do not know which one is accurate. It is recommended to make sure your hardware map files are correct on both servers before upgrading to this version.

29. Fixing a few spots that were possibly causing deletions to get resynchronized during cluster synchronization.

30. Fixed a bug where individual user records could not get updated by the cluster synchronization because the database search was not enclosing the user's name in quotes when attempting to find the user to change.

31. Fixed a bug. Sending a single users table was broken in cluster synchronnization.

32. Fixed a bug that was preventing single new user record updates from syncrhonizing between cluster nodes. The users table should now be cluster synchronizing properly.

33. Panel Designer label controls now save out the On/Off state property. Previously that was not getting stored to the xml.

1. For backwards compatibility:

2. New label controls are by default set to On so that if they are hardware mapped to a DISP object the On state is sent.

3. Label controls that do not have the State property in the XML when they are opened in panel designer get the On value in the state, but the backcolorOff color is copied into BackcolorOn. This forces the control to look like it did. When it is resaved, the On State is saved. Then the properties are independent again.

34. This version introduces a loop inhibitor to stack events.

1. This function monitors the frequency of action execution. By default if the actions are executing more frequently than 10 times per 100ms, the event is considered to be misbehaving and the loop inhibitor will disable it. This is in an effort to save the CPU from going into an endless loop and causing 100% utilization.

2. If an event gets disabled by the loop inhibitor, a log message is generated and the event group that contains the disabled event is highlighted in red in the stack event group list in the server.

3. In the stack event editor, items that are normally disabled are given a pale red color and events that have been disabled by the loop inhibitor get a bright red color in the event list.

4. Also added an Advanced button in the stack event editor. This allows the Administrator to override the default settings and tune the max count and per millisecond values for the loop inhibitor for a specific event. This can be used for the rare case that an even is legitimately supposed to be executing more frequently than 10 times per 100 ms. This Advanced screen also shows if the event is currently loop inhibited.

5. In order to re-enabled an inhibited event, you must select the enabled checkbox. If the event has not actually been fixed, it may get inhibited again however.

6. This functionality will not necessarily stop all loops. A slow moving loop with time delays and/or calls out to the equipment may still exist, but typically those will not cause a CPU load.

35. Added IO hiding. IOs that have been discovered in Axia Audio and Gpio routers but are not necessary can now be hidden. Select the router in the server and click edit names. Using the scroll bar, scroll to the right in either the sources of destinations list and you will find a checkbox for hiding the IOs. Commit the changes by clicking Done. Once the IOs are hidden they will not be displayed in the routing clients, stack event editors, or through the port 9500.

36. Added Silence and Clipping override per IO. You can now override the default silence and clipping values on an IO by IO basis. Select the router in the server and click edit names. Using the scroll bar, scroll to the right in either the sources of destinations list and you will find fields for changing the silence and clipping levels. Valid ranges are 0 to -100. If the field is blank then the default value as determined in preferences is used.

37. Fixed the VMIXState return command in SAPV1 port 9500 to remove the double decimal points that were being returned and also return values for gain, timeup, and timedown that match the engine web pages (/10).

38. Changed the Name field of the Timeout in Silence alarm field in the stack event editor so that it now says "Timeout (in seconds):" so the user knows they are entering seconds and not milliseconds.

39. Fixed a bug that affected the cluster synchronization of large databases. If there was a double space (two spaces) in a name in the data and that double space was late in a large database, the database synchronization would fail and potentially cause a memory leak and CPU load as the buffer grew and would be analyzed again and again.

40. Fixed a bug in SAMeterServ. If the RMS values are not present from the node as exhibited by XNode software 1.2.0l, metering woul dnot work. This has been fixed.

41. Probel Route change messages were being added to the probel outbound stack 2x because. That has been fixed.

42. Also increased the message buffer which is used to wait for corresponding ACKs from 100 to 5000. In the case when a large number of changes are being queued this could potentially have caused messages to have been lost.

43. Prior to this change route stats and gpio stat changes were sent to all translators. Now if the translator requires a login, they will only be sent out that translator if the user who is logged in has the rights to the router in question. This change could be breaking to outside apps if they do not use the login since route stats and gpio changes on the main SoftAuth port will only be displayed after a successful login. If this is an issue for your outside app turn off the login requirement on the main translator.

44. Virtual routers now immediately check all points whenever the router gets rewritten because IOs are added or removed. Prior to this change it could be several minutes until the route states were correct after the router was edited, because the states were being checked one at a time with a delay between each check. This causes minimally more CPU utilization when completing the editing of a virtual router.

45. Changed the font in the panel designer property grid to MSSanSerif to better support international character sets. Make sure you select a font for the controls that support your international charcters. For example, the default font used in buttons and labels is Arial which is not supporting Cryllic. By switching the controls to MSSanSerif, the correct characters may be displayed.

46. Reduced the metering poll rate requested by the clients from 150ms to 120ms.

47. Fixed a but in SAMeterServ that was causing very sluggish metering. SAMeterServ was holding messages for a period of time or until a buffer size was reached before sending them. As a result messages were coming to the client in blocks and only the 3rd or 4th metering message was being drawn to the screen. This has been fixed to make the meters much more responsive.

48. Fixed a bug. The option controls for protocol translation states and stack event enabling states were all in the same group and so were interfering with each other. That is why they would spontaneously unselect. Created a frame for each set of option controls to separate them and fix that bug.

49. Fixed a bug with Lwcp parsing that could cause system items to get piggybacked onto the end of the last property value.

50. Added a delay to Zip one messages after the login since commands right after the login will not work without a beat between the login and the first command.

51. Added some additional error message checks for failed login attempts to the login scan tester in the Livewire wizard.

52. LWCP connections now send a login which matches the LWRP login immediately after connection. This should allow the changing of passwords on LWCP enabled equipment. Prior to this change Pathfinder's ability to use LWCP resources relied on maintaining the blank password. It is important to note:

1. If the device appears in both audio and Gpio routers, the device needs to have its Password updated in both routers or LWCP connections may not send the correct password.

2. ZipOne currently accepts a blank password on LWRP even if there is a password that has been set for the device. This means the Lwrp login test may pass but Lwcp will not work. The password should match the web page one password in order to use the ZipOne stack event capabilities.

53. Fixed an issue where if you made changes in the Edit Names data grid that wer written to the database and then clicked the X rather than Done, the internal RAM data structures would not get updated.

Version 4.75 (Server) 09/07/2012

1. Changed the parsing of SAProtocol commands. It now determines whether a command is complete based on the carriage return and throws line feeds out during command parsing. In some cases if the TCP packets were splitting the carriage return and line feed between packets, this protocol translator was leaving the line feed intact as the first byte of the next command invalidating the command or it was leaving the carriage return as part of the data of the preceding command rather than removing both as the command splitter. This has been fixed. This was discovered when certain automation systems were sending login commands to an SAProtocol translator. When the carriage return and line feed got split between TCP packets, the carriage return was getting left as part of the password bytes causing a login failure.

Version 4.74 (Server, Client, Mini, PanelDesigner, RepairAndCompactTool) 09/02/2012

1. Made a few changes to clients in preparation for PFCore support.

2. Fixed a bug where stack even route actions which had the override locks option turned on but the lock option turned off would not unlock the route.

3. This version now issues the Save command to livewire windows drivers when making route and gpio changes so that the driver will save the state between restarts. This is not necessary in the hardware equipment as the equipment handles this internally to better save the flash cards.

4. Changed the Livewire router creation/editing wizard, virtual router creation/editing methods, and PFSRemote methods to make safety copies of the databases. When editing an existing router, this version will now make a copy of the router database, make the changes to that copy, and then only if the changes are successful will it recopy the temporary database over the original. This is a safer way to update the database to prevent any problems or possible corruption.

5. Added a repair and compact tool. In rare cases we have seen router database corruption which presents itself to the end user when they try to add equipment and then get an error message and a blank database. The item above should prevent this from happening, but it will also leave the database in an unaltered state without the new equipment. This issue here is a rare corruption that can happen to Microsoft Access databases which prevents the system from deleting and creating tables in the database among other things. The tool (RepairAndCompactTool) which is now included in this version of the server will allow the user to repair and compact such a database which should then allow them to add the equipment in again. This situation is rare and ununsual but critical enough we felt the tool was necessary. This tool will also make a copy of the database before attempting the repair and compact and will only overwrite the original if the repair is successful on the copy. It will also make backups of both the original and cleaned database to the backups folder. Where possible, it is best practice to run this tool with PathfinderServer shut down. Though for the router databases it is usually possible to run the tool while Pathfinder is still running. The tool will inform you if the database is locked by Pathfinder and therefore cannot be repaired. If you do not want to upgrade Pathfinder, this tool can also be used on an older version of Pathfinder by downloading the repair and compact zip file and unzipping the three files into the PathfinderServer folder. RepairAndCompactTool.zip. See the following document for more details: RepairAndCompact.pdf.

Version 4.70 (Server) 11/04/2011

1. BTools emulation was not supporting GPI pulse stretching so that the GPI presented to the automation system was at least a certain length no matter how long the Axia GPI was. This is available for each emulated GPI device through the advanced menu.

Version 4.69 (Server) 10/31/2011

1. Optimized panel control property access to improve performance with large numbers of panel controls. Since a key is now used it is critical that panel.button name combinations be unique.

2. Added a dummy response in BTools emulation so that it responds to a request for silence alarm data. This is currently fake data that always shows audio present but some automation systems (such as NextGen) needed a response to be made to this request for data. Implementing this fully will require additional UI components to allow the user to define what IOs in Axia to monitor for the silence status.

3. Fixed a bug in BTools emulation where the *uSPA command was not getting recognized as a complete command and was therefore being processed when the next command came in rather than when this command comes in.

4. Realized that actual BTools boxes only dynamically alert the controlling system of changes that take place if the id of the BTools device is 0. Any devices with an ID above 0 must be polled for state changes. This version makes our emulator behave in the same manner. This was critical to make NextGen work with our emulator as the NextGen system will only allow its configuration to be set for ID 1 or higher and relies on only receiving responses to messages it has requested specifically.

Version 4.66 to 4.68 (Server)

1. Internal release only

Version 4.65 Beta (Server) 9/12/2011

1. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Fixed a bug where stack events could not run PFS scripts which required arguments.

Version 4.64 Beta (Server) 9/6/2011

1. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Metering service will now start automatically when PathfinderServer starts if it is not started already.

4. Finished getting initial version of Ross Overdrive protocol translator integration working to the Ross test simulator.

5. Fixed an issue since 4.62 where since the metering service moved updates on changes to fader on/off and fader value were slow to update in the meter fader controls in mini and client.

6. Added a command line option called -sw=ipaddress (eg. -sw=10.10.10.33) which when used adds some additional timing logging surrounding the ingest of data from an Axia audio device for debugging any delays in ingesting the data.

Version 4.63 Beta (Server) 8/28/2011

1. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

2. See notes for 4.62. This version requires at least 4.62 of the clients and mini for metering to work. Since 4.62 metering now runs from a separate service which is installed along with PathfinderServer. Be sure to start the service after installing PathfinderServer by using the service start button on the panels tab. The service will start automatically if the computer is rebooted. See notes from 4.62 on this.

3. Started support for a Ross Overdrive protocol translator for controlling Element consoles using Ross overdrive. This module is not tested or complete yet.

4. Added an option in the code for protocol translators that want the speed of commands limited which uses a buffer in those cases. Currently only enabled for Ross Overdrive.

5. Fixed a bug where the warning message about creating a second Axia Audio or GPIO router appeared when editing the router.

6. Fixed a bug in the livewire scanning when creating an audio or GPIO router where if there was a quoted parameter at the end of a line and the quote was unterminated it would not add the device. This should never happen, but certain manual mistyped data commands can create this scenario.

7. Changed the reconnect algorythm so that it is not driven off of the data message poll timer if it can’t connect. Instead it will wait for the connect attempt to time out before trying to reconnect instead of recycling the connection early. This change may reduce CPU load during reconnect cycles on failed and/or missing equipment.

8. Added Preview on/off as an available option to change and monitor in Livewire console stack events. This functionality requires powerstation version 1.13a or Element version 2.5.0.5 or later. Both of these software revisions for Powerstation and Element are still in beta and not released yet.

9. Made the metering service restart after editing the audio router to add or remove devices to force it to pick up new ios. May find a better way of doing this later.

Version 4.62 Beta (Server, Client, Mini, PanelDesigner) 6/20/2011

1. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

2. The PathfinderServer installer now installs a new service for handling metering. All metering for panels and clients now funnel through that service so that the PathfinderServer application itself does not need to handle that workload. The service is called SAMeterServ. When installed, the SAMeterServ service is set to start automatically on bootup. However, if you do not reboot your computer after installing PathfinderServer, you will need to start this service before metering will work. This can be done from the Panel tab in PathfinderServer where we have added a new button to start, stop, and monitor the state of this service.

3. All of the metering controls have been reworked to make the graphics less CPU intensive. This greatly reduces the CPU load for larger meter panels.

4. Added a command to SAProtocol called GetBufferSizes. It is aliased as "gbs" as well for easier typing. This will return the internal buffer size of all connections in PathfinderServer. This is useful in debugging if it is suspected that a buffer is growing larger than it should.

5. Added a warning message in the server if the user is attempting to create multiple Axia Audio or Axia GPIO routers since this is not recommended except in rare multi-site installations.

Version 4.60 Release (Server, Client, Mini, PanelDesigner, SAPortRouter) 5/13/2011

1. WARNING: See Notes about version 4.36 and 4.37 and the notes in 4.37 about the new installer package. If you are upgrading from a version prior to 4.36, you must upgrade all applications as the communications protocol changed between the client applications and server with version 4.36. As always we recommend making a backup of your PathfinderServer folder before upgrading.

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Release version 4.60 including iso image.

Version 4.57 Release Candidate 13 (Server, Client, Mini, PanelDesigner, SAPortRouter) 3/14/2011

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. This version adds an option in the Master Socket settings under the File menu to add a delay to opening the client socket after the event system starts. Some customers with very large stack event systems need a little extra time for the system to fully synchronize. In existing versions the client connection was open and allowing clients to connect during this synchronization period. This delay allows the administrator to delay the opening of the port for client and mini connections for a period of time after the event engine starts to allow this synchronization time to complete fully.

4. In panel designer, modified the folder browsing window which is selected when tyring to pick default graphics paths so that share names can be typed and network shares more easily entered.

5. Updated the SAPortRouter application to store its configuration files in the windows environment common application folder under SAPortRouter in that folder. Normally this is a hidden folder called C:\ProgramData\SAPortRouter. This allows the service to start and run properly on Win7 since this directory is writable by a service. For upgrading customers the software should automatically copy existing configuration files from the program files directory to this folder. As always a good backup is recommended before upgrading.

6. Generated a test .iso image of all applications in preparation for full release.

Version 4.56 Release Candidate 12 (Server) 2/14/2011

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Revised the help document which is embedded in the programs.

4. modified the size of the hidden root MeterFaderControl that instantiates the array from a small size to a normal size. For some reason having this be small was causing crashes when closing the panel sometimes and may have been causing loading problems as well. This may be a scale issue with t he fonts in the control but we have not tried to look into that yet.

5. If you hardware mapped a button to a GPIO, the on/off state of the GPIO was based on both the On/Off state of the control as well as trying to interpret color states. The code that was making it map to backcolor states has been removed so that this is only based on on/off.

6. Added Help Menu to Panel Designer.

7. Added an option called fileloads to the subscribe command in SAProtocol which will spit out a message whenever files are loaded. This is useful in debugging.

8. Cleaned up some panel loading issues. All panel files were being loaded each time a PathfinderClient was started in order to get the friendly names of the panels to display in the menu. The friendly names are now cached to reduce this.

9. Panel data was getting loaded from the file more than once when a panel was opened. Two functions were both causing a read of the file. This has been cleaned up so that it only reads the data from the file once.

10. French Boolean values were sometimes getting returned in the program as the French words for True and False causing parsing problems – especially with the meterfader controls. This has been fixed.

11. Fixed a bug in the GPIO display where certain values soemtimes caused the metering columns to appear instead of the correct pins to display. This has been fixed.

12. Fixed an Decimal parsing bug when Stacking Event Editor was run on a foreign client.

13. Implemented a subscribe IOStateChanges command to SAProtocol which will spit out messages when IO availability, name, or description changes dynamically while a router is running. It will not spit them out during a full router refresh. Return commands are formatted like:

1. SourceStateChange <RouterNumber> <IONumber> <Availablility><Tab><Name><Tab>Description

2. DestStateChange <RouterNumber> <IONumber> <Availablility><Tab><Name><Tab>Description

3. Example:

1. SourceStateChange 1 25 0 PC 24a PC 24a ON satestserver

14. When a full router definition changes there will now be a command on SAProtocol called RouterDefinitionChanged. Command sent by PFS is formatted like

1. RouterDefinitionChanged <RouterNumber>

2. Example:

1. RouterDefinitionChanged 1

Version 4.55 Release Candidate 11 (Server) 12/20/2010

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Fixed a bug with the Any source in stack event route actions. To reproduce the problem, create a stack event where the qualifier is a route with a set destination and a source of any. Create an Action which sets that destination to a specific source. This should cause the route to be forced back if anybody changes it. This worked with Engine resources which do not report anything back if a route change is set to what it already was (no change). A node however spits back the route command even if we are setting it to what it already was. If there was a route request pending (even if it was to the same thing again) a review of stack events was forced. This would cause a CPU spiking loop where the route request would be sent over and over again. This has been fixed.

4. Added a command to SAProtocol called version which will return the version number and license version of the server.

5. Fixed a display issue with the Axia IPort router where the scan list when creatnig the router would display all axia audio devices rather than just those with IportMpeg resources. It was a benign bug in that those other devices would not get added into the router at the last step, but it was disconcerting to the user. This is now fixed.

6. Fixed a bug where if Axia Automatic Src/Dst was turned on, the non mpeg vmix resources would get added into an Axia IPort router. This is fixed.

Version 4.54 Release Candidate 10 (Server, Client, Mini, PanelDesigner) 12/10/2010

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Fixed a bug where the login testing was indicating the login test had been passed with blank passwords whether or not the unit accepted a blank password. Therefore the login test in the wizard would pass but the software would announce a login error when it actually tried to use the equipment. This is now fixed so that the testing procedure will fail for a unit if the login is rejected in all cases.

4. Fixed a bug where if you edit a router and change a login, that change was not sent into the actual existing device object without a restart of Pathfinder. This is fixed. This should fix the Omnia login issues.

5. Version 2.4 of the OmniaOne software also adds GPIOs. But the GPIOs have blank names. Pathfinder will now add GPIOs that have blank names by assigning a name to the IO in the database. If the device is identified as an Omnia it will assign a name of OmniaGPIOx - where x is the GPIO number. Any others are assigned a name of NoNamex.

6. Fixed a bug where some of the processing of KEY=UP and KEY=DOWN for LCD button panels were not forcing case insensitive analysis as they should be. The latest version of software for the Ethernet LCD button panels which has not been released yet has some case changes in the commands so that case insensitive analysis is required for it to work properly.

7. In SAProtocol in the verbose mode, if there is no source verbose information we were returning a blank field. This was causing parsing problems for some automation systems, so this field now returns a zero if there is no data in the field.

8. In SAProtocol, a RouteStat command was not being sent if a channel number changed on a GPIO port. This is not actually a route change in the router, but in verbose mode the source verbose field carries this channel number so we needed to send the command when this change takes place.

9. In SAProtocol, the RouteStat command in verbose mode was sometimes missing a tab delineation. This has been fixed.

10. Fixed an issue in Server, client, mini, panel designer, and the meterfader control used in these applications where the fader values would not display or send correct values if the system was set for certain nationalities such as French. This has to do with the use of a comma rather than a decimal on these systems which has to be interpreted and translated properly.

11. Fixed an issue where panel buttons that are hardware mapped and use a source/destination route map rather than a stack event may not show the correct color state when Pathfinder first starts up until the button is toggled. This has been fixed.

12. It is possible in this version to map multiple hardware controls to the same software control. There is no user interface for doing this. It has to be manually set up in the hardwaremap.xml file so is only for support staff or advanced users that are knowledgeable on this file and how it works.

13. In SAProtocol, fixed an issue with the read write state indicator in the SourceGPIORW field in the verbose mode version of the routestat command. This column was actually displaying the read write capabilities of the destination instead of the source. This is fixed.

14. In SAProtocol, ASI cards were not displaying the correct read write state or online state of GPIs in the verbose version of the RouteStat command. It was sometimes showing NotEstablished in the SourceVerbose column rather than 0 for no route but established. This has been fixed.

15. In the stack event editor when closing the StackingEventList, the editor will now select the last touched StackingEvent on the StackingEventGroupList instead of the first StackingEvent.

16. Fixed a bug in the stack event editor where when a Stacking Event was edited, it would always indicate changes would be made.

17. Fixed a bug in the stack event editor where StartTime and EndTime Details of a TimeRange Factor were not being read correctly when the value was from the old editor.

Version 4.53 Release Candidate 9 (Server) 11/10/2010

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Fixed a bug created in version 4.51 which caused high CPU load on the secondary server during synchronization. This was due to an error in the new ability to adjust the Name property of a control which was causing repeated reloading of the panel files during the synchronization process.

4. The GetListVersion timestamp for SourceNames and DestNames lists was not getting updated when a name in the router changed. This has been fixed.

Version 4.52 Release Candidate 8 (Server, Client, StackEventEditor) 11/4/2010

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Fixed a bug in the server that was not allowing the client to be updated on GPIO route changes immediately. This bug only existed in version 4.51 due to the GPIO optimizations. It is fixed in this version

4. Improved performance in the client for devices with large numbers of IOs when the entire device goes online or offline. The function which switched those IOS to red or black in the lists was not as fast as it could have been causing CPU load int he client during those transitions so that has been optimized. This was not a user reported problem but was something we found in the lab when doing scalability testing.

5. Fixed a bug in the stack event editor where StartTime and EndTime Details of a TimeRange Factor were sometimes not being read correctly when the value was from the old editor.

6. Protocol translator escape characters for carriage return and line feed \cr\lf were case insensitive on qualifier but had to be uppercase on action. That is fixed.

7. Fixed a big in Silence alarm stack events where silence alarms longer than 32 seconds might not fire. This has probably been present since 4.43.

Version 4.51 Release Candidate 7 (Server, Client, Mini, PanelDesigner, StackEventEditor) 10/26/2010

2. This version requires the .net framework (3.5 SP1) to be installed on the server if it is not already.

3. Optimized GPIO Router IO access on very large routers for better performance.

4. Fixed a bug in the stack event editor where if the user tried to cut a stack event factor when none was selected the editor would crash.

5. Fixed a bug where cutting a stack event factor would cause the user to be prompted.

6. In the Client, the first row of a router would no show the destination description in the description field. This has been fixed.

7. In international versions of windows where commas are used instead of decimals for numbers, the VMIX gain, time up , and time down was not working properly. This should be fixed.

8. Made the MeterFader update its gain control faster after the VMIX fader gain had changed.

9. Fixed a hexidecimal conversion problem where Axia Audio routers with a router ID greater than 10 were not working properly with metering display.

10. Fixed an issue where stack events that were using VMIX submixers above 8 (submixers 9 through 16), were not getting polled for their initial state and therefore the stack event would not function until the state was toggled. Also reduced the poll rate so that the initial state can get acquired faster now that there can be 16 submixers worth of VMIXers to query.

11. User Panels have the ability to change the name of a button on the fly as a stack event action. This should be avoided at all costs unless there is no other way to make the panel do what you need it to do as you are actually altering the unique identifier for the button so this must be carefully monitored and kept track of. However, this functionality was broken prior to this version. It has been fixed but should still be avoided unless absolutely necessary.

12. In the stack event editor when opening the arrow list (used to be ellipsis), the list will now highlight the currently selected item.

13. Fixed an issue where meters and some other controls might not reinitialize on panels in the client and mini after the client/mini lost and regained connection with a server without shutting down and reopening the client/mini application. This should be fixed.

14. Fixed a bug where the server was not handing out all of the cluster client addresses for clients to connect to when a redirect to the other server in a cluster was taking place. It was only passing the first one.

15. Fixed a few login issues related to redirection in load balancing cluster situations in the client and mini if login is required.

16. Added a function which attempts to order the redirect list of server IPs according to the subnet of the requesting client for a faster reconnect after redirect.

17. Fixed a bug in the stack event editor - Moving a Factor via Drag and Drop did not remove it from the source.

18. Fixed a bug - when the flash to a button in panels is turned off, the color is left in the last state (on or off) as opposed to the actual On/Off state of the button. This has been fixed.

19. Added an option to the port 9500 Subscribe Silence command to allow an IP address (subscribe silence 172.16.1.254). This allows you to only see all silence messages related to a specific IP address if any of the IOs for that IP address have silence alarms associated with them.

20. In the stacking event editor, added a Feature: When a Stacking Event Group XML file fails to be ingested, it now presents a more verbose explanation of the problem.

Version 4.50 Release Candidate 6 (Server) 9/19/2010

2. This version requires the .net framework (3.5) to be installed on the server if it is not already.

3. Remove button for Panels in the server was not working correctly at all times. This has been fixed.

4. Fixed the ability in the Stack Event editor to program functions in the Router field of Actions in the Router, GPI, And GPO Actions.

5. Some versions of Engine and PowerStation software did not have a space between the VMIX and the sub number in the DST command for VMIX Name ("VMIX1 in 1" instead of "VMIX 1 in 1"). This meant that the MeterFader did not understand the point was a VMIX channel. This will be fixed in the engine code, but since that version of software is in the field, we also now check for this on Ingest and add the space back in so that PFS logic works.

6. Icons complete in stack event editor.

Version 4.49 Release Candidate 5 (Server) 9/2/2010

2. This version requires the .net framework (3.5) to be installed on the server if it is not already.

3. Fixed an issue with the Protocol Translator stack event qualifier and the new stack event editor. The command may not get ingested when entered with the new editor. This has been fixed.

4. Fixed an issue with the VMIX Time Up/Down/Gain values when entered with the new stack event editor. There was a chance that they could be ingested into Pathfinder incorrectly.

5. Added support for 16 VMIX Busses in the stack events VMIX qualifiers and actions. The events will only function if a source or destination from the VMIXers above 8 being used exist in the router. PFS uses the database and messages from the Engine to determine if support for VMIXers higher than 8 should be enabled and which ones should be enabled. This is so that status updates are not sent to older software versions for VMIXers that do not exist in that software revision.

Version 4.48 Release Candidate 4 (Server, Client, Mini, Panel Designer, VMIXControl 1-06) 8/25/2010

2. This version requires the .net framework (3.5) to be installed on the server if it is not already.

3. Fixed an issue where the Power Station was not showing up as an available option in the Probel Protocol Translator.

4. This version has the revised version of the new stack event editor with new icons and reduced number of window changes.

5. Removed a blank line in the GetList StackEventChildren SA Protocol command. Also fixed the name and description for getlist secf 26 ID 2.

6. Silence alarm polling now active for Engines/IPort/Omnia8x. This is just the sanity check function to make sure silence alarms are in sync.

7. Removed the a and c memory slot alias from the getmemoryslot SAProtocol command. A or C could be valid memory slot names.

8. Removed silence alarms now clean up resources that were earlier left in use.

9. Added the ShowStackKeys command to SAProtocol. This allows us to see the key collections used for quick access to monitored stack event qualifiers. Used for debugging purposes only. Arguments include: Memory, Profile, User, Audio, AudioWatched, GPIO, GPIOWatched, Routing, Time, UserPanel, VMIX,EventSysStart ,ConsoleLWCH, ConsoleFACH, DeviceFail ,AESSyncLoss, LWMuteOnAES, LWStreamFail

10. Staggered the audio silence subscription poll if there were more than 4 IOs subscribed to on the same device they will get polled in groups of 4 each time through the poll. This is only for the sanity check poll that makes sure nothing has been missed.

11. Added TextOrAny as a field type in stackeventchildren in SAProtocol. Applied it to the Memory value to make the stack event editor display the Any checkbox for a memory slot value.

12. Added a log message type to log messages being sent and received on protocol translator ports.

13. Fixed a bug where the verbose mode was not always returning verbose data on RouteStats. Fixed for WO.

14. Fixed an issue where an IO added with the Automatic SRC/DST add menu item on Primary would get inserted in the database on secondary, but would not become available for use on clients connected to the secondary without a restart of the secondary. This has been fixed.

15. Made the Source and Destination and router Getlist versions follow clustering version stamps so that those version fields are matched across a cluster.

16. Added code to prevent blank panel files during cluster synchronization if the panel no longer exists on the servers due to a manual file removal.

17. Rewrote the Panel Clock component to use buffered graphics to reduce flickering when background pictures are used. Also added an option (true by default) for Element style hand graphics.

18. Added the quit and exit commands to SAProtocol which also shut down the TCP connection to SAProtocol

19. In SAProtocol in SEChildFiled 20 - changed the field name for item 2 from "Livewire Channel Number" to "Livewire Channel" to make it look better in the stack event editor.

20. In SAProtocol when verbose mode is on, added two columns to the RouteStat commands if the router in question is a GPIO router and verbose mode is on. These additional columns display the Read and Write ability of the GPI and GPO on the source and destination ports involved in the route. Details listed below:

1. ‘Legend for the additional GPIO columns

2. 'For GPIOs verbose Routestats only – Letter preceding the I or O in the 4 letter group defines whether the I or O is Read, Write, Both, Neither

1. 'XIXO X=Not a GPIO Port

2. 'NINO N=Neither Read or Write or available

3. 'BIBO B=Both Read and Write are available

4. 'RIRO R=Read only is available

5. 'WIWO W=Write is available 'You will never see this because if write is available so is read

3. 'Actually currently used

1. 'RIBO Read on GPI only and Both Read and Write on GPO - standard GPIO port

2. 'BIBO Both Read and write on both GPI and GPO - this is a software port

3. 'NINO Neither Read or write on GPI or GPO - this is assigned to source points that are 0 - 'so where no route is routed to the destination, the source column will say NINO

21. Added a command line option in the shell command in Pathfinder which launches the new stack event editor which specifies the Backup folder the editor should use. This is necessary for International windows to make sure the backup path is correct.

22. Modified the Metering poll in VMIXControl to only poll the six channels that are visible rather than a blanket Meter call. Used to reduce the load on the Engine when multiple VMIX control applications are using the same engine.

Version 4.45 Release Candidate 1 (Server) 7/12/2010

2. This version requires the .net framework (3.5) to be installed on the server if it is not already.

3. Fixed an issue in the new stack event editor where the internal version number in the stack event files was not being updated after every edit. This would cause the changes not to get synchronized via clustering after editing an event with the new stack event editor.

4. Added the Pathfinder Servers themselves as options in the DeviceFailure Stack Event qualifier. When clustered, the servers can now monitor each other and trip event actions if either of the servers in the cluster fail.

5. Stack Events are now added properly into the cluster synchronization table when created/edited with the new stack event editor.

6. Panels have now been added into the cluster synchronization. Panel changes will now be synchronized between the clustered servers. It is recommended that you backup your panel files before upgrading to this version.

7. The stack event editor buttons are now completely disabled if the server is the secondary in the cluster until/unless it takes over.

8. The stack event grid in the server will now list the events on the secondary even if it is running in standby so the user can see the events that are on the server.

9. When manually shutting down the Pathfinder application on the primary server in a cluster, it will now send a message to the secondary as it is shutting down so that the secondary knows it is closing and will take over immediately instead of waiting to try and reestablish a connection. There will still be a wait of up to 30 seconds in the case of a catastrophic failure such as a power loss on one of the servers. In that case the secondary tries to reconnect to make sure it is an actual outage rather than just a network hickup before taking over the event engine. But if the shutdown is planned and therefore manual such as during system updates, messages will be sent so that the secondary takes over immediately.

10. When the Primary server comes back online while the secondary is already online and in control of the event system, the event system will remain running on the secondary until all synchronization is complete and the primary signals it is ready to take over. The primary then sends a message and the secondary kicks into standby. Previously the secondary would put its system into standby before the primary was ready to take over leading to a brief event system outage. Items 9 and 10 reduce outage time during planned system maintenance.

11. This version will not execute data file synchronization between the primary and the secondary if the software versions are mismatched. It will synchronize real time data such as memory slots, but not file data. This allows mismatched versions of software to synchronize real time data temporarily during an upgrade process reducing down time without causing problems with changes in the file design between software versions. Both servers will need to be upgraded to this version before this function will work properly, but from there on out this will be the case going forward. This means after all servers are to 4.45 or later, during a system upgrade, users may allow mismatched software to synchronize minimizing event system downtime during a system software upgrade.

12. Fixed a bug with the LWRP attribute in the ver command on non-english systems for support of the new AES functions in the nodes. The former did not seem to work on French versions of windows.

Version 4.44 Beta (Server) 6/16/2010

2. This version requires the .net framework (3.5) to be installed on the server if it is not already.

3. Added “GetList AxiaDevices HasAES” to the getlist functionality in SAProtocol. This returns AxiaDevices in the routers which have AES ports.

4. Added “GetList SourceDetailsStat” and “GetList DestinationDetailsStat” to the GetList functionality in SAProtocol. This returns a source or destination list of sources or destinations which support the STAT LWRP functionality. STAT on the source side provides access to alarms on AES clock loss. STAT on the destination side provides access to Livewire stream loss alarms. This only works with node software 2.6.12a or later and driver software 2.5.2.7 or later.

5. Added the AESSync qualifier in stack events. This allows an alarm to be tripped on the loss of AES sync on an AES input. This only works with node software 2.6.12a or later and driver software 2.5.2.7 or later.

6. Added the LWStreamLoss qualifier in stack events. This allows an alarm to be tripped on the loss of the Livewire Stream. This only works with node software 2.6.12a or later and driver software 2.5.2.7 or later.

7. Added the AESMuteOnLivewireStreamLoss qualifier and action. This action changes this property in AES nodes. The qualifier gets tripped if this property changes in an AES node. This property in the node if enabled will mute the livewire stream on an AES input if AES clock disappears.

8. The qualifiers and actions listed here are currently only accessible through the new stack event editor. The legacy editor (accessed by shift-clicking the Add/Edit buttons) will not support these new qualifiers and actions at this point in time.

9. The icons in the new editor for these new qualifiers and actions have not been created yet.

10. Most of the changes in this version can only be used with new alpha software for the audio nodes and driver.

11. Polling of LVL (silence alarm polling to double check accuracy) and enabling of the STAT (AES and Livewire stream alarms) commands are enabled if the node/driver software reports LWRP version 1.2 in the VER command.

Version 4.43 Beta (Server) 6/12/2010

2. This version requires the .net framework (3.5) to be installed on the server if it is not already.

3. This version introduces a new stack event editor. The editor includes copy, paste, and drag and drop icons. Qualifiers and actions may be added with the + buttons or by opening the palette and dragging and dropping qualifiers and actions from the palette. Copy and paste can be accomplished using the standard Ctrl-C, X, and V keys, right clicking, or simply dragging an existing qualifier, action, or event. Events, qualifiers, and actions can be edited by double clicking the item. More details, tips, and tricks about the new editor will be released in the next version of the Pathfinder manual which is currently in production.

4. The legacy stack event editor still exists in the system by holding the shift key when you click the Add Stack Event or Edit Stack Event button in the server.

5. Added the ability to copy an entire stack event group from within the server application. When you copy an event, a new one gets created with the new name. The newly created copy of the event will be created in a disabled state so that duplicate qualifiers and actions are not loaded into the system before the user has a chance to modify the parameters.

6. This version adds the Syntax Getlist command to the Software Authority Protocol for use with the new editor.

7. This version adds some new GetLists to the Software authority protocol for use with the new editor including SourceDetails, DestinationDetails, StackEventChildren, StackEventChildFields, ConsoleFaders, and ConsoleFaderSourceList.

8. Fixed an issue in the BTools Protocol Translator configuration wizard where it would sometimes show sates from a previous configuration during editing.

9. Changed the BTools Protocol translator so that GPO changes are not automatically reported back to the controlling system. GPIs still are. This is more consistent with how the BTools devices themselves actually work. This was causing problems with some automation systems such as Wide Orbit.

10. Fixed an issue with functions. Nested functions such as funct:blah(funct:blah(1,1),2) were working but subsequent functions like funct:blah(a,b) funct:blah(c,d) were not. This has been fixed.

11. Fixed an issue with multiple functions as multiple arguments of another function such as funct:StartsWith(funct:MemorySlotValue(Routeur),funct:MemorySlotValue(Routeur)). The first memory value would get converted and the second one would not. This has been fixed.

12. Fixed an issue with hardware LCD button stack events where the event was not cross checking properly in all cases to determine if the event was looking for an up or down state. This was leading to some strange anomalies like the button sometimes being considered down at startup.

13. Fixed an issue with rackmount panel LCD button stack events. The response from the rackmount panel carries an extra space which was causing PFS state holding analysis to be incorrect. This caused problems when multiple qualifiers were in use in the event and one of the other qualifiers tripped the analysis. This has been fixed.

14. Fixed an issue where silence alarm subscriptions were not getting reinitialized after editing the main audio router to add or remove equipment. This could leave the silence alarm states permanently in the last known state until the server software was restarted. This has been fixed.

15. Fixed an issue where when a Fader style console control action was selected as opposed to livewire channel number style, it would sometimes send an invalid source profile change to the console when the source profile change was set to No Change causing the source profile to be cleared.

16. Fixed an issue in the Telos Livewire Router regarding Lock States in the RouteChange Function. The lock state would not be protected and could get cleared if a scene change asked to make the route that already exists. This has been fixed.

17. Fixed an issue with UDP based protocol translators. There was an issue with the component we were using for UPD transmission and reception which could cause a specific property to get reset after reception of data on the port. Even if the data was not being used in PFS, the reception of that data would cause the property to get cleared. The result was that the first command PFS sent over the UDP socket would work and subsequent ones might not. This was most reported by Enco users. We have implemented a fix for this problem in this version.

18. Fixed an issue with the BTools B command for making route changes in a switching rather than mixing configuration. Route changes would work as long as you were moving up through the destinations but moving back down would not work properly. Wide Orbit automation systems use this command. This has been fixed.

19. We now monitor the VER command for the presence of STAT. If it exists then we now occasionally poll the LVL states of subscribed sources and destinations. This offers a sanity check to make sure that we are in sync with the silence alarm states. This property and polling command ability only exists in node software 2.6.10a and later. We may need to modify this for the driver as the most recent driver software supports this polling but does not have the STAT command. Will research this for the next version.

20. If the STAT property is present we also occasionally poll the STAT command for sources and destinations. We have not finished the code to do anything with STAT commands or added them to the stack event system yet. That is targeted for the next version. STAT commands show loss/presence of AES clock and Livewire Stream on destinations. It is only available in the nodes in software versions 2.6.10a and later.

21. Also tightened up the clock used in stack event silence alarms so that it is more accurate and does not drift by a few seconds relative to the requested timeout. It is now within 500ms of the requested time relative to the reported outage by the device. Some devices report silence faster than others so there still may be a larger difference but this should be tighter.

22. Added the “Subscribe Memory” and “Unsubscribe Memory” command to SAProtocol. This will subscribe to memory slot changes on the port 9500. When used, memory slots will report their changes to port 9500 allowing for easier testing and debugging of stack events.

23. Added the “Subscribe Silence All” and “Subscribe Silence Changes” and “Unsubscribe Silence” commands to SAProtocol. This will subscribe to silence alarms and report them on port 9500. This will only report silence alarms for sources and destinations that are used in an audio level standard event, used in a silence stack event, or are currently visible in a Pathfinder client routing window. The “All” argument will report all silence messages from the equipment including polled states for nodes and drivers that support the LVL poll command. The “Changes” argument will only report when the state changes from audio present to silence or back or clipping or back. The “Changes” argument will not report the poll state if the underlying state has not changed. This is useful for testing and debugging or third party silence alarm monitoring.

24. Fixed an issue with ConsoleControl PGM4 qualifier that was not making it trigger correctly.

25. If a hardware user button panel is not in a software panel and is only referenced in actions and not in qualifiers, PFS would not connect to the device ip and therefore the action commands would not get sent. This has been fixed

26. Added the ability for Pathfinder qualifiers to use the State of a hardware button (On/Off) as part of the quaifier. It is important to understand the nuances of this addition. The rackmount LCD and Element LCD button panels do not report On/Off state in any form. This means PFS is caching what was last sent in order to make this qualifier work. This means on startup until PFS actually sends an on or off to the button, it assumes the button is off since it cannot check the actual state. Once a state change has been sent, then this qualifier will be accurate. Since most of the time the buttons are being set based on the state of something in the system by stack event that run on startup, this is ok. Manually changing the state of the button with a third party application or command will not cause PFS to know that state because the panel does not report it or allow it to be polled at this point in time.

27. Fixed an issue with hardware based panel buttons which might cause a hardware based panel button qualifier to get analyzed improperly if it is paired with other qualifiers in same situations.

28. Fixed an issue with using the TimeUp, TimeDown, or Gain as part of a VMIX qualifier. PFS was comparing text as opposed to the numeric value which caused some inconsistencies. This has been fixed.

29. Added a scan range menu item to the livewire router wizard which manually scans a range of ip addresses for addition into the router. This appears in the Utility menu of the Livewire Router creation wizard.

30. Changed the Event System start qualifier functionality. Previously it would only evaluate as True during the moment of event system startup. Now it evaluates True or False depending on whether the event system is running. This is useful for events with multiple qualifiers that depend on whether the event system is running.

31. GPO Channel number changes were not working in the qualifier section of GPO qualifiers. The changing of the GPO channel number can now be a part of a GPO qualifier.

Version 4.41 Beta (Server, Client, Mini) 4/3/2010

32. WARNING: See Notes about version 4.36 and 4.37 and the notes in 4.37 about the new installer package. If you are upgrading from a version prior to 4.36, you must upgrade all applications as the communications protocol changed between the client applications and server with version 4.36. As always we recommend making a backup of your PathfinderServer folder before upgrading.

33. Recompiled Client and Mini with 4.41 version number to keep it in sync with server.

34. Fixed a bug where it is possible with slower connections for the Login command to be sent to Axia devices before the TCP connection to the device is established. This has been fixed.

35. Fixed several issues with the Getlist commands to make sure they respond with the sent arguments included in the BeginList header and proper empty lists and error messages where appropriate.

36. Fixed a bug with Pathfinder talking to SAAudioPlay where if the SAAudioPlay service was restarted, PFS would not log in again at reconnect and therefore would not be able to play audio again until the server software was restarted.

37. Introduced a new timer in silence alarm stack events which greatly reduces CPU overhead when there are large numbers of stack event silence alarm timers.

38. Fixed a bug where after editing an Axia Audio Router, the connections to the devices were destroyed and recreated but the silence alarms were not subscribed to again without a restart of the server application.

39. Added additional pre-show getlists for NAB.

Version 4.40 Beta (Server) 3/23/2010

2. Fixed a bug where if a route to source 0 was requested from SAProtocol for a destination on an Engine, the route would not clear. This has been fixed.

Version 4.39 Beta (Server, Client) 3/22/2010

2. Added support for alternate port when routing GPIOs (172.16.1.23:4013/1).

3. Added support for LWRP to run on an alternate port. These can be manually added in the Livewire Router setup wizard witht he Add button by using IP and port (172.16.1.23:4013). Currently there is no support for multiple instances of LWRP running under different ports on the same IP address. That work is not complete yet.

4. Fixed a bug with function calls in the Route Stack Event editing window. Occasionally the source would show Previous rather than the function call. This hsould be fixed in this version.

5. In verbose mode on the SAProtocol, this version has an additional 4 columns in the GetList Routers command which show the Source and destimation lowest and highest ID number. Needed for WO integration work.

6. SAProtocol had a bug in the Routestat command that would return an invalid lock state if a single route point was being queried. This has been fixed.

7. There was a bug which was not allowing a virtual router to be created or edited from the client application. This has been fixed int he client application.

Version 4.38 Beta (Server) 3/12/2010

2. There were extra blank lines appearing in the panel list in Pathfinder Server Panel List. These have been removed.

3. Fixed a bug where console control stack events were not getting polled for their initial state during startup so that the control being watched would sometimes have to be toggled once before the stack event would work.

4. Fixed a bug where the Console Livewire Channel Mute qualifier was not working due to a changed response from some Element code versions.

Version 4.37 Beta (Server, Client, Mini, PanelDesigner) 3/04/2010

1. WARNING: See Notes about version 4.36. If you are upgrading from a version prior to 4.36, you must upgrade all applications as the communications protocol changed between the client applications and server with version 4.36. As always we recommend making a backup of your PathfinderServer folder before upgrading.

2. This version requires .net framework 2.0 or later to run for some of the components in the PanelDesigner, Client, and Mini.

3. The installer package has been completely reworked in order to support the hybrid technologies. If you have created shortcuts to the applications on your desktop or quick start bar, they may need to be recreated after upgrading to this version.

4. Added support to create an IPort Mpeg router which routes the mpeg stream side of IPort. This currently only works if the MPEG streams are set to multicast.

5. Added EV for AVC.

6. Fixed a bug with standard events that caused the None option for source to not work correctly in standard routing events and caused unending wait icons in the client user interface. Also added the None option to the server interface for standard routing events.

7. Added a command line switch to the server to log metering/silence alarm mismatches. This is for internal debugging only unless support asks the client to enable it as it adds load to the cpu. The switch is –lm.

8. Added the ability to enable and disable stack event groups and stack events.

9. Optimized code in the client and mini for metering displays. Also optimized the meter control itself. This resulted in large reductions in cpu utilization for large metering user panels. A side effect is that the meter control on the panel will no longer have a transparent line between the left and right meters.

10. Added the clock control to user panels. This control can display time with an analog or digital clock with and without a face and with and without a background image. There are quite a few properties which can be manipulated with this clock.

11. Added the ability in user panels to change the font in buttons and labels.

12. Fixed a bug in the console control stack event qualifiers that was causing them not to get evaluated properly in some cases. This bug had been introduced since we added the ability to change source profiles loaded to a fader.

13. Updated the syntax and GetList router type strings so that they match for all routers in SAProtocol. Some routers which previously had spaces in the type names of the router for these commands have now been changed.

Version 4.36 Beta (Server, Client, Mini, PanelDesigner) 2/11/2010

1. WARNING: This version changes the communication protocol. All applications must be upgraded to move to this version. Older versions of the client will not work with this version of the server and vice versa. As always we recommend making a backup copy of the Pathfinder Server folder before upgrading.

2. Modified the communications protocol between server and client as well as between the server and mini to remove Ascii protocol markers above Ascii 128. This protocol change should allow the software to function on systems with international character sets.

3. International Customers who wish to migrate an existing server that is set to international language settings should upgrade and launch the new version of the server first. Then Open the new client and open any scenes and resave them. Then they can migrate to the new language settings. International customers who are installing new do not need to worry about this step.

4. Exposed Silence alarms in scripting by adding AddSilenceWatch, RemoveSilenceWatch, and GetSilenceWatchState functions in scripting.

5. Modified the textual copy and paste code in Panel Designer to allow copying and pasting in the property list

6. Modified the Save functions in Panel Designer to more closely represent normal save dialogs and remove the extra message boxes.

7. Added a * to the PanelDesigner title bar when the panel has changed and needs a save.

8. Fixed an issue in the GPIO stack event handling code that was causing it to take longer than it should due to duplicate analysis.

9. Includes the option to change the GPIO livewire channel number association in the GPIO stack event qualifier and action.

Version 4.35 Beta (Server, Client, Mini, PanelDesigner) 1/30/2010

1. Added Mixing capability to the BTools emulation. BTools emulation can now be configured to be switching or mixing. Mixing requires VMIX. Please see the white paper for setting up and configuring BTools emulation with mixing. BToolsEmulatedMixing.pdf.

2. Updated automatic generation of VMIX busses in the BTools mixing emulation to utilize fewer VMIX channels and achieve the same goal.

3. On computers with certain versions of the Microsoft XML interpreter there was a misinterpretation which would cause Source meters to display as the same numbered destination meter instead. This has been fixed in Client, Mini, and PanelDesigner. Remember Panel Designer does not need to be installed on a server machine as it is automatically installed as part of the Server installation package. 4.35 server package also carries 4.35 panel designer.

4. Added an option to change the GPIO livewire channel number association in the GPIO stack event qualifier and action.

Version 4.34 Beta (Server) 1/30/2010

Version 4.33 Beta (Server) 12/15/2009

1. Fixed a bug which was introduced in 4.32. The bug made creating Virtual Routers impossible because they would appear as Gateway Routers. This has been fixed.

Version 4.32 Beta (Server) 12/09/2009

1. Fixed a bug in time based events/stackevents. If there were a lot of events scheduled to run in the last second or two before midnight, it was possible that some would not complete before midnight and those that did not would get skipped. Now they all will get run even if it takes a second or so after midnight to complete.

Version 4.31 Beta (Server) 11/23/2009

1. Added an Any option to the memory slot qualifier which will allow the actions to be run whenever the memory slot is changed. When analyzing the qualifier, the qualifier will always be true unless the named slot does not exist (has been deleted/cleared or not created).

2. Protocol Translators can now be TCP Clients as well as TCP Servers. PFServer protocol translator will maintain and reconnect to another computer IP/port.

3. Added a field on the Protocol Translator tab which shows the connection state of the translator.

Version 4.30 Beta (Server) 11/20/2009

1. Fixed a bug in the memory slot qualifier with uppercase letters in the values which would not allow a match. Matching of memory slot values is now case insensitive.

2. In the User Command Stack Event UI the Enabled and Disabled items in the combo box for protocol translators were reversed. This has been fixed.

Version 4.29 Beta (Server, Client, PanelDesigner, Mini) 11/17/2009

1. Added support for Source Profile changing and sensing in the Console Control Stack events. Qualifiers can now sense when a source profile is loaded, and source profile changes on a physical fader can be triggered from stack events. This requires Element version 2.2.0.9 or later and PowerStation 1.0.2g or later.

2. Fixed a bug reported by Broadcast Bionics where console control actions would send the fader gain even if no fader change was selected to be sent.

3. Fixed a bug which sometimes caused destination meters not to display properly in panels. This is a fix in Client and Server and Mini.

4. Protocol translators can now have three states – Enabled, Disabled, and Sleeping. Startup states can be programmed. The states can be manually changed with the protocol translator tab, and they can also be changed through stack events. Changes in these states can also act as qualifiers in protocol translators. The sleep state includes a wake a sleep command which can be set. When a translator is in sleep, it is open and will accept connections but will not process or send any data unless it sees the wake command, which will kick it to enabled. If the sleep command is received it will go into sleep mode. The sleep mode is useful in situations where you have multiple backup automation systems trying to address the same set of resources (like GPIOs). For example if you have 2 Google boxes (Primary and Backup) communicating via BTools emulation, you can program both emulators to target the same GPIOs. The one that is not active will remain asleep and be ignored unless a wake command showing it has taken over is received. The current state is also synced across the cluster.

5. Added the REGEX keyword. This can be used in protocol translator sleep and wake commands and in memory slot analysis and in protocol translator command analysis. In these data fields use REGEX(myregex). This allows a stack event memory slot or inbound protocol translator command to be analyzed using a regex for a match. This is useful for example in data where you may get the results of multiple closures in a row and you only care about the third one. See Wikipedia for information on Regex.

6. Added the syntax command to SAProtocol. This allows the syntax for getlist functions to be retrieved. Will be used in the new stack event editor to retrieve PFS data.

7. Fixed a bug where if the main form load fails, it could leave the main client connect port at 0 which then picks an arbitrary port. This is fixed.

8. Added the Previous entry to the Route Change Source Stack Event Action. This will allow you to route back to whatever was previously selected without needing to know what that selection was. This is useful if you want to quickly change the source routed to a destination and then return back to whatever was previously selected. PFS must have been running long enough to have seen a change to know the previous entry.

9. Added the Previous entry to the Element Profile Change Stack Event Action. This will allow you to load the previously selected Element Profile. This is useful if you want to quickly change an Element profile and then change back. PFS must have been running long enough to have seen a change to know the previous entry.

10. Added the Previous entry to the Source Profile Combo (see item 1). This will allow you to load the previously selected source profile. This is useful if you want to quickly change a source profile loaded to a fader and then change back to whatever was selected. PFS must have been running long enough to have seen a change to know the previous entry.

11. Added the Any entry into the Router Change Source Stack Event Qualifier. This allows the actions to be run whenever a new source is assigned to a destination no matter what the source is.

12. Added the Any entry into the Element Profile Change Stack Event Qualifier. This allows the actions to be run whenever a new Element Profile is loaded.

13. Added the Any entry into the Source Profile Change Stack event Qualifier. This allows the actions to be run whenever a new Element Source Profile is loaded.

14. Introduced Functions into stack events. Functions may be used in fields in place of values. This allows you to do things like make a route change to whatever source number resides in a memory slot, or make a label on a panel display the name of whatever source is loaded to a destination. Use a Function by using the keyword funct:functname(). So for example – funct:add(1,2). Functions can also be nested. funct:StartsWith(funct:MemorySlotValue(“CurrentState”),”ONAIR”)

1. funct:RouterName(<RouterNum>) Returns the name of a specific Router when given the number

2. funct:SourceName(<RouterNum>,<SourceNumber>) Returns the name of a specific Source

3. funct:DestName(<RouterNum>,<SourceNumber>) Returns the name of a specific Destination

4. funct:SourceDescript(<RouterNum>,<SourceNumber>) Returns the description of a Source

5. funct:DestDescript(<RouterNum>,<DestNumber>) Returns the description of a Destination

6. funct:SourceRoutedTo(<RouterNum>,<DestNumber>) Returns the number of the source that is routed to a destination

7. funct:SourceNameRoutedTo(<RouterNum>,<DestNumber>) Returns the name of the source that is routed to a destination

8. funct:SourceDescriptRoutedTo(<RouterNum>,<DestNumber>) Returns the description of the source that is routed to a destination

9. funct:CurrentElementProfileID(<IPAddress>) Returns the ID Number of the currently loaded Element Profile

10. funct:CurrentElementProfileName(<IPAddress>) Returns the currently loaded Element Profile Name

11. funct:CurrentElementProfileState(<IPAddress>) Returns the state of the currently loaded Element Profile

12. funct:StartsWith(<DataString>,<StartsWithString>) Returns a String "True" or "False" as to whether the DataString starts with the StartsWithString (Case Insensitive)

13. funct:MemorySlotValue(<SlotNameOrNumber>) Returns the value in a specific memory slot

14. funct:Add(<NumberA>,<NumberB>) Adds two numbers and returns the result

15. funct:ProfileNameLoadedToFader(<ElementIP><FaderNum>) Returns the name of the source profile loaded to a physical fader (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

16. funct:ProfileIDLoadedToFader(<ElementIP><FaderNum>) Returns the ID Number of the Profiel loaded to a physical fader (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

17. funct:LWCHLoadedToFader(<ElementIP><FaderNum>) Returns the Livewire Channel Number loaded to a physical fader (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

18. funct:FaderLWCHLoadedTo(<ElementIP><LWCHNumber>) Returns the physical fader number that a Livewire Channel Number is loaded to (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

19. funct:LWCHLoadedToFaderDest(<Router><Dest>) Returns the Livewire Channel Number loaded to a fader by the fader’s Pathfinder Destination Number (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

20. funct:ProfileNameLoadedToFaderDest(<Router><Dest>) Returns the Source Profile Name loaded to a fader by the fader’s Pathfinder Destination Number (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

21. funct:ProfileIDLoadedToFaderDest(<Router><Dest>) Returns the Source Profile ID loaded to a fader by the fader’s Pathfinder Destination Number (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

15. More functions will get added later as the need arises. It should be noted that the UI does not guarantee that a function is returning a valid value for the field the function is being used in. An invalid response will be ignored.

16. Fixed a display bug in the response of getlist userpanels.

17. Added hovering tooltips over fields in the stack event editing ui so the user knows whether text or a number are being written to the stack event XML from the field. This helps proper function use.

18. Warning: Significant changes were made to stack events to accomplish all of the goals above. If you run into any problems with your stack events in this beta, feel free to roll back to 4.28 and report so that we can fix ASAP.

Version 4.28 Beta (Server, Client, PanelDesigner, Mini) 8/17/2009

1. Rewrote much of the underpinnings of stack events so that they consume less memory and the properties pass through a function that analyzes for function calls. Function calls will be introduced in 4.29.

2. Added scripting support for PlayAudio and user log messages so that they can be called from a script,

3. Added support for PowerStation. This is the first version of PFS that fully supports Powerstation and ICEIO. The powerstation must be running software version 1.0.0d or later.

4. Fixed the gain range for controlling normal audio nodes, mic nodes, and ICEIO gains.

5. Fixed issues with PFS where new panels often required a restart of PFS before they would be available and start working.

6. Fixed an issue where deleting a memory slot was not causing a check of related stack events. Now it does.

7. PFS now monitors the PFSPanels folder for changes to panels and to the hardwaremap file and reloads files accordingly within a minute of their being changed.

8. Added two additional tabs to PFS – One for logs and one for panels.

9. The Panels tab now displays the panels that are on the server. The add and edit buttons will launch the panel designer and load the correct panel or a new one. The delete will delete a panel.

10. The log files tab now displays the list log files. Files may be viewed or deleted. Clicking view will open the log file in whatever application the machine is set up to open .txt files with.

11. The log file tab also now has an option for auto deletion of log files older than a certain date. If this option is turned on, deletion will take place nightly at approximately 12:12:00 AM.

12. Found and fixed an issue where LWCP commands which spanned multiple packets might not be parsed properly. For example long user profile lists. This has been fixed.

13. Fixed an issue where closing a meter or meter fader in one place would cause the meter or meter fader that was locked to the same IO to freeze. The meter was not unsubscribing and subscribing properly. This has been fixed in the server, client, and mini.

14. Added code to clean up meter subscriptions if the client is forcibly removed such as in a non-graceful shutdown of the client.

15. Placed a timer to space out the initial check of modified stack events after their loading to allow subscriptions for silence detection, etc. to spin up properly and subscribe with the device. This issue was previously causing silence detect events to execute on application startup before the actual initial subscription to those events took place with the node.

16. Added an addition line that can be added into the PFSMini configuration file at the end. Placing the line “AlwaysOnTop=True” without the quotes will make the mini panel always stay on top of other applications.

17. In Panel Designer – added the command line options for opening a specific panel file or a new panel. This is used by the server to launch the designer with a new panel or a specific selected file.

18. In Panel Designer - Fixed an issue where after saving a panel to a location other than the default location, Panel Designer would resort back to the default location on each FileIO operation. It will now remember the last save/open location until you shut down the application.

Version 4.27 Beta (Server 4.27 – Not released to public) 5/16/2009

1. Added SetMemorySlots and DeleteMemorySlots to SAProtocol (Alias sms and dms)

2. Added wildcards for Get,Set,and Delete Memory slots. Using a * at the end of the slot name will find all slots that start with the text before the *.

3. Added code to auto-delete memory slots if they are only being used by a stack event and that stack event gets deleted.

4. When in verbose mode in SAProtocol, gms can return the owner, last read object, and last write object.

Version 1.07 Beta (SAPortRouter 1.06) 6/17/2009

1. Added an option in the GPIO config when sending user commands to a GPIO driver via the GPIO port option. With this option, quotes will not be sent around the custom message. Prophet did not implement this with quotes, so this allows it to work better for Prophet.

Version 1.06 Beta (SAPortRouter 1.06) 6/17/2009

1. Fixed a bug in the GPIO port messaging via SAPortRouter where the port was not issuing the login command to the driver before attempting to send commands.

Version 4.26 Beta (Server 4.26, Client 4.26, Mini 4.26, PanelDesigner 4.26, GoogleVMIXWidget 1.0) 4/17/2009

1Since 4.25 was never publicly released – see the notes under 4.25 in addition to these notes to understand the changes since 4.24

2. Added the MeterFader control as described under 4.25 to Panel designer and Mini as well. This allows metering and a fader to control audio node level, VMIX level, or Element fader level. This control is now resizable as required by mini panel designing. The close float-in only appears when it is a standard meter in PFClient, and not in mini or designer. Right-clicking the panel will bring up program bus assignment buttons as well if the control is directed at an Element console fader. It is important to note that PF cannot always figure out the initial state of the Element fader on/off and program bus assignments. The commands to fix this are supposed to be included in the next Element release. Until then, after PFS is started it is possible you might have to switch the fader off once before these buttons will work properly in mini and client.

3. Fixed the output of some getlist commands when the request yielded no information to return.

4. Introduced a VMIX Control widget for the Google Automation system. This is a first beta release for the NAB show. Drop the zip file into the plug-ins folder on the Google automation system and then add the widget in Google. There is a text file in the resources folder that gets created that must be modified with the IP address of the Engine to control. After modifying this, restart the Google software to get the widget to control the correct engine. This only presents the first 5 VMIX channels at this point in time.

Version 4.25 Beta (Server 4.25, Client 4.25) 3/12/2009

1. Added a Gain Control Stack Action. This action allows you to pick a source or destination that supports gain control and change the gain as an action. It is intelligent enough to know whether the gain command should be directed at the node input or output gain, VMIX fader gain, or actual Element fader gain. This action also allows for turning channels on or off if the destination is a VMIX fader or Element fader. Of course turning these on and off is also possible through the Console Control and VMIX sections. For the Element fader, this option is slightly different from the console control action as it is tied to the actual fader as opposed to the livewire channel loaded to the fader. Internally the code dynamically changes the command sent to reflect the actual Livewire channel loaded on the fader. In the Console control section, the command is directed at a Livewire Channel number and so if that moves to a different fader the command is directed at the different fader. So it depends whether you want to control the physical fader no matter what is loaded to it or the Livewire channel no matter which fader it is loaded on. Warning! – PFS cannot currently detect the state of Program assignment and on/off buttons on the element on startup. They will not appear correctly until the user makes a change to them on the console. This will be fixed in the next Element beta code revision.

2. Added internal architecture so that engine objects know what Element is associated with them.

3. Added a latching option to user button qualifiers. Checking this option on will make the button event work in a latching fashion without any additional logic events. When this option is on, button down is no longer a qualifying property. Instead the State on or off is the property and PFS handles switching that state with each push.

4. Created a new meter in PFClient. This meter has new graphics and includes a fader for any IO that supports gain changing including node IOs, VMIX IOs, and Element Channel Destinations. The VMIX and Element faders, and On/Off Button is also present. For Element faders, right-clicking on the meter box will present a PGM assignment section. Dragging the fader with the left mouse button is for precise positioning. If you drag it with the right mouse button it will go to the nearest full db when letting go. Double-clicking will send it to 0.

5. Added a checkbox in the stack event main section that will allow delayed actions to be aborted if the qualifier state changes before the delay time is reached. This is useful when the customer wants the user to have to hold the button for a brief period of time before it will work.

Version 4.24 Beta (Server 4.24) 3/12/2009

1. Added a Device Failed qualifier to stack events. This will allow users to run actions if PFS can no longer communicatye with a device. This will trip if either LWCP or LWRP port fails for those devices that carry both,

2. Added a User Defined Log Message Action to Stack Events to generate user defined log messages. The log message typeID must be 9000 or above

3. Added a checkbox to the email stack event action to include a Date/time stamp in the email

4. Replaced spaces in the remotedevice section of the log if present to make the log entries more easily parsed

5. Routers which use the Generic Setup Wizard were not closing the communication port and reconfiguring it after the router was edited (For example XI-Audio UDP, ZSys, Sigma)

6. Added logging to SARemoteGPIO By Port and By Pin object so that remote device state changes (online/offline) will get reported in the log

7. Attached RouterDeviceReceievedCommand RouteStat (2001) log messages to incoming XIUDP RouteStat commands

8. Attached RouterDeviceReceievedCommand SilenceThreshold (2002) log messages to incoming XIUDP StreamStat commands

9. Setup XIUDP Router StreamStat to act like silence threshold enabling this trigger to work in silence detect stack events and standard events

10. Added a log item for XIUDP Router Source stream active/inactive monitoring

11. Modified the remote device field of log messages coming from XIUDP routers so that it reported port 91 rather than 93

Version 4.23 Beta (Server 4.23, SA_PortRouter 1.05) 2/24/2009

1. Fixed a bug in the server where sending an ActivateRoute command through SAProtocolTranslator to a virtual router where the source was 0 would not clear the route, but rather would return an error. This command will now clear the route when addressing a virtual router.

2. Fixed a bug in the server where silence detect stack events would not get tripped and cleared when the node the event was addressing failed or became unresponsive. This condition will now trip the audio based stack event. It should be mentioned that it may take PathfinderServer as long as 30 seconds to a minute to detect and confirm a node failure. Then the silence wait time in the stack event will be added to that before the event will be tripped. In the future we hope to have a device failure qualifier that can be used independent of silence detect. Finally, it is possible that PFS would trip the silence alarm if the unit becomes unresponsive to commands from Pathfinder but is still passing audio. If PFS cannot talk to the node, it assumes it has failed and sets the audio to nothing.

3. Fixed an issue in the server installer that would cause the installer to get re-launched if certain non-critical text files were deleted from the server folders.

4. Fixed an issue in SA_PortRouter where if a source was routed to two destinations and the first destination TCP connection was not established, incoming commands would only get sent to the second connection intermittently.

Version 1.02 (SA_AudioPlay 1.02) 1/24/2009

1. Added a User Interface to the SA_AudioPlay service. The installer now also installs a user interface that can be used to start and stop the service and set parameters such as Username, Password, Default Audio folder, and TextToSpeech Voice. The service needs to be restarted after making changes to the configuration.

2. If you pass the service the name of a file without the full path, the service will try to find the file in the folder configured as the default audio folder by the configuration application.

3. If you pass the texttospeech a field with the prefix File:\\ (i.e. FILE:\\C:\Junk\text.txt), the service will try to open the text file and read the contents instead oif reading literally what is sent.

4. Known bugs in both 1.00 and 1.02

1. The service will currently only play on the first sound card on the computer which may or may not be the default one. We are working on a fix for this.

2. There may be an issue with PathfinderServer reestablishing a connection with the service after the service has been restarted. Restarting PathfinderServer fixes this. This has not been confirmed yet.

Version 4.22 Beta (Server 4.22, Client 4.22, PanelDesigner 4.22, SA_AudioPlay 1.00) 1/15/2009

1. Added port 9500 to the server. This is a dedicated port running the SAProtocol translation. It will always exist for remote systems to control and work with Pathfinder Server.

2. Added a Verbose command to the SA Protocol Translator. This adds additional stream and channel information into the getlist routestats command and may be used in the future to indicate the need for slightly more verbose responses to some commands. Turn the mode on and off with verbose on and verbose off.

3. Created 2 new router types (PathfinderRemoteGPIOByPort and PathfinderRemoteGPIOByPin). These routers will route GPIO closures through Pathfinder between sites by pointing one Pathfinder server at another server. Because it is TCP only, it will work over the Internet or WANs. The ByPin version can also be used to create a Pin based GPIO router rather than a port based GPIO router. This can be created between servers, or on the local server using the loopback address. These routers will also allow GPO to GPO and GPI to GPI (where the device supports GPI changes from software) routing.

4. Added a PUID table to the databases used by the two new routers mentioned above to make sure between creation and deletions, points obtain the same ID in the database. Eventually livewire points will also be added to this database so that in the future an ID is assigned at initial discovery and it will never change unless this table is wiped. Thus routers will be able to be destroyed and recreated and still always gain the same ID. This is only implemented for the remote GPIO routers at this point in time. But in a future edition will probably implemented for others as well.

5. Added support for the XIAudioUDP Router developed by Streamcom. Streamcom has developed a router that routes the UDP data from IPorts allowing a multsite audio router to be created. Pathfinder can now control this router just like any other router it supports.

6. Fixed a bug where if a time based stack event was edited from the raw file rather than the PFS UI, it would get picked up but the times would not get entered into the current day’s todo table and so they would never run.

7. Added the IPort as a device that support VMIX into PFS.

8. Fixed a bug that was causing the VMIX state to not get initialized properly so stack events might require the VMIX to get turned off and on again before they would register properly.

9. Added more detailed messaging to the getlist sourceaddress and destinationaddress commands in the SA Protocol Translator.

10. Increased performance significantly on stack event file loading.

11. Added code that would only check for and load newly created stack events (created manually by editing the file or by the UI) if there was at least 7 seconds before the next time based event. Some of the file IO can be intensive when loading a bunch of newly created events so we wanted to make sure existing time based events were not blocked. If there is not enough time the load is delayed slightly until there is time.

12. Added a field in the events tab of the server that displays the current time and date.

13. Added a field in the stack event tab so you can see how many stack events are in the list.

14. Added a GetMemorySlot command to the Software Authority translator. This allows you to view all of the memory slots, all used memory slots, or specific memory slots by name or by value. Type ? GetMemorySlot for details. There is also an alias for this command gms so you do not have to type the full GetMemorySlot.

15. Added a text file which if it exists will allow you to enter names of stack event files with a wildcard (*) at the beginning or end. If these stack event file names exist, they will not get synchronized across a cluster. The filename is StackClusterSkip.txt.

16. Added a menu item which will allow you to select memory slots to get stored to a table so that they do not get cleared between restarts. If this option is on, memory slots will retain their values between restarts. If it is off they will get cleared on restart.

17. Reloading stack events will not update a changed stack event in memory if it’s delayed timer is currently running. It will wait for the dely timer to end before loading the modifications for that event into memory. In that case the update will get loaded at the next normal refresh within 60 seconds.

18. Worked on the GPIO panel in the client. It now shows both GPI and GPO of both the source and destination involved in the route. This is much more intuitive. It also shows the route direction using a line. This line becomes important in the PFSRemoteByGPIOPort and ByPin routers as these routers can route GPI to GPI and GPO to GPO and GPO to GPI as well as GPI to GPO as long as the when the GPI is a destination the device supports it (Axia driver).

19. The SourceList call in SA Protocol Translator was reporting erroneous information in the last column when addressing GPIO routers. This has been fixed.

20. Certain internal collections for fast stack event searching were not getting cleared when events were being modified. This has been fixed.

21. Fixed a bug with the Broadcast Tools 16x4 protocol translator which caused routes on the 4^th destination not to work

22. Fixed a bug with the Broadcast tools protocol translator which would cause it to address the wrong virtual router in certain extremely rare situations.

23. Added support for the LCD 17 button panel into PFS.

24. Added support for the LCD 17 button panel into the Panel Designer UI

25. Fixed a bug that would not allow a stack event to function properly if multiple audio (silence detect/present) qualifiers existed in the same event. This is fixed in this version.

26. Fixed a bug where in certain extremely rare situations the clearrecordset would not work when updating a virtual router database leaving the database with a blank table in the sources or destinations.

27. Added the support for the GET SUPV STATE command supported by more recent beta versions of the Engine to check LWCP state.

28. Added a new stack event group in both qualifiers and Actions called Console Control. This supports tripping and sensing changes to On/Off/Mute/PGM 1 through 4 assignments. It also supports setting a fader level. It will not sense the initial state on startup so the state has to change for PFS to pick it up. This is due to current command restrictions in the Element. Also some of these functions are only supported in Beta and Alpha versions of Element code and so will not be fully available to the public yet.

29. Created a new service called SA_AudioPlay. This service can be deployed to computers on the network including the server and presents a TCP port (11051) to which you can send the following tcp commands. Login Admin Admin, playaudio <filename>, texttospeech <text>. It will allow files accessable by that computer to be called and text to speech commands to be called, and they will play on the default sound card. This installs on the computer as a service. Once installed either reboot or go into the service manager and start the service. At this point in time the service will only play wave files. The service requires the .net 3.0 platform which can be obtained from the Microsoft updates page if it is not already installed.

30. Added a stack event group of actions to trigger the SA_AudioPlay services on local or remote computers. In this way PFS can trigger basic text to speech and/or audio playback.

31. Added and implemented the following log objects ServerEvent_RefreshStackList, ServerEvents_StackEventLoadEvent, ServerEvents_EventRemoveEvent. These are not turned on by default. They must be turned on. But then stack event removals due to file deletion, changes due to stack event modifications, and initializations after modfiying, creating through UI, or discovery may be logged.

32. Added log events to track the SA_AudioPlay functions and responses from the remote computer so that they can be logged. These are turned on by default if logging is enabled.

33. Fixed a bug where very old versions of engines when upgraded would sometimes not get the right database entry updated for backfeed sources. And if automatic SRC/DST additions were turned on could actually lead to a duplicate entry getting created for the backfeed.

34. Fixed a bug in Panel Designer that would cause the selection of destination on meter controls to get written as source and not stick as destination.

Version 4.21 Release CandidateV2 (Server 4.21, Client 4.21, PFMini 4.21, PanelDesigner 4.21, VMIXControl 1-05)

1. Added new Help File to Client and Server installation packages.

2. BG_111 - Fixed a bug since 4.20 in Server where new protocol translators would not work or appear until PFS was restarted

3. BG_112 – Fixed a bug in the Server where new Element profiles would not be available to the server until the server disconnected and reconnected to the Element or was restarted.

4. In SAProtocol in the Pathfinder Server, modified the TriggerGPO and TriggerGPI commands so that they sould return a state command if no change was made. In other words if the command asks for the same state that already exists, previously PFS would return nothing since nothing actually changed. Now in this case it will return the current state.

5. Removed erroneous character from getlistversion command in SAProtocol.

6. Removed erroneous character from Error message if a route change is requested that is locked is SAProtocol.

7. In VMIXControl, fixed a bug that in certain reconfiguring circumstances could cause all faders to disappear when they are not supposed to,

8. In VMIXControl, made the Engine line at the top of the tree display the host name of the engine when possible.

Version 1.04 Release Candidate V1 (SA PortRouter 1.04)

1. First Release Candidate of the SAPortRouter serial data routing service application. This application runs as a service on the computer. There is a configuration application that allows the user to drag Serial, TCPClient, and TCPServer ports to the service and configure their settings. Then after committing the changes and starting the service, you can route the data traffic from any port to any port and vice versa.

2. At the moment this only supports ASCII data (characters below 128) as opposed to binary. A future version will also support binary.

3. Routing can also be controlled dynamically by Pathfinder.

4. Each port can have a defined End of Message set of characters as well which means the commands will only get forwarded when complete. To use non-typable characters for EOM, use a % and a 2 digit hex code for the ascii number. For example, a carriage return and lines feed end of message would be represented as %0D%0A.

5. This application and routing support for it requires a PathfinderPro or Legacy license.

Version 4.20 Release CandidateV1 (Server 4.20, Client 4.20, PFMini 4.20, PanelDesigner 4.20, VMIXControl 1-04)

1. Introduced the new licensing model for Pathfinder Legacy, PathfinderPC, and PathfinderPro. See Feature Comparison list and license FAQ for details.

2. Added Licensing menu item to the File menu of PathfinderPC Server.

3. Created Licensing web site to create and upgrade licenses. Legacy customers (purchased before July 1, 2008) are entitled to a free upgrade to PathfinderPro. See Feature Comparison list and license FAQ for details.

4. Added support for VMIX Control to PathfinderPC Server

5. Added a GPIO status command to Software Authority protocol.

6. Added router address and name commands to the GetList Functions.

7. Introduced VMIXControl application. This application requires a legacy or PathfinderPro licensed copy of Pathfinder. It can be installed on as many machines in this environment as desired. It must have TCP access to both the PathfinderPC server and an Axia engine. It controls the virtual mixer in the Axia Engine. This application requires PathfinderPC Server 4.20 or later.

8. Introduced Metering and web browser support to Panels. This feature is only available to legacy and pro licenses.

Version 4.19 Beta (Server 4.19) 5/22/2008

1. BG – If the Mail Server settings were set with a blank user name and password for anonymous emailing, setting an email address in a standard silence detect event would generate a warning message. Should be fixed in this version.

2. Add the new version of the Panel Designer (Version 1.20) to this installer package. See the notes below for the new features in this version of the Panel Designer.

Version 1.20 Panel Designer Only Beta (Panel Designer 1.20) 5/22/2008

1. You can now select multiple controls on the panel to manipulate together by holding the shift or control key and selecting the additional controls.

2. Selected controls will have a handle around them. Resize by dragging on the handles. If multiple controls are selected, they will resize together. Holding the Right mouse button and dragging on the handles with will allow you to move (as opposed to resize) selected controls.

3. When controls are selected, the arrow keys can be used to resize one pixel at a time.

4. If you hold the shift key while tapping the arrow keys, you can move the selected controls one pixel at a time.

5. Added AlignRight, AlignLeft, AlignTop, and AlignBottom menu items. There are also shortcut keys for these menu items. These will automatically align the selected controls to the selected edge. For example, selecting Align Left will look through the selected controls for the control that is farthest to the left. It will then align the rest of the selected controls to that same left point.

6. Added Spread Horizontally and Spread Vertically menu items. There are also shortcut keys for these menu items. These will find the left most and right most (or top most and bottom most) selected controls and evenly spread the other selected controls between them. If the spread would cause the controls to overlao or the controls are overlapping, spread will place them right next to each other instead of overlapping them.

7. If multiple controls are selected, changing properties that apply to all controls will be applied to all controls. So you can select a bunch of buttons and then apply the same color/picture settings, etc. to them. This also works for left, top, height, and width settings.

8. If multiple controls are selected and the property being changed is one that should not be duplicate (for example name), the system will ask if the user wants to auto-increment the property. This applies to properties such as Name, Caption, and hardware map Button/Circuit number. For example a user could select 10 buttons and then set the Hardware map IP address and module number with one property change. And then set the first button number property, and the system will ask if the user wants to auto-increment the rest.

9. If you change the panel name and the panel caption was the same as the old panel name, it will change to the new name too.

10. Fixed issues with Copy, Paste, and Delete functions.

11. You can now copy, paste, and delete multiple controls if they are all selected.

12. Fixed several other minor issues with Panel Designer.

Version 4.18 Beta (Server 4.18) 5/16/2008

1. BG_108 – Some users needed to send emails through a mail server that did not require user authentication. We modified the code so that if the username and password fields in the mail configuration are blank, PFS would not send the authentication commands. This did not work as expected in 4.17. Should be fixed in this version.

Version 4.17 Beta (Server 4.17) 5/16/2008

1. BG_106/105/102 – You could not enter a recurring daily stack event time based qualifier where the start day was different than the end day crossing midnight. For example - starting Mon at 11:00PM and ending Tues at 1:00 AM. The system would not let you set this up and would reset the end time to a second past the start time. In addition direct XML editing would also not allow this kind of event to run as the logic was not in place for this. This version has logic written to handle this condition and the restrictions lifted to allow this qualifier.

2. BG_104 – Some users wanted to be able to send emails to non-standard SMTP port. This version adds a field to define the server SMTP port. This ability has not been tested with a mail server set to this state yet.

3. BG_108 – Some users needed to send emails through a mail server that did not require user authentication. We modified the code so that if the username and password fields in the mail configuration are blank, PFS would not send the authentication commands. This has not been officially tested with a mail server set to this state yet.

Version 4.16 Beta (Server 4.16) 4/2/2008

1. BG_93 – Entering a start time for the afternoon of one day, and an end time for the afternoon of the next day would not work in stack events. The event system was designed to make sure that the end time is later than the start time, and was not taking the day into account as part of this. This has been fixed.

2. BG_94 – CRITICAL – Beginning with version 4.05, backfeeds are handled differently in the database. Because of this change some customers found that if there were 2 backfeed sources that had been loaded to the same fader, and then the router was edited, in certain situations, not all of the later engine sources and destinations would get brought back into the database after the edit. This has been fixed.

3. BG_95 – If locks states somehow got out of sync between a base router and a virtual router, the state would not get discovered until a lock was changed. This version adds the lock state into the regular check functions.

4. BG_96 – Locks were not always traversing properly from the base router to a virtual router unless the PF number of the base point and virtual point were the same. This has been fixed.

5. BG_97 – If a firmware update on an Axia device removed a system level lock state from a resource, PFS would not pick this change up and unlock the resource without a restart. This has been fixed.

6. BG_98/99 – The Auto SRC/DST addition function was not checking previous tables for pre-existing ID numbers before assigning a new number. This has been fixed.

7. BG_100 – Backfeeds using RTPA address as opposed to LWSA addresses were not always being detected by Auto SRC/DST additions or by the updating functions. This has been fixed

8. FQ_32 – This version detects the version of Engine software on the Engine, and only opens LWCP (VMIX) control connections if the Engine software is late enough to support it. It also will only list Engines with late enough software in the VMIX drop down combos.

Version 4.15 Beta (Server 4.15, Client 4.15, PanelDesigner 1.19, Mini 1.19) 3/20/2008

1. BG_88 - If server is set to require login, and you need to manually point client to a new IP, login would crash client. Then on restart it would work. This has been fixed. May still need some tweaking.

2. BG_87 - Captions for the main panel object entered in Panel Designer do not get written to XML. This has been fixed.

3. BG_87 - Captions for panels entered in Panel Designer do display in panels in client or Mini. This has been fixed.

4. BG_87 - Friendly Captions for panels entered in Panel Designer do display in panels in client in Panel List. The File name is shown instead. This has been fixed.

5. FQ_29 - Engine based VMIX control is now supported by both stack events and ACU-1 translator. All UI combo boxes that relate to VMIX now also display Engines as possible VMIX control objects. This also means that PFS will try to maintain a 4010 LWCP connection to all engines. This may lead to extra connection attempts and log activity when in a facility with older engine code. We will work on a modification in the next version to prevent these connection attempts if the Engine software is older than the new release version - 2.4.8w3.

6. BG_89 - During Livewire Scan in initial router setup, IP addresses are found and added to the list multiple times. This means the actual connect attempts in the next phase of the scan also happen multiple times causing a significant delay in the time it takes to complete the scan. Fixed

7. BG_90 - Forced any text commands being sent to DISP object on hardware user panel to be sent in the ON context.

8. BG_92 - Occasionally a scene change would be left showing all or most routes routed to a single source in the client. Closing and reopening the router in the client fixed the display problem. This has been fixed.

9. FQ_31 – Full cluster replication support now exists for the additional data file required by BT Protocol Translators.

10. BG_83 – The Top field in Panel Designer is read only. This has been fixed where necessary.

Version 4.14 Beta (Server 4.14) 2/28/2008

1. FQ_27 – Server – Added support in Stack Events to turn Element Faders On/Off. In the User Button Section of Stack Action, Select the Use Button Address option and enter the Element IP Address. For Module Number scroll to LWChannel. Enter the LWChannel Numer, and then select whether the On Button or Off Button will be triggered, though in reality either can be used and the actual channel on/off is then tripped by the State property. Use the State property for either On or Off.

Version 4.13 Beta (Server 4.13) 2/9/2008

2. BG_85 – Server – Compiled with the original TCP Base but with a fix for BG_75 instead of the new TCP base introduced in 4.12. The New base introduced in 4.12 has a bug where if there are more than 5 clients (PFClient or Mini) trying to connect at the same time as would happen during a cluster roll or when the server is starting and there are already a bunch of clients running that are trying to connect, the new TCP stack was not letting the clients join. Thus we fixed the BG_75 issue in the original TCP base as well, and rolled back to that TCP base until we could spend some more time on the new TCP base.

3. FQ_18 – Server – Introduced a protocol translator to translate BTools protocol. Will translate audio switching, GPI/PIP, GPO/Relay. No mixing or cross-fading is supported at this point in time.

Version 4.12 Beta (Server 4.12, Client 4.12) 1/20/2008

1. BG_75 – Server - If a client application was shut down or disconnected unexpectedly and the server connection had a large amount of data in buffer to be sent to the client, it could cause the server to crash with a Dr. Watson error. This has been fixed.

2. ***Important*** - This version also uses a new TCP base for communications between clients and server which provides for more efficient communications.

3. BG_76 – Server - If two Virtual routers shared the same base point and a lock was issued from one virtual router, the lock would not engage on the virtual point on the other virtual router. This has been fixed.

4. BG_77 – Server - A stack event with an Element profile load qualifier that was set to run actions on startup, would sometimes not execute when the server was not part of a cluster. This is because the stack event engine would launch before PFS has a chance to connect to the element and get the current profile. The first run of this kind of action on startup now gets delayed until a connection is established with the Element and the profile check successfully responds.

5. BG_78 – Client - The viewable audio state bubbles might not display after loading a very large router (5000x5000). This occurs if the scroll timer executes prior to the completion of loading all sources and destination information into the grid. This has been fixed.

6. BG_79 – Server – When editing Time based standard events from the client, the edit window would not appear if there were no events in the existing server. This has been fixed.

7. BG_80 – Standard Silence Detection/Backup route events were not displaying their state on clients that were connected to the backup server in a cluster. This has been fixed.

8. BG_81 – The state of Time based standard events was not being sent from the Primary machine in a cluster which owns the event system to the backup. Therefore this state would not display properly on clients connected to the backup server.

9. FQ_22 – Added log settings for script (not stack event) timers so that all changes in script based timers could be logged if desired.

10. FQ_23 – Added a text file which if it exists holds lines of text. If the text file exists, each line in the file is brought into an array. Before any line is written to the log file, the array will be checked to see if any of the lines of text exists in the log entry. If it does, the log entry is skipped and not written to the log. The text file to enter this information is called LogSkip.txt. This allows you to prevent certain log entries from appearing.

Version 4.11 Beta (Server 4.11) 12/18/2007

1. BG_76 – The flash state on user buttons would not always work properly or traverse a cluster properly. This has been fixed.

Version 4.10 Beta (Server 4.10) 11/15/2007

1. BG_73 – Duplicate event names in a stack event group cause the stack event not to load or run. This is only since 4.06 due to the optimization. Duplicate names are supposed to be disallowed by the UI, but if an older event has them, this version will alter the duplicate name when it loads to allow the event to load and run.

2. BG_74 – Any time based stack events beyond the first one would not load or run. This is only since 4.06 due to the optimization changes. This has been fixed in this version.

Version 4.09 Beta (Server 4.09) 11/13/2007

1. BG_72 – Panels that used RouteMaps where the maps where the names of the router, source, and destination instead of the numbers would cause the server to repeatedly launch a database finder box. This is the only fix since 4.08 in this version.

Version 4.08 Beta (Client 4.08, Server 4.08) 11/11/2007

1. Since 4.05, 4.06 and 4.07 were not general releases, please review release notes for those versions as well to get full scope of changes in this beta release)

2. BG_31 – When large routers are opened in the client, the client appears to hang. This has been fixed and a count bar added in the lower left corner of the client to display the load count as IOs are loaded into the grid.

3. BG_32/65/66 – Lock States were not synchronizing properly between cluster nodes. This has been fixed in this version.

4. BG_50 – The Use Lock State checkbox in a route status qualifier gets stuck on. If you turn it off, it is back on when you try to edit the qualifier again. This has been fixed in this version.

5. BG_51 – The Use Lock State checkbox in a route status qualifier did not work. With this check on, the lock did not affect the qualifier. This has been fixed in this version.

6. BG_52 – Protocol Translator message qualifier does not work. This is only an issue with 4.06 and later due to the optimization. It has been fixed in this version.

7. BG_53 – VMIX qualifier does not work. This is only an issue with 4.06 and later due to optimization. It has been fixed in this version.

8. BG_54 – Button name field at the bottom of a button qualifier was hidden as it is not viable as an option. The button name is already at the top of the qualifier as the primary object. Also the Caption field was not working as a potential part of the qualifier. This has been fixed.

9. BG_55 – The Force Lock checkbox in the ActivateRoute Stack Event action does not work. This has been fixed in this version.

10. BG_56 – In the UserButton Stack Event Action, if an IP based button is selected, the default button number was a single digit rather than an option from the drop down menu. This has been fixed in this version.

11. BG_58 – In the client, after adding a new virtual router, the router drop down combo would turn blank. After that no routes in an open chart view can be made until the router is reselected in the drop down. This has been fixed in this version.

12. BG_59 – The Lock Override checkbox in a Scene Change Stack Event Action would not save or work when the action was executed. This has been fixed in this version.

13. BG_60 – In the UserButton Stack Event Action, KeyState has no meaning as this is a qualifier function not an Action function. This has been hidden in actions.

14. BG_61 – Forecolor option in Stack Event Unser Button action and qualifier has been disabled as it is for future use and is non-functional at this point in time.

15. BG_64 – In a VMIX Stack Event Action, Setting a gain of 3 resulted in .3 rather than 3.0. 3.0 worked properly. This has been fixed in this version.

16. BG_67 – In a cluster, if you create a new virtual router on one server a PFClient connected to the other server would not see the new router until that client is restarted. This has been fixed in this version.

17. BG_68 – If the Probel Router translator is pointed at a virtual router, and routes on that router are in the Other State for sources routed that are not a part of the virtual router, the translator would report back garbled data. This has been fixed in this version. It now reports back 0 which equates to a cleared route state.

18. BG_69 – Prophet ACU-1 Translator was setting the timeout for silence alarms in milliseconds when the UI says seconds. This has been fixed so that the seconds variable from the UI gets multiplied by 1000 to create the correct alarm time.

19. BG_70 - Mismatched states between router tables during cluster synchronization could sometimes lead to empty or deleted router tables. This could be exhibited by deleting a router from a single server. And then shutting that server down and launching the other server and making lock changes on the still present router on that server causing a timestamp update of the routes table on that server. Then when the first server is brought back up corruption in the synchronization could occur. This has been fixed in this version.

20. BG_71 – Protocol translator additions and removals were not synchronizing across the cluster without several restarts. This has been fixed in this version.

Version 4.07 Beta (Client 4.07, Server 4.07) 10/31/2007 (not released to general public)

1. BG_42/45/47 - Editing an existing standard event in PF Client sometimes returned an error. This has been fixed.

2. BG_48 – Could not edit Virtual routers and scenes in the PF Client. This only existed in version 4.06 due to the optimization. It has been fixed in this version.

3. BG_49 – Time based stack events would not run. This only existed in version 4.06 due to the optimization. It has been fixed in this version.

Version 4.06 Beta (Client 4.06, Server 4.06) 10/28/2007 (not released to general public)

1. A great deal of code optimization work has been done primarily to the server application but also to a limited degree the client application in this version. This optimization is designed to increase performance and decrease processor load on large routers. Because of the amount of code changes involved in this work this version is undergoing rigorous bug testing.

2. BG_8 – Rare crashes of PFS server with specific clients due to hung winsock connections with the PFclient and/or probel protocol load issues have been addressed.

3. BG_44 – Prophet router computer caused sluggish routing responses when the Probel protocol was in use. This was because certain embedded messages were causing NAKS (invalid message responses) which led to cueing and repetition of messages in both directions. This has been fixed.

Version 4.05 Beta (Client 4.05, Server 4.05) 9/24/2007 (not released to general public)

1. BG_6 – When a route is requested using the Probel General Switcher protocol (for example from a Prophet Router computer), and the route change that is being requested already exists, PFS does not return a confirmation because no change has been made. In the case of the Prophet Router computer, it waits for a response for a period of time, so this could cause a delay in subsequent commands. This has been fixed so that PathfinderPC Server does respond even if the route already exists.

2. BG_12 – Leaving the Axia Automatic SRC/DST additions feature turned on can lead to duplicate additions in the database. If this feature is left on, a new source or destination can get added multiple times until the server application is rebooted. This has been fixed.

3. BG_27 - In a cluster if a PathfinderPC Client connects to the second server in a cluster before synchronization is complete, and that client has certain kinds of user panels open, they will not refresh with the initial state after synchronization completes. In this version a status is pushed after synchronization, but more importantly clients are not allowed to connect during the cluster synchronization process. Existing clients will not get dropped during synchronization though.

4. BG_28 – In a cluster if there is an orphan router database file on the second server, and a new router gets added on the primary server that uses the same number as the orphan file on second server, the router will not get created on the second server and may get deleted from the primary server during subsequent synchronizations. This has been fixed.

5. BG_29 – If a virtual route source and destination includes multiple points from the same base router, only 1 route will actually complete. This has been fixed.

6. BG_32 – In a cluster, locks made from a client connected to one server do not transfer to the other server. This has been fixed.

7. BG_33 – The Lock, UseLock, and Lock Overrides checkboxes in the RouteStatus stack event qualifier and action were not sticking between edits. Actually these were being written to the stack event file and acted upon, but on the next edit, these settings were not being brought into the edit window and would therefore revert if the user did not catch it. This has been fixed.

8. BG_34 – Cluster synchronization when large routers (greater than 5000x50000) were involved and changes were made that required a rewrite of the database on one of the synchronized servers could cause the process to appear to hang for an extended period of time with CPU loads on at least 1 of the servers at or approaching 100%. This has been addressed and the synchronization speed greatly improved in this version.

9. BG_35 – Element backfeeds may not maintain a unique source ID number in previous versions of PathfinderPC Server. The backfeed source number in PathfinderPC Server was bound to the fader number sourcing the backfeed rather than to the stream address itself. This has been fixed so that the backfeed stream address will always relate to the same PathfinderPC source address, and the information about the console and fader hosting it will change instead as it moves between consoles.

10. BG_36&37 - Cluster synchronization when large routers (greater than 5000x50000) were involved and changes were made that required a rewrite of the database on one of the synchronized servers could cause route points from the routes table to get lost and not entered into the synchronized database. This has been fixed.

11. BG_39 – The Axia Automatic SRC/DST additions feature was not sending the additions across the cluster link to the second server or updating the timestamp for the table. This has been fixed.

12. BG_40 – In the PathfinderPC Client the Number column was too small to accommodate numbers greater than 999. Numbers larger than this expanded beyond the width of the field. This has been fixed in this version.

Version 4.03 Beta (Client 4.03, Server 4.03) 8/6/2007

1. This Version includes everything from 4.02 plus the changes listed below.

2. BG_25 – If a client or mini connects to the secondary server in a cluster while the secondary server is undergoing synchronization, and that client has a user panel open, the initial state may not display properly until the control state changes or the panel is closed and re-opened. This has been fixed.

3. Added a heartbeat in the software user panels that occasionally pings the server to which it is connected to make sure the server knows it needs to be included in updates.

Version 4.02 Beta (Client 4.02, Server 4.02) 8/5/2007

1. BG_1_22 – Even when the “Run Actions on Startup” option is selected in a silence detect based stack event, it’s actions would not run after the server initially starts until the threshold is crossed. This has been fixed. This can be seen easiest using a user panel with buttons that light different colors for silence detection and audio present. With the “Run Actions on Startup” option selected, such panels will now display the correct state as soon as the server event system comes online.

2. BG_2 – Sometimes silence detect events could possibly get stuck in a state. This could happen if the meter response came back different and later than the silence detection response. Silence detect events are now completely independent of meter responses except for the initial state check after an event has been launched. This bug is also thought to have been reported more in relation to BG_7 and 15 below.

3. BG_3 – In Chart view in the client, selecting the last destination in the list would not drop the destination into the Take panel. This can lead to the user activating a route based on the last selected destination instead. This has been fixed in this version.

4. BG_7_15 – Stack events in a cluster that had a space in the name of the event did not always synchronize properly and were subject to spontaneous deletion from 1 or both of the servers in a cluster during cluster synchronization. In some places in the application spaces were converted to underscores, and in others they were left alone causing confusion in the clustering synchronization process. This has been fixed.

5. BG_9_10 – In the client, the window location storage buttons at the button of the screen were subject to an endless loop in certain configurations when the configuration was loaded. This has been fixed. In addition, the buttons were not saving whether the router panel was in list view or chart view. This has also been fixed.

6. BG_11 – If you delete a scene from a router on a server in a cluster, it tends to reappear after synchronization routines take place. There was a bug in the code that caused the scene not to get deleted on the second server, and so at synchronization time, the scene would get recreated. This has been fixed.

7. BG_13 – In the client, the connect menu to manually make the client connect to a different server would always error out. This has been fixed.

8. BG_17 – List orders on the server page sometimes displayed in a bizarre order. This has been fixed so that routers and Protocol Translators are always displayed in numerical order by ID, and stack events are displayed alphabetically.

9. BG_19 – The state of some software user panels (such as silence detect based user panels) would not update properly without being closed and re-opened after the panel had been rolled to another server either through manually connecting to a different server or from cluster server failure causing a rollover of the client. This has been fixed.

10. BG_20_23 – In the client in chart view, scrolling would not cause the blue lines to scroll as well. This resulted in the take panel being out of sync with the representative blue lines. This has been fixed.

11. BG_21 – Sometimes switching between routers in the client did not cause the correct scene list to be listed in the main scenes menu. This has been fixed.

12. BG_24 – After the client switched to a different server either because of manual server connection or cluster failover, if a router panel was active it would not be active properly unless it were closed and re-opened or the user switched to a different router panel and switched back. This would mean the user could not make routing changes on the panel until it was closed and re-opened or a different panel was selected first. This has been fixed.

13. FQ_1 – Limited the maximum size the routing dots can become in small router windows. This prevents the dots from becoming huge.

14. FQ_11 – Added the GetList function to the Software Authority Protocol Translator. This function accepts arguments and returns a variety of lists of information in the Pathfinder Server system. It has been developed for use in the new stack event editor that is still under development, but it can also be used by third party applications to obtain information from the routing system. See the document FR_11_GetListFunction.doc for more details.

15. Also, please review the white paper on the importance of time synchronization between servers in a cluster – Bug_14_ClusteringTimeSynchronizationIssues.doc.

Full Release Version 4.00 (Client 4.00, Server 4.00a, Mini 1.15a, PanelDesigner 1.16) 6/15/2007

1. Moved this to Full Release

Release Candidate Version 4.00 (Server 4.00a, Mini 1.15a, PanelDesigner 1.16) 6/13/2007

1. Panel Designer Insert menus were not working properly. This has been fixed

2. Updated the Server installer to include the 1.16 version of Panel Designer. No changes were made to the server executable itself.

3. Updated the PaathfinderPC Mini installer so that the uninstaller will not remove the configuration file. Uninstall of existing version will remove this file, but after installing this version future uninstalls will not remove this file so that it retains these settings from install to install.

Release Candidate Version 4.00 (Client 4.0, Server 4.0, Mini 1.15, PanelDesigner 1.15) 5/28/2007

1. After saving changes to a software panel, closing and reopening the panel in the client or mini should now display the changes without restarting the server. This is subject to altered state. If the current state of the control is the same as what the old control state was, then it will be updated. If a stack event has changed the property, then it is assumed the property should not be updated. Essentially when the panel is opened, the initial state is saved as a defualt. When the panel is then edited and reopened, if the current state before opening is the same as the defualt, then the control gets the new state from the newly updated panel. If it is not, then it does not inherit the new state since the control state has been altered to show something and it should continue to show that condition.

2. Fixed a bug in the panel designer that caused the wrong color to show when certain hexadecimal color numbers were used. If the number could also be interpreted as a decimal number, it would do so rather than using the hex version. This has been fixed

3. Fixed GPIO circuit naming to make it more intuitive.

4. When Selecting a GPI or GPO qualifier in a new stack event, only the source or destination drop down appears depending on whether it is a GPI or GPO. This makes this screen more intuitive.

5. Added warning messages in the GPIO stack event configuration for non-standard configurations.

6. Pathfinder PC was not restoring panel window positions when saving window positions in the window state store locations. This has been fixed.

7. Stack Event route changes were not able to use None in virtual routers to force a clear route. This has been fixed.

8. Using the Event Engine Start as a qualifier to initialize IP based button actions was not working. This has been fixed. Part of this also was that if you restarted the Element or lost and reestablished the conection to it, PFS would not push out the current button states. The LWCPCommand SendData module now Caches buttons states, and will push them out on reconnect. This will make buttons display properly after Element restart or loss of connection. It also answers the problem above since even though the Stack Event Engine in a stand-alone server starts before LWCP connection is established, the button state commands that cannot be sent to the unestablished connection get put in the button state cache and then sent when the connection does come up.

9. Fixed Tab Order in all screens in all 4 applications.

10. If the server and client have their date status set to New Zealand rather than English, standard events that are on a weekday schedule may not work. This has been fixed. However at this point in time, both client and server must be set the same. This was because the New Zealand calendar week begins on Monday rather than Sunday.

11. In Panel Designer you cannot set the GPIO hardware maps. This has been fixed.

12. If you add a new standard time based event, events for the same day that have already executed would get their status cleared. This has been fixed.

PathFinderPC Release Notes – Version 3.0

Version 3.68a (Server Only) 5/22/2007

1. This is the same as the previous 3.68 server software except an issue with the installer and windows 2000 machines relating to the iphlpapi.dll file has been addressed.

Version 3.69 (Client and Mini Version 1.12) 5/11/2007

1. Script based panels would not work correctly if they were connected to the second server in a cluster (the server that does not own the event system). This has been fixed.

2. Editing existing time based events in the client produced a record not found error. This has been fixed

Version 3.68 (Server and Client) 5/4/2007

1. Fixed a bug in the ellipsis button of the client that would not allow the last item in the list to be dropped into drop down menus

2. Fixed a bug in the server that was breaking the ability to use direct ip address configuration for the buttons

Version 3.67 (Server and Client) 4/13/2007

1. Added scripting support for raw LWCP commands

2. Fixed a bug in the Route Status stack event qualifier that only allowed the qualifier to work on the first router in the database

3. Fixed a bug in the client where the ellipsis list would occasionally select item one off from requested after switching between routers.

Version 3.66 (Client and Server and Panel Designer)

1. In Server - prohibited cluster host names with spaces in them

2. In Server - added new context sensitive help file

3. In Client - added new context sensitive help file

4. In Panel Designer install - added new context sensitive help file

Version 3.65 (Client and Server - Both should be upgraded to move to this version)

1. In the Stack Event User Panel configuration, added a warning message if the user has not filled out either the buttonname or the hostIP field. One of the two must be filled in to commit the qualifier or action.

2. LWChannel Element ON, Off button addressing in user panel stack event did not work for LWChannels above 999. This has been fixed.

3. Fixed a bug in clustering when the stack event group name had spaces in it, the file names were not synchronizing and replicating properly to and from secondary server.

4. Fixed a bug in the Ellipsis Select list. If a source or destination was selected that had the same name as the original source or destination, but was in fact different, it would not change properly.

5. Added additional sensing and messaging to alert clustering users of the illegal duplicate license state which prevents clustering from working properly.

Version 3.64 (Client and Server - Both should be upgraded to move to this version)

1. Stack Event GPIO drop down was displaying numbers rather than description, and the ellipsis buttons were not appearing. This has been fixed.

2. Stack Event Source lists and GPIO lists were offsetting the Host IP, Name, Axia Channel information by 1 because of the None field at the top of the list in the ellipsis selct list. This has been fixed.

3. In the Client Event wizard - the destination drop down lists were not populating with an initial value causing the ellipsis button to bring up a blank list until something was selected. This has been fixed.

Version 3.63 (Client, Server, Panel Designer - Both client and server should be upgraded to move to this version)

1. Added Stack Event Qualifier Support for Element Channel On/Off buttons. To use this select a user panel button qualifier, enter the Element IP, select LWChannel for the module, enter the LWChannel number, and select either On_But or Off_But to trigger the qualifier. This requires Element software version 1.1.13.9 or later.

2. Fixed a bug in the Time Based stack event qualifier. With events that were to run on repeated days, the qualifier was not resetting after the first run, and therefore would not run on subsequent days. This should be fixed in this version.

3. Fixed a bug with Software User Panels in a Cluster. If the user panel (Mini or Client) connected to the secondary server, and the panel actions were only based on stack events, the button pushes and property changes were not forwarded to and from the server owning the event system. This should be fixed in this version.

4. Improved Performance on Server for large routers

5. Added the ellipsis button next to all source and selection drop down menus. This button presents a grid to select a source or destination from. The grid includes columns all of which may be moved and sorted. The columns include such data as name, description, PFS number, Host IP, Host Name, Axia Channel Number . . .

6. Addressed Form resizing on all forms in client and server

7. Added the ability in the User Panel Stack Event qualifiers and Actions to address Element user panels directly without first having to create a software panel and map to it.

8. Added support for the Accessory Panel in both Panel Designer and the User Panel Stack Event qualifiers and actions

9. Fixed an issue where backfeed names were just displaying as To rather than the whole backfeed name

10. Reduced traffic between client and server as routers to have names transmitted were not being cleared out of the server pending cue and thus were being sent additional times periodically

11. Worked on Backfeed movement between Elements and subsequent owner displays

12. Fixed an issue in the server automatic addition of found LW sources when that was selected that was causing backfeeds to be added multiple times rather than their ownership changed

Version 3.61 (Client and Server - Both should be upgraded to move to this version)

1. Created the "Other" state for virtual route points whose base routes are not cleared but are also not routed to anything that exists in the virtual router

2. Added Clear Route capability to scene changes (Scene changes to be analyzed for clear route conditions as those will be met and executed by this version)

3. Increased client and server performance for larger systems

4. Fixed a bug in the Chart View of the client that locked the client application when trying to display chart matrixes above 1500 x 1500

5. Reworked the Import function for Virtual Router creation and editing in both the server and the client. The Import function now allows you to pick the rows using intuitive standard windows selection techniques to be imported from the base router. Previously you were forced to import the entire router and then remove the entries you did not want or manually create each virtual entry one at a time. This was extremely cumbersome when the base router being used was large. This update addresses that issue with displayed lists that can be used to select the entries to import using the shift and Cntrl key to import multiple entries.

6. In the client - added buttons next to the source and destination drop down boxes which will pop-up a list of the sources or destination in a table form. This table includes not only name and description columns, but host ip, host name, Axia Channel Number, PFS number, etc. The list is sortable by clicking on the top of any column. Columns may be reordered by selecting the column using the top description, and then clicking and dragging on that bar again (red arrows are displayed to show the move status). Double-clicking an entry is the equivalent of clicking an entry and then clicking select. This drops the entry into the source or destination combo box on the main routing panel so it is ready for a take operation. Holding the Ctrl Key and clicking on a destination type entry will go to that line in the main grid as well. Many clients were asking to be able to see Axia Channel numbers in addition to PFS numbers. This allows this. This screen will also be allowed in the future on other screens that require source and destination selections.

7. Added a Shell Command Action to stacking events. This allows any windows command line command to be run. To run a VBS script, you must invoke the script handler as part of the command - for example the shell command would be: CScript C:\Junk\Test.vbs.

Version 3.60 (Server Only) 1/18/2007 11:39:00 AM

1. Fixed a bug in the clear route function that caused an error message to appear when clearing routes in a main router

2. Fixed a bug in Stack Events Silence Detect that caused erroneous behavior when two stack events tripped off of silence and audio present on the same source or destination respectively.

Version 3.59 (Server Only) 1/12/2007 2:45:00 PM

1. Added hold time parameter to GPIs being sent as part of Prophet ACU translation to allow for Prophet polling

2. Fixed a bug in Stack Events - If the "Run Actions if any qualifier are met" was checked, Actions would only be run if the first qualifier was true, and not is any subsequent ones were true. This has been fixed.

Version 1-03 (SAACU Bridge) 1/8/2007 9:00:00 PM

1. Added logging to the ACU Bridge Application

Version 3.58 (Server and Client) 1/04/2007 9:07:00 AM

1. Fixed a bug where in certain cases a 0.0.0.0 source route could get interpreted as an actual route point rather than a None route

2. Fixed a bug in Silence Detect stack events. Certain left/right disparities and/or clip events could stop and or erroneously trigger the timers. Event is only seen as silent if both left and right are silent.

3. In the Client, double-clicking lines in the source and destination lines in the search results now align the main grid to that point. In the case of a source only, it will bring that source up in the routing drop down box. There is still a little bit of work to do on this in the chart view rather than list view.

4. In the Client, search results line number column is now expandable.

Version 3.57 (Server) 12/03/2006 11:26:00 PM

1. Fixed a bug where in certain cases after an Element reboot, PFS would not re-connect with the VMIX/Profile Change Port 4010.

2. Fixed a bug in Silence Detect stack events. If multiple stack events are monitoring the same source or destination for silence, the Actions were getting tripped more often than they should.

3. Reworked the Name Change screen code to protect names in nodes better. There was an occasional condition that could make the wrong name get pushed to the node.

4. Eliminated Pathfinder's ability to automatically push name and address changes to a node. This was put in Pathfinder Server to make it push changes if a new node replaced a bad one. This was deemed dangerous as it could cause unwanted changes. Also this functionality will be replaced by the Axia management tools under development.

5. If you change the name of a GPIO source or destination in the node, Pathfinder Server was not picking up the changed name. This has been fixed.

6. Stack Event Time based interface did not re-populate the End Date option properly when the event was edited. This has been fixed.

7. Time based Stack Events required a restart of the application to work. This has been fixed.

Version 3.56 (Server, SAACUBridge, SAGenericBridge) 10/22/2006 11:26:00 PM

1. Fixed a bug in the ACU Translator that caused the proper state not to be sent when first starting PFS up with Channels/relays/optos on, until the channels/relays/optos were kicked off and on again

2. Added an option for the ACUTranslator to support the SAACUBridge through event driven changes rather than strictly polling on the TCP side of the bridge

3. Added an option to Translators to allow them to be turned on automatically or to follow the event system for cluster solutions where the translator should only be on on the computer currently owning the event system.

4. Fixed a bug where occasionally ACU Translators after being edited would not restart

5. Created the SAACUBridge application to run on serial computers where it is desirable to convert the ACU serial data to event driven TCP data and allow that communication to roll between cluster nodes with the event system.

6. Created the SAGeneicBridge application to convert serial control data to TCP data and roll the TCP side between multiple cluster nodes with the event system.

7. Added support for the SAPortRouter (not released yet).

Version 3.55 (Server) 10/5/2006 9:50:00 PM

1. Scan function now binds to the correct NIC

2. Cluster update router record refreshes router rather than reinitializes

3. HardwareMaps were getting reinitialized every time a router was updated. This caused some state issues as seen in MPR scripts when ID light got left on.

4. NonTerminal sources should get converted to real sources during a scan if the scan finds a LWRP capable engine responding on those sources

5. Added an "Are You Sure?" message when PatfhinderServer is asked to shut down. However at this point in time the message is modal stopping other application capabilities until it is responded to.

Version 3.53 (Server, Client) 9/4/2006 9:18:00 PM

1. Client was not resubscribing to audio thresholds when it switched from one cluster node to another

2. Increased delay times available in stacking events from 60000ms to months in ms

Version 3.52 (Server, Client, Mini 1.09, PanelDesigner 1.09) 9/3/2006 8:26:00 PM

1. Fixed a bug in the ACU translator configuration screen which made it impossible to remove GPIO closure points from the translator

2. Finished all logging capabilities including logging to Syslog UDP destination

3. Fixed a bug when editing routers that caused multiple copies of hardware connections to be opened

4. Event creation was showing silence detect gui options on final screen no matter which event type was fixed - that has been fixed

Version 3.49 Beta (Server, Client, Mini 1.07, PanelDesigner 1.07) 8/20/2006 8:29:00 PM

1. Added ACU-1 translator with support for VMIX

2. Fixed serial port settings bug when editing a protocol translator with serial port parity other than none

3. Fixed resizing issues of Protocol Translator wizard screen

4. Pathfinder Mini now remembers it's screen position from last startup

5. IF Client Connection to Server Hung but did not disconnect, client was still posting the lost connection and ending rather than trying to reestablish or find new server to which to connect. This is fixed.

6. When LogToFile was enabled, server would create a garbage log file in the root of the PFSServer folder. This has been fixed.

7. Added clustering support for the ACU Table in the Protocol Translator Database.

8. Added additional loss of connection sensing into the inidvidual node modules

9. Fixed log where disconnects were getting logged during inital connect that were not actually disconnects

10. Added additional connection logging code

11. Fixed a bug in the new refresh router function that could cause wrong information and require a reboot of the application

12. Added subscription for silence detect so only those sources and destinations in the current view window of a client, or involved in a stack event, or normal event are subscribed to. Cuts down dramatically on traffic analysis

13. Added AxiaAutoUpdate option which allows the server to automatically add sources and destinations on existing LW devices as they appear. For example when busses are turned on in element they will get added into the matrix if this option is on.

14. All TCP outgoing connections now include heartbeats, TCP Error handlers, and TCP Close Handlers

15. Added NO Change option to User Panel Key State Stack event Qualifer

16. Added \HEX escape characters to user command qualifier and action in Stack Events

17. Serial Port Transators only open when event engine is running

18. ACU Protocol Translator silence detection added

19. VMIX support for fadeup and down times, On/Off, Gain added to scripting engine, SA Protocol Translator, and Stack Events

20. Panel Designer fixed bug when saving file with a different name, was not writing the correct panel name into the hordware map file

21. Added support for DISP object into panel designer hardware map to support the LCD display at the top of a User panel

Version 3.48 Beta (Server) 7/27/2006 8:29:00 PM

1. Fixed a bug in the Database writing for the Pro-Bel General Router Protocol Translator which in some situations was not allowing the router to be used field to get filled in. - Server Only Update.

Version 3.47 Beta (Server) 7/24/2006 11:06:00 PM

This is a beta version of the software.

1. Fixed a bug in the Serial Port implementation of the Pro-Bel General Router Protocol Translator

2. Added support for commands 101, 106, 103, and 107 to Pro-Bel General Router Protocol Translator

3. Foxed Clear Route command in Pro-Bel General Router Protocol Translator

Version 3.46 Beta (Server) 7/24/2006 2:16:00 PM

This is a beta version of the software.

1. Added Pro-Bel General Router Protocol Translator - Only commands 1 through 4 supported at this point in time

Version 3.45 Beta (Server, Client, PathfinderPC Mini 1.05) 7/18/2006 10:05:00 PM

This is a beta version of the software.

1. Fixed a bug in the virtual router creation when early points in the imported list were removed, that caused synchronization with based tables to work incorrectly

2. Fixed a bug where if an Axia Audio router configuration was changed in the server, sometimes some of the nodes would get their destinations all set to the first route point in the PFS list

3. PathfinderPC Client and Mini now both will continue to search through the list of available servers in the cluster continuously until they find one or are shut down. If the client of mini loses connection with the server, it will now try to reacquire that server first then any others in the list rather than shutting down.

4. Completed more logging parameters. Still have some logging parameters that are available in the logging list to complete. Should be finished in next version.

Version 3.43 Beta (Server, Client, Panel Designer 1.06, Pathfinder Mini 1.04) 6/28/2006 3:35:00 PM

This is a beta version of the software.

1. Fixed a bug where Virtual Router Points would start at 0 rather than 1 when first creating the Virtual Router

2. Fixed a bug Virtual Route Point editor in the server would have the cpations Source and Destination Reversed

Version 3.42 Beta (Server, Client, Panel Designer 1.06, Pathfinder Mini 1.04) 6/28/2006 3:00:00 PM

This is a beta version of the software.

1. Fixed a bug where UDP send in protocol translator was not working correctly

2. Fixed a bug where UDP send out parameters would not fit in the field in the protocol translator database

3. Fixed a bug where Panels mapped to Virtual Routers would not update properly

4. Significantly increased speed from receive of route change status to display in client and protocol translator

5. Changed Router numbering so that ID numbers do not get renumbered as routes are added or removed from the list. Furthermore when adding a route the software will check back to the past revision of the database and if the route existed there, try to reuse the same number. This means that the route list may not be contiguous numbering but rather those numbers will act as unique identifiers. This will prevent scene change and protocol translator mappings from getting mis-assigned after route points are added or removed from a router.

6. Modified the first status update request to units on software startup to achieve faster synchronization with the network - less than 10 seconds.

7. Additions and removals from a router of points and Livewire devices should automatically post to the client and become active rather than requiring a reboot of the server application. Some additional testing and modification of this point may still be needed.

8. Fixed a bug where if there where multiple silence detect stack events, anything above the first would also get its timer started whenever the first passed below the threshold causing unpredictable alarms.

9. Added a Default Graphic Path item to the Panel Designer. If pictures are used in a Panel Design the panel will first look for the graphics in that default path location, and if it does not find them there, it will look for them in a PanelGraphics folder within the folder where the application is launched. If they are not found either place, they will not be displayed.

10. Added ButtonOnUpPicture, ButtonOnDownPicture, ButtonOffUpPicture, ButtonOffDownPicture fields in the Panel Designer.

11. Made all of the graphic options listed above for user panels work on both the Pathfinder Client and Pathfinder Mini applications.

12. Changed the PanelDesigner so that right-clicking on an object enters it into a state for dragging and resizing. Left click will allow simulation of the graphic changes listed above from within the designer.

13. Added escape characters to send LineFeed and Carriage Return in user defined commands out the Protocol Translator from stack events.

14. Added a label in the main control panel of the client to show the IO number selected for both Source and Destination.

15. PathfinderPC Client now only updates level graphics in the viewable part of the scroll for increased efficiency

Version 3.39 Beta (Server, Client, Panel Designer Update)

This is a beta version of the software. We are getting close to a final release but still have some known bugs and issues we are working on.

1. MouseUp in the Stack Events User Panel Qualifier fixed

2. Added Logging Gui

3. Added Logging Engine - though not all options in the gui are actually active in the code in this version. That will be fixed in the next version

4. Fixed a memory leak when editing stacking events

5. Memory Qualifier in Stack event did not trigger if the memory option was the only qualifier. This has been fixed

6. Added Element Show Profiles to both the qualifiers and actions in the stack events

7. Panel Designer now writes the hardware map file

8. Fixed Panel Designer Cancel Save

9. Panel Designer warns on exit if panel has changed giving the user a chance to save

10. Save operation with multiple panels opened fixed

11. Fixed the label shift in Panel Designer when clicking on a label

12. Controls in Panel Designer can be copied and pasted

13. \n works for carriage return in label and button captions and stores properly now

14. Panel name now follows filename and vice versa

15. Added scrolling to the chart view in PFClient - still needs some work for the next release

Version 3.35 Beta (Server Update)

This is a beta version of the software

1. Fixed the negation function on memory slots in Stack Events.

2. Added support for GPI commands in SATranslator and Stack Events. GPIs may only be changed in the software driver, not in hardware nodes. SATranslator now has a TriggerGPI command and a TriggerAllDestGPI Command.

Version 3.34 Beta (Server and Client Update)

This is a beta version of the software

1. Fixed an issue in both the client and server to make the GPIO status panels in the client work properly again by right clicking on any GPIO router line in the client.

2. Finished a performance enhancement in the SetMeter functions in the server.

Version 3.33 Beta (Server Update)

This is a beta version of the software

1. Fixed an issue with GPO based stack events where the GPO information would not come back when trying to edit the event and the GPO event would not fire.

2. Produced several performance enhancements for large routing systems by using indexing in certain arrays.

3. Added a Generic Protocol Translator type. In the future this will tie to a text file so that the user can create their own protocol translation rules. For now this allows this will allow unique commands to trigger stack events.

4. Added a Protocol Translator command as a qualifier allowing the user to make any specified command on a protocol translator trigger a stack event.

5. Added a SA Command Action to the protocol translator which will allow an action to be any command in the Software Authority protocol translator protocol.

6. Made the TriggerGPO command work on virtual router destinations that have GPO points mapped to them.

7. Added a command to the Software Authority Protocol Translator Protocol called TriggerAllDestGPO.

o This command will trigger all GPOs to which a specified source (either GPI source in a GPIO router or virtual source) is routed.

o Syntax: TriggerAllDestGPO <RouterNumber> <SourceNumber> <State 'lllll|hhhhh|lhhxxx . . .'> <PulseDuration in Milliseconds>

o Example: TriggerAllDestGPO 2 3 lxxxx 500

o See the SAProtocolTranslatorProtocol document installed with the server for details.

Version 3.32 Beta (Server, Client Update)

This is a beta version of the software

1. In the Server fixed an issue where GPI changes were not getting entered into the memory array above the first 8 in a GPIO router.

2. Produced several performance enhancements for large routing systems.

3. Added the beginning stages of System Logging

o This currently has three levels and may be outputted to a TCP port or a file.

o Care should be used with the Medium and high levels as these are meant strictly for debugging and will probably be changed later. Plus they output a great deal of data and could slow the server down.

o The Low level will output disconnects and reconnects with the nodes making it easier to see if the server is having a problem communicating with the nodes.

o It is advisable to use the port version and capture using Hyperterminal or some telnet capturing program rather than having PFS write to a file as this is slower.

o In the future there will be a log capturing and viewing application and much more useful data will be added to the logging function. Also the format for these logs is still under development so this is just an introduction to this feature

4. Fixed some issues in the User Database Editor

5. Added a backup table when editing a Livewire router system that will automatically initiate a clean rollback in the event that the Livewire edit fails to complete.

6. Added GPIO support to the Software Authority protocol translator to both view GPIO changes and initiate GPO changes

7. Added the ability within the Software Authority Protocol Translator setup to select which routers and thereby limit the routers the translator will display information for.

8. Fixed a bug where the runscript command in the protocol translator would not work if the particular script did not require an additional argument beyond the calling object.

9. In the client Added registry keys which can be used to limit access on the client without requiring a login

o HKLM\Software\Software Authority\PathfinderPC\ACL\

a. FullAccess (0 or 1)

i. This is set to 1 by default when the program starts and this registry key does not exist.

ii. 1 enables full access (according to user login rights if enabled on server)

iii. 0 limits access to the below entries

b. Router_<RouterName> (0 or 1) for deny or allow

c. Panel_<Panel

d. Name> (0 or 1) for deny or allow

e. VirtualRouterEdit (0 or 1) for deny or allow

f. SceneChangeEdit (0 or 1) for deny or allow

g. LevelControlChange (0 or 1) for deny or allow

h. EventEdit (0 or 1) for deny or allow

Version 3.26 Beta (Server, Client update)

This is a beta version of the software

1. In the client fixed the restart so that it brings up last used User Panels

2. In the Server dramatically increased speed of the scripts by caching them so that they do not have to get pulled from the hard drive each time

3. In the Server added support for Includes to the scripting

Version 3.25 Beta (Server, PanelDesigner update)

This is a beta version of the software

1. Added hidden grid for dropping controls in designer

2. Reduced unnecessary traffic between client and server application

Version 3.24 Beta (Client, Server, Mini, PanelDesigner update)

This is a beta version of the software

1. Added storage of the previous route point for each destination into the internal routing memory

2. Added a script command to allow the system to return to the previous route point for any destination. For Livewire routers this will return to the actual previous source stored in the node regardless of whether that source lives in the PFS route list. For standard and virtual routers it will return to the last route in the route list.

3. Fixed a hexi-decimal conversion issue with certain colors picked for panel buttons in both the client application and in Mini

4. Introduced the Panel Designer. The Panel Designer is the alpha version of a graphical designer to design custom button panels. No help is available for this application yet. The application is now automatically installed along with the server application using the server application installation package. The separate installer for the panel designer is for those users who wish to design the panels on a different workstation and then just copy the xml files to the server.

Version 3.23 Beta (Server update)

This is a beta version of the software

1. Found 2 un-trapped socket errors that could cause application crashes.

Version 3.22 Beta (Server update)

This is a beta version of the software

1. Adds support for UDP connections to the Protocol Translator.

Version 3.21 Beta (Client and Server update)

This is a beta version of the software

1. Fixes issues with Panels making duplicate scripting calls under a clustering condition.

2. Adds a Heartbeat to the Clustering to double check activity between the nodes.

Version 3.20 Beta (Client and Server update)

This is a beta version of the software

1. Adds support to run scripts from the protocol translator - undocumented and not in the protocol translator help files yet.

2. Fixes a bug with clustering where an extra cluster node object was being created and interacting with the clustering view making it appear that the connection was connecting and disconnecting repeatedly.

3. Fixes a bug that caused the hardware user panels not to repopulate after an engine was rebooted.

Version 3.19 Beta (Client and Server update)

This is a beta version of the software

1. Fixes a loop created by the fix in version 3.18.

Version 3.18 Beta (Client and Server update)

This is a beta version of the software

1. Fixes a problem where the router creation wizard cannot complete properly if there are blank names for sources or destinations in the nodes. Blank names are not supposed to be allowed in the nodes, so this version of the software pushes a new factory default name to any blank names in the nodes.

Version 3.17 Beta (Client and Server update)

This is a beta version of the software

1. Adds full support for Clustering including data synchronization of database files, Stack Event files, and memory slot and matrix locations. Panels and scripts must still be manually copied as these must be manually created.

Pathfinder Mini Version 1.0 (Alternate Client Application - Requires Server Version 3.16 or later)

This is a beta version of the software

1. Pathfinder Mini is a small application that displays custom user panels. The user panels are XML documents that are dropped inside the PFSPanels folder of Pathfinder server. They allow a designer to create custom button panel to manipulate routes and call scripts for custom logic. The controls in these panels can have their color, text, and other properties dynamically controlled by scripts and stackable events. They can also be mapped directly to a particular route to light when the route is active and cause the route to be activated when the button is pushed. Scripts can be used to create advanced routing logic tied to these panels. The button panels have been available to advanced designers as a window within Pathfinder for some time. Pathfinder Mini provides a small application to run these panels without all of the other features of the Pathfinder Client. This is useful for end user panels where you do not want the end user to see the full interface of Pathfinder Client.

2. A demo file of a Pathfinder User Panel is also available for download as a self extracting exe file. This panel xml file when extracted on the Pathfinder Server gets dropped into the PFPanels folder.

3. The Pathfinder Mini file includes a simple text configuration file where an administrator defines the IP address of the server and the name of the panel from the server to display and use. These configurations are not GUI driven because the idea is that it is to be used for situations where the end user is only supposed to have simplified limited control, and such a GUI would place other panels and properties and the end user's touch.

4. Documentation on the Panel definitions and Scripting language for advance work is still sparse though that will be forthcoming. Contact Dan Bays and [email protected] for more details until such documents have been completed and posted.

Version 3.16 Beta (Client and Server update)

This is a beta version of the software

1. Fixes a GPO Contact closure issue in Stackable Events. Adds several new functions to the scripting engine including GPO sensing and triggering. Adds option in the Stackable events gui to force a run of the actions. Modifies hardware user panel commands in server so that text updates are only sent if they change to increase performance on the Element CAN bus.

Version 3.15 Beta (Client and Server update)

This is a beta version of the software

1. Fixes a memory Leak in version 3.14

Version 3.14 Beta (Client and Server update)

This is a beta version of the software

1. This version finishes Stackable Event support of Audio Events. Stackable Events can now have their qualifers set to be true if all qualifiers are true or if any qualifiers are true. It also adds GPO Trigger to standard silence detect events. Finally it fixes several bugs including a failure of scenes to activate if a User Panel has the focus. Please Note: GPO Pulse settings should remain at 0 until further notice as GPIO units do not seem to be responding to pulse command from LWRP correctly at this point in time.

Version 3.13 Beta (Client and Server update)

This is a beta version of the software

1. This version introduces Stackable Events as well as the ability to map a route point to a panel button in the Panel XML definition.
Please Note: Audio Level Detection in Stackable Events not working properly yet in this version.

Version 3.12 Beta (Client and Server update)

This is a beta version of the software

1. This version is exactly the same as the 3.11 Release version, except with the Clustering tab enabled for Beta sites to be able to start experimenting with Clustering. Clustering users should be aware that this feature is still under development. At this point in time clustering is working, but database synchronization is not complete. Thus the system must be set up and then the databases manually copied from one server to the other. That will be fixed in future releases.

Version 3.11b Release (Client Update Only)

This is a release version of the software

1. Fixed Drop Down Lists losing Sources and Destination Lists When Switching between multiple routers

Version 3.11 Release (Client and Server update)

This is a release version of the software

1. Fixed locks getting stuck on red

2. Fixed slow load time of long lists into combo boxes

3. Clustering Tab Disabled in this version

4. Fixed Chart View bug that made cleared routes still hold the last uncleared state.

Version 3.10 RC (Client and Server update)

This is a maintenance release to fix certain bugs, and not a major feature set release.

1. Release Candidate version 3.10

2. Fixed GPIO Config bugs

3. Fixed GPIO trigger bug with nodes above the first GPIO Node

4. Fixed Locking bug with Scene Changes

5. Cleaned up Event List Viewer and Event Wizards

6. Added Automatic Backup of all critical changes to databases

7. Added Email Alert Support to all Events

8. Fixed Bug with events on repeating daily schedule

Version 3.05 to 3.07n (Client and Server update)

1. Added ChartView, Support for Scripting Engine, User Panel Button Support, GPIO buttons as user button support, multiple fixes and updates

Version 3.0 5(Server update)

1. Scene Events could only add scenes that were named with names less than 16 characters. This has been fixed to allow names up to 251.

Version 3.04 (Client and Server update)

2. Fixed a bug in the edit wizard of the livewire points from the route names screen on the server that prevented destination changes from being stored properly. Also added the description field to this window.

3. Fixed several bugs in the event wizard of both client and server which were causing source lists not to display properly, GPIO events to get stored with no proper contact closure number if stored from the client, and several other user interface issues

4. Modified the TCP/IP receive routines on both server and client to be more elegant and guarantee processing of all commands if multiple commands are included in the same transmission packet

5. Fixed some bugs in the user interface of the virtual router creation and editing wizard. This caused source lists to not display properly in some situations. Also caused naming issues on the grid columns. Also fixed issue with GPIO contacts with no descriptions being added as virtual maps to a virtual point.

Version 3.03 (Server update only)

1. Maintenance Fixes

Version 3.02 (Client and Server update)

1. Fixed a bug that caused the scene creation page to not allow multiple rows to be selected in the grid.

Version 3.01 (Client and Server update)

1. Fixed a bug in the Livewire setup wizard which added incorrect information into the database for Axia Windows driver Sources. This incorrect information was causing routing problems when the user attempted to route an Axia Windows Driver Source.