How it works
Specifically, the XProtect VMS and MIP SDK have been extended with a ‘Video Processing Service’ driver, and a toolkit and sample code for building a Video Processing Service that can load the GStreamer libraries and configure the source and sink functions. Furthermore, the MIP SDK’s Video Processing Service driver also supports that the outcome of the video processing done in the GStreamer framework optionally can be returned to the XProtect VMS as a modified video stream and/or metadata stream.
This could for instance be a video stream where the brightness, contrast or colors have been enhanced, objects have been blurred or masked out, or the video simply have been transcoded to another video codec, resolution, framerate or bitrate. The separate metadata stream can for instance contain information about the detected objects or other information delivered by the 3rd party application.
For video processing integrations that do not use the GStreamer framework, the MIP SDK furthermore contain documentation and samples for building an ASP.NET Core based video processing service.