2.0.x

Warning:

Version 2.0 of Pathfinder is undergoing Beta testing. If you would like to be a beta tester - please contact support. It will require a 2.0 key 9 license before you can update to 2.0. It is very important to understand that while all configurations from Pathfinder 1.10.x work in 2.0, changes in 2.0 are often not downgrade-able to previous versions of PathfinderCore PRO. Also note that this document is also in beta form and still undergoing revisions.

Version 2.0.0 11/01/2026 - TBD

• Release links not available until release

• Beta testers - Find links in Beta Documentation - note: beta testing 2.0 requires a Key9 license upgrade.  Contact support if you wish to beta test 2.0.

Pathfinder Core PRO 2.0 is the first major release since 1.10. It includes everything from the pre-2.0 beta work, a redesigned web interface, a new Panel Designer and Logic Flows editor, and Key9 as the only licensing model. The changes below are implemented since 1.10.13.

Web Interface

• New dark design. All pages use the Telos dark theme, with consistent buttons, tables, forms and dialogs.

• Grouped navigation. The menu is organized into Automation, Devices, Messaging, Routing and Audio, and System. Each section collapses, the whole menu can be hidden for more room, and "Expand all menus" keeps every section open.

• System Status dashboard. Cards for system status, live CPU, RAM and Ethernet trends, network, clustering, bank control, services, time, version and licensing. Most cards link to their settings page. You can drag the cards into your own order.

• Services at a glance. Each service is a green or red block, now including the EngineCore router and licensing services. A warning about stopped services appears on every page.

• In-page dialogs and editors. Confirmations and messages appear inside the page instead of in browser pop-ups. The editors for memory slots, email messages, log writers, device emulators and audio alarms open over their list.

• Bulk actions. Select several rows to delete user panels, backups or memory slots at once, or to clone user panels.

• Connection banner. A banner appears when the browser loses its live connection to the system, and again when the connection is restored.

• UI Options. Set the banner color, the banner text color and custom banner text, and choose whether the hostname appears in the banner and the browser tab. This makes main and backup units easy to tell apart.

• Large systems and proxies. List pages stay responsive with thousands of entries, IP addresses sort numerically, and the interface works behind a reverse proxy or under a sub-path.

Logic Flows

• Redesigned editor. Flows are drawn as cards wired port to port. Each combiner's shape shows its logic type, and every start and end card shows its live value.

• Free layout. Drag cards, whole flows or a lasso selection, with snap and auto-arrange. Positions are stored on the server, so everyone sees the same layout.

• Shared links. When flows write and read the same object, such as a memory slot, a labeled link joins them across flows and folders. Selecting the link highlights everything that uses that object.

• Live activity console. Counts of broken, licensed-out, disabled and healthy elements, above a live, filterable list of value changes. Wires pulse as values change.

• Inspector, search, undo and zoom. Selecting a card shows its settings in the Inspector. Search dims everything that doesn't match. Undo and redo reach back to the last Apply. Zoom runs from 25% to 400%.

• FIFO processing. The new Use FIFO Queue option on translators and combiners processes every input change in order instead of only the latest one. This prevents rare out-of-order results.

• Delay bypass values. Inputs matching a delay combiner's bypass values pass straight through without the delay.

• Panel binding flows. Panel-generated flows have recursion detection and execution limits. A flow disabled by recursion can be re-enabled from the panel designer.

• Folder copy keeps settings. Copying a logic flow folder now keeps each flow's execution limit, recursion check, FIFO and startup options.

Block Execution

• Pause parts of the system while it keeps running. Use it for maintenance, testing or troubleshooting.

• Inherit, Block or Override. Set any logic flow folder, scene, property group, router, timer, user panel or panel page to Block. Items below it are blocked too, unless they are set to Override.

• One place to manage it. A Block Execution dialog on the System Configuration page shows the tree of managers and items. Blocked items show in red across the interface.

• Scriptable. BlockExecution is an ordinary property, so a scene, a panel button or the API can block or unblock items.

User Panels

• New Panel Designer. A control palette and layers on the left, the canvas with page tabs in the center, and an Inspector on the right.

• Faster building.

  • Snapping, smart guides, alignment, distribution, size matching and a tidy-grid command.

  • Grouping, layers, cut, copy and paste, and undo and redo.

  • Editing several controls at once in the Inspector.

• Bindings drawer. Bind properties from a side drawer, with searchable pickers for audio sources and destinations, routers, gain controls, calendar resources and hardware buttons. View Bindings lists every binding on a page.

• Autosave and recovery. The designer saves drafts in the browser and offers to recover them. It also has Preview and a "Jump to element" search.

• Button aliases. A control can hold several aliases, each with its own properties and bindings, chosen at run time. Hardware buttons follow the active alias.

• New controls. A latching button, a line control with rotation, and pickers for images and web pages.

• Custom themes. Create, edit, clone and delete themes. A binding can switch a panel's theme while it runs.

• Export and import. Export a panel, with its pages, images and themes, to a file and import it on another system. You choose how name clashes and bindings are handled.

• Blocked panels in red. Execution-blocked panels and pages are shown in red in the list and in the designer.

• Compatibility. Panels saved in 2.0 can't be opened by 1.x.

Memory Slots

• Array memory slots. A new type that holds member slots of any type, including nested arrays. Subscribing to the array delivers every member, and the list shows arrays as an expandable tree.

• Numeric operations. Numeric slots gain write-only Round, Floor, Ceiling, Multiply, Divide and DivideRound properties.

• Current and startup values. The startup value can now be changed, and the current value can be set from the list without changing it.

• Clone and bulk delete from the list, plus a tidier editor and faster changes on large systems.

Scenes

• Authoritative scenes. A scene can keep reasserting its values, with a retry interval.

• Read-only scenes. These can't be activated or edited from the interface, logic or API.

• Item mutability. Each item is read-only, read/write or write-only. This decides whether the item executes on activation and whether it counts toward IsActive.

• Disable items and change values. Individual items can be disabled without deleting them, and logic can change an item's value with ChangeValue.

• Execution limits on scenes.

Property Groups

• Object groups. Pick object paths and properties, and Pathfinder creates and maintains a redundancy or synchronization subgroup for each matching object. View Subgroups shows their live state.

• Disable groups and items. A disabled group stops working, and disabled items are left out of the group's logic.

• Execution limits on property groups and synchronization masters.

Routers

• Several Axia audio routers. Split audio sources and destinations between routers by IP range, using Auto Insert Limits. Axia GPIO routers support limits too, and audio alarms and panel pickers let you choose the router.

• Object routing. SAP property routers can route whole objects, such as vMix sub-objects, with object clear values.

• Router commands.

  • ExecutePattern makes routes by pattern (ClearAll, LeftToRight, OneToAll, LastToAll).

  • LockUserAll and UnlockUserAll lock or unlock a whole router.

  • PulseAllSources and PulseOnMount re-send source values, on demand or when the router finishes starting.

• Clear values follow changes. A cleared destination re-sends its clear value when logic changes that value.

• Blocked routers. A router blocked by Block Execution refuses route changes and is marked in red. Each router's tables now keep their own filter and sort.

Devices and Emulators

• REST API authentication with JWT. REST API devices support static or dynamically fetched bearer tokens, with header or body placement, including Triton Station Manager.

• Fewer false "device offline" events. Poll timeouts now measure real activity and allow for load during startup, cluster sync and failover. New diagnostics show suspected and confirmed timeouts.

• More reliable connections. The reconnect logic has been reworked. A device reports logged in only once all of its connections are, and the Recycle button now also resets the device's meter connections.

• Quasar Vmix inputs. The Quasar's AUX SEND 5–8 and TALKBACK can be selected as Vmix inputs.

• Device emulator handshake. TCP client emulators can wait for a success reply, with wait times, and reconnect if it doesn't arrive. A new Recycle button restarts an emulator's connection.

• Node emulator port. The node emulator can listen for LWRP on a port other than 93.

Audio Alarms and Vmix Control

• Per-IO alarm thresholds. Silence and clip levels can be overridden for each audio IO. Every other IO follows the system-wide setting.

• Redesigned Vmix Control.

  • A five-strip mixing surface with a master strip, scaled to fit the window.

  • Combined fader and meter bars, faders that only move by their grip, and fade-up and fade-down times.

  • A connection indicator.

• Internal and external Vmix sources. Each input can take an external Livewire source or one of the engine's own internal sources, such as a program, record or phone bus, or an aux send. The fader locks while an internal source is in use.

Clusters

• Node cards. Each node is a card showing its state, whether it runs the event system, certificate trust (with a link to review a failure) and sync progress. Floating IPs have their own panel.

• Override Primary. Choose which node runs the event system. A floating IP can follow that choice with Host priority follows cluster.

• Backup license grace. A backup node's inherited license is enforced for 90 days, with a warning at 60 days and an error at 80. A node that leaves the cluster falls back to its own license.

• Cluster-wide Block Execution. See Block Execution above.

Users and Security

• Security Groups. Rights (administrator, route locking, menus and allowed APIs) are now set on named groups, and each user belongs to a group. Upgraded systems keep each user's existing rights.

• LDAP and Active Directory groups. A directory group maps directly to a security group of the same name, so placeholder users are no longer needed.

• Emergency Access. Users marked for Emergency Access can log in at /emergency/ with their local password when LDAP or Active Directory is unavailable.

• Safeguards. Changes that would leave no administrator are refused, and user names that differ only by letter case are rejected.

• Smaller improvements.

  • IP white list entries can have a description.

  • A failed LDAP test shows the real reason.

  • Factory default clears users and groups.

• TLS hardening. TLS 1.0 and 1.1 are disabled, and each unit gets its own certificate export password.

Logs

• One row per log. Rotated files are grouped under their log, with View, Tail, Download and Delete/Clear for each.

• Live tail. Watch new lines arrive as they are written.

• Search across logs. Multiple criteria, regular expressions and context lines, within a time range shown as a histogram. Searches can be saved, and saved searches show how many new matches there are.

• Summary and timeline. The summary lists the most repeated problems, dropped devices and service restarts. The timeline shows every log's entries around any moment.

• Benign marks. Expected warnings can be marked benign so the error counts show only what needs attention. Error and warning counts step you through each entry.

• Support bundle. One click saves the logs for a time range, with a summary, to send to Telos support. Keys are removed.

Backups

• Retention policies. Remove old backups automatically by age, by file name, or both, with exclusions for backups that must be kept.

• Automatic backups. Take backups on an hourly, daily, weekly or monthly schedule.

• Redesigned dialogs. Create, upload and restore have been redesigned, including drag-and-drop upload and a clear choice of what to restore.

• Certificates included. Backups now include the web server certificate and trusted root certificates.

System and Network

• Static routes. Add and remove static IP routes from the Configuration page.

• Net Tools. Run ping, netstat, nslookup, traceroute and telnet from the unit, in the browser.

• Readable Advanced Options. Options are grouped by area, show their defaults and mark changed values. The plain-text editor is still available.

• Bank Control and updates. Each software bank is a card, and Restart is enabled only after you select the other bank. The update upload page shows its progress.

Licensing

• Key9 only. Key9 licensing arrived in 1.10.12. 2.0 uses Key9 license keys and no longer uses the legacy license files. A unit moves to 2.0 by updating to 1.10.12 or later and adding its Key9 license there first.

• License server status. Every configured license server is checked, and each is shown as connected or not.

• Offline activation is offered only on hardware units, where it applies.

• Factory licensing. New units can leave manufacturing with their license installed, ready to activate on first use.

Container

• Production container. Pathfinder Core PRO can run as a Docker container on a Linux host. The image is based on Ubuntu 24.04, includes EngineCore and Key9 licensing, and keeps configuration, backups and logs in persistent storage.

• Host or bridge networking. Host networking supports Livewire. With bridge networking the ports can be moved, and the Livewire and office interfaces can be named.

• Certificates and LDAP. The container can supply its own web certificate, rebuilds trusted root certificates at start, and supports LDAP over TLS.

• Container-aware interface. Network, time, Bank Control and Upload Update pages are hidden because the host manages them. Status shows the container's own uptime and resources, and a restart recycles the container.

SAPv2 API

• SET across many objects. A SET with $MAX_DEPTH changes the property on every matching object below the path. For example, one command can turn off every GPO.

• $SETID. Tag a SET request, and the same ID comes back on the resulting change. This suits synchronization tools.

• New properties for every feature above, including BlockExecution, UseFifo, array slots, scene mutability, router pulse and pattern commands, and per-server license status.

Reliability and Performance

• Faster logic startup on large systems, and no more startup hang on systems without flows.

• Lighter memory slot changes on systems with many slots.

• Watchdog. Restart escalation resets once the system proves stable.

• Cluster licensing fixes. A backup node that starts before the primary now loads its devices, and a restarting primary no longer tells its backups they have no license.

• Robustness. A dropped browser connection can no longer crash the core service, and log delete and clear work again.