CM RT Vebox parameters serializing

[mzolotarov]

The C for Media (Metal) Runtime provides the Vebox interface (CmVebox) with parameters passing as a CmBufferUP object. It's not clear how to convert from (assumedly) CM_VEBOX_PARAM_G10 to memory buffer correctly (for further feeding this to device->CreateBufferUP() and vebox->SetParam() accordingly). An attempt to copy the CM_VEBOX_PARAM_G10 structure instance memory as it is (contains pointers!) leads to a GPU hang / vecs0 resetting on reading the output surface.

i915 0000:00:02.0: [drm] GPU HANG: ecode 12:8:2cff3ffc, in cm-test [5023]

A working CM RT example with Vebox is very appreciated, as it's a part of the official API.

[AthiraM_Intel]

Hi,

Thanks you for posting in Intel communities.

This forum primarily focuses on issues related to Intel Media SDK and oneVPL.

Could you please let us know whether you are using Media SDK or oneVPL?

Thanks.

[mzolotarov]

CM RT is a part of Intel Media.

https://github.com/intel/media-driver/tree/master/cmrtlib

The community is called Visual Computing / Media. Please suggest another community thread where computer vision with Intel Media driver is appropriate to discuss.

[mzolotarov · Accepted solution]

Responded on the GitHub: CM RT will be dropped. Resolved.

[AthiraM_Intel]

Hi,

Glad to know that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Thanks.