Best Approach for Milestone Integration with Third Party Analytics like FRS, ANPR, Video Analytics

MIP
, , , ,
1

Dear Team,

I would like to know what is the most recommended approach for using proxy streams of Milestone added Cameras in our analytics application. The scope of integration would not just be restricted to live streams but also to perform some analytics like Face Recognition on the recorded data within Milestone so we would also need to access the playback streams.

Based on the MIP SDK documentation, we have found the Milestone Directshow Filter to be a decent integration approach but we have the following concerns:

  1. Will this integration work for all OEM Milestone products, since we have a product which is an OEM of Milestone, we were specifically interested in knowing this. Practically, we have found the MilestoneDX://ip_address:80 URL format to work with our OEM product but the observations have been inconsistent since it fails at times.
  2. By using MilestoneDX://ip_address:80 URL, we understand that we will be fetching the uncompressed streams which is good for analytics applications but would again have an adverse impact on bandwidth.
  3. This method of integration will require the user to perform an addition installation of Milestone Directshow filter on the recording and management servers, which is cumbersome and also not preferred for OEM products where Milestone is at the backseat as far as branding is concerned. Installing this filter will also make the user realize the internals of the OEM product.

Another method of accessing proxy streams that we have seen, but failed to get any success with is using the milestone://ip_address:7563 URL format. Could you please share some documentation related to using the same as I was unable to find it. Also, how does it compare to the Milestone Directshow method (MilestoneDX://).

Awaiting your suggestion and response.

Regards,

Saurabh Gandhi

2

I would recommend using our toolkits for handling protocol and decoding. (When executing on a Windows OS).

It produces a much better performance than DirectShow filter, and will utilize GPU for decoding – if available in CPU (Intel Q-Sync).

You can utilize the Toolkit via C# and C++.

As for your questions: (Only relevant if you chose to NOT use toolkit)

Re 1) as far as I know DirectShow will work for all products, IPv4 only – if you see errors, please create a support case (Also – not always on :80 !! )

Re 2) Decoding should be done on the client side, this is the default

Re 3) No, DirectShow filter is installed where you execute your analytics (not on the recorder or management server)

The directshow filter are using the connection on port 7563, as you indicate (ImageServer interface).

This interface use documented under protocols, called ImageServer interface.