GBD codec type for h.264 has a different bit pattern when privacy mask is used

MIP
, , ,
1

Using XProtect Professional+. I am getting an unexpected codec type in the GBD header - 0x0D0A for h.264 when a privacy mask is being used. Our current code expects 0x000A for h.264 codec as described here:

https://doc.developer.milestonesys.com/html/MIPGenericByteData/addtl_sub_formats.html

Is there something that should be done when handling streams with privacy mask?

I did some experiments and if the Connect Request includes

yes

…

then the codec type is returned as expected, i.e. 0x000A.

In that case. is there a way to check for the presence of privacy mask for a camera for a particular time frame, or alternately is it safe to pass yes even if the camera does not support it?

Thank you very much in advance.

2

Hi Ruslan,

When you add a privacy mask to a stream then the stream will have to be transcoded to JPEG to impose the privacy mask. So H264/H265..whatevercodec will become JPEG once you get the image with the privacy mask.

3

Hi Artur,

Happy New Year! Thank you very much!

I am able to receive H.264 stream when passing in yes as part of the request, and it shows the image properly, i.e. only the region not covered by the privacy mask, which is acceptable.

My question is if it’s legal to pass yes for camera streams that do not include a privacy mask.

Thanks,

Ruslan

4

Hi Ruslan,

Thank you and Happy New Year to you too :slight_smile: .. and yes it is legal to pass privacymask>yes< even if the camera doesnt have one, then it will just not send any privacy mask :slight_smile:

5

Thank you, Artur