For the complete documentation index, see llms.txt. This page is also available as Markdown.

HOLOPLOT OS 2.5.2

We're excited to announce HOLOPLOT OS 2.5.2. This release introduces Show Mode in HOLOPLOT Control, overhauls the communication backend for scalable performance in large systems, and adds a range of Processor reliability improvements and bug fixes.

The Public System API has been updated to v1.6.0.


What's New

Show Mode

Show Mode adds function locking to HOLOPLOT Control, protecting the system from accidental changes during an ongoing show.

Scalable communication backend

The protocols and backend architecture for HOLOPLOT Control have been overhauled to focus on scalable performance in large systems with a vast number of modules and beams.

Extended AutoChecker v2

New automated health checks help validate your system:

  • Module Configuration Health Check

  • Driver Health Check


Improvements

HOLOPLOT Control

  • Redesigned the Network Settings view for easier navigation and better responsiveness on small screens

  • Additional frontend performance improvements

  • Improved the reliability of module status reporting, including the Module Configuration Health Check

System Backend

  • Reduced the overall load on the communication cluster by optimizing client subscriptions

  • Improved throughput by sending updates to the frontend in batches

  • Updated the internal messaging layer for improved stability and performance

HOLOPLOT Processor

  • Improved audio stream recovery to maintain consistent latency after CPU overload events

  • Improved hardware health monitoring to prevent false fan and power-supply alerts


Bug Fixes

HOLOPLOT Control

  • Fixed incorrect module state information shown in the Pairing View, caused by the neighbor detection algorithm

  • Fixed the active preset not being displayed correctly after canceling a preset change

HOLOPLOT Processor

  • Fixed automatic failover events not being recorded correctly in the Event Log

  • Fixed an issue that could cause processing overruns following network disconnects


Known Issues

The following issues are known and will be addressed in an upcoming release.

  1. Control link temporarily reported as "Unknown" after a network disconnect

    When the active control network connection (primary or secondary) to an audio module is disconnected, the module may temporarily (up to 60 seconds) report its control link state as "Unknown" until it re-establishes communication over the secondary control network link. During this transition, the connection between HOLOPLOT Control and the module may be interrupted.

    Audio playback continues uninterrupted.

  2. Inconsistent pairing and power status display

    In rare cases, the Devices and Module Pairing pages in HOLOPLOT Control may display inconsistent module pairing and power status — showing modules as unpaired and sleeping while they are actually offline or removed.

Last updated