OpenAVC v0.13.0 - Changelog

OpenAVC 0.13.0 brings child entities: a single controller like an AV-over-IP system, a video matrix, or a multi-zone amplifier can now expose every encoder, decoder, output, zone, or preset as its own controllable entity. It also adds the Video Panel plugin for live H.264 and H.265 video on the panel, moves community drivers and plugins into the data directory so they survive upgrades, and lets macros navigate panel pages.

Child entities

A driver can declare child entity types, and the platform tracks each child as its own addressable unit. A matrix shows up as one device, but each input and output is an entity you can command, bind to a button, and read state from. The same goes for DSP zones, video-wall presets, and AV-over-IP encoders and decoders.
The Programmer adds a Child Entities tab on the device view, with a searchable command picker and one unified filter that spans device state and child entities, so a controller with hundreds of children stays manageable.
Live child state lives under device.<id>.<child_type>.<padded_id>.<property> and every child carries an online flag. Macros, triggers, scripts, and plugins all read and act on child state the same way they do for any device.
Child state relays to the cloud with per-property priority, so latency-sensitive state like video routing goes up quickly while bulk telemetry relays on a slower cadence, and large snapshots are paced so a big controller does not flood the link.
The project file moves to v0.5.0 to store per-child labels and config. Projects upgrade automatically, and projects without controller-style devices are unaffected.

Video Panel

The new Video Panel plugin shows live H.264 and H.265 video on the panel. Point it at an IP camera or another RTSP source and place the stream on a panel page for a confidence monitor, a camera feed, or an overflow display. Streams are set up from a Video Streams panel in the Project view, and you install it from the plugin library once you are on 0.13.0.

Where drivers and plugins live

Community drivers and plugins now live under the data directory, for example /var/lib/openavc on Linux, instead of beside the program files, so they stay intact across upgrades and reinstalls. Existing installs migrate automatically on the first start after the update, on Windows, Linux, Docker, and the Pi image.

Page navigation from macros

A new ui.navigate macro step lets a macro switch the panel to another page, so a single button can run its actions and move the operator to the right screen. It understands $back, which walks back through the page history.

Plugins

Plugins can register their own HTTP routes, ship custom panel elements that appear in the UI Builder, and keep a per-plugin persistent data directory. These are the building blocks behind Video Panel and are available to any community plugin.

Reliability and polish

Discovery pre-fills a driver's default settings when you add a discovered device, so it lands ready to connect.
Faster state handling on large projects, through a state-key prefix index and bulk subscriptions.
Some plugins would not enable on a fresh install, with no feedback from the Enable button. Both are fixed; the missing dependency is bundled, and plugin enable, disable, and settings errors now surface in the Programmer.
Uninstalling a plugin updates the project revision so other open editors notice the change.
Custom plugin panel elements no longer interfere with editing project state and config.