OpenVX 1.3.2 Released: More Precise Errors, Better Consistency, and Groundwork for 2.0

Khronos has released OpenVX 1.3.2, a focused update to the royalty-free vision-processing standard that leans hard into clearer failures and cleaner implementation rules. For teams building graph-based image pipelines, the practical win is faster debugging and fewer portability surprises when code moves between vendors or hardware targets.

The biggest developer-facing changes are the new VX_ERROR_TIMEOUT and VX_ERROR_GRAPH_NOT_VERIFIED codes, which make runtime and setup failures easier to diagnose. OpenVX 1.3.2 also adds VX_DF_IMAGE_RGBA support, improves 1-bit U1 image handling, broadens virtual object array support, and allows user-defined structures in vx_scalar.

Consistency work runs through the whole release. Read-only attributes now consistently return VX_ERROR_NOT_SUPPORTED, allocation failures map to VX_ERROR_NO_MEMORY, and the spec replaces vague wording with “implementation-defined” to better spell out what vendors must document. That should help both engine teams and hardware partners avoid edge-case mismatches.

Khronos says the sample implementation and conformance suite have been updated as well, including fixes for community-reported issues. The release is incremental, but it also lays groundwork for OpenVX 2.0, which is expected by the end of 2026 and will extend the model toward radar, ultrasonic, and other accelerated sensor workloads.