Polaris Vega Device - CRC Error upon Averaging Feature Activation on the Device about pluslib HOT 17 OPEN

I think it is both an expected feature, and a bug, as we have not experimented with any hardware averaging from the Vega. Any configuration variables will be strictly related to the software averaging feature of Plus.

I will explore the hardware averaging of the Vega and see what I can do.

from pluslib.

Hi Adam,
Thanks for the reply.
I suppose that when activating the average feature on the device, the message is modified and that is why it gives the error. Let me know if I can help with the development in some way, although I am not familiar with either the library or the tracker messages.

from pluslib.

To confirm, this is with a Vega XT? I'll go see if we have one, the one I am working with is a Vega

from pluslib.

We do not have an XT. We do have an ST and VT, is this feature available on either of those?

from pluslib.

I have followed your steps, but I don't get an error. However, I noticed that when I go back to NDI Configure after connecting to the device, Data Averaging Depth has been reset to 1

from pluslib.

I have found this in the NDI documentation:

API Revision G.003.006 introduced the concept of data averaging.
Data averaging is available only in combination with the command BX2. If data averaging is enabled
and the command BX or TX is issued, the command returns an error code.

We do not currently support BX2, but I'll work on it

from pluslib.

I am using a Polaris Vega XT with the Firmware Revision 010 (Package 010.017).
I have found this in the documentation regarding different devices:

Data averaging is available for all Vega and Lyra systems, but is most useful on Vega XT
because of the higher frame rate achievable.

from pluslib.

I have support for enabling data averaging and BX2 support, but when I turn on data averaging I get majority timeout responses from BX2 command (which doesn't happen without). Investigating

from pluslib.