I would like to know the TI-recommended best-practice way to connect a VISS and AEWB TIOVX nodes. In J784S4 SDK, as far as I can tell none of the Vision Apps demos actually connect the AEWB node's output to the VISS node's input (ae_awb_result).
Presumably, one cannot simply assign the same reference object to both node parameters, as that would create a circle in the OpenVX graph, so naturally we would use vx_delay. This is actually done in a TI test program.
However, TIOVX does not support vx_delay for safety-critical applications. The documentation warns delay objects are not supported with pipelining (here, and here). This is apparently a known issue that will not be fixed.
I understand there is a proposed workaround using graph parameter, but I would like to know if there is a standard implementation example from TI, as it is a core part of TI's offering.
For example, the Single Camera VPAC Application Vision Apps demo diagram shows the "AWB Gains", but in the code the tivxVpacVissNode parameter ae_awb_result is initialized as NULL.