ACAP version 4.13 is released and is compatible with AXIS OS 11.9.

One of the standout features of this release is the comeback of Parameter API (AXParameter). This was available in ACAP version 3 and is now back in version 4 thanks to your valuable feedback. If you have applications that couldn't make the jump to ACAP version 4, now they can. If you're new to this API, it's handy for saving application settings that are persisted after an application restart, update, or AXIS OS upgrade. Plus, you can use the API to read parameters of the device itself, like the serial number.

We're also excited to introduce the Metadata Broker API (in beta). This API lets you build applications that can easily access analytics metadata of detected objects in the scene. This is going to be a game-changer for any application that relies on scene metadata and analytics.

We have more API news. After a breaking change in beta, we've promoted VAPIX access for ACAP applications into General Availability (GA). That means you can now use it with full confidence in production.

We've been working hard on documentation too. We've added a new section to the ACAP documentation called "Computer vision on device". This offers more insight into the computer vision capabilities and subtleties of different Axis devices. We've also put together a guide on how to run YOLOv5 on ARTPEC-8. And we've updated the instructions for setting up Visual Studio Code to include manifest schema validation.  

We've added new features to the manifest schema as well. You can find all the details about these additions, and the full scope of the release, in the release notes. Happy developing!

For the complete set of code examples, visit our GitHub organization where the ACAP examples are pinned at the top of the page. If you have questions or bug reports related to the examples, please report them in the issue tracker for the specific repository.