Unclear point about "Isolate Camera in its own driver proces"

MIP
, , ,
1

Below you will find an explanation about: Isolate a camera in its own driver process.

Everything is clear except this part:

“Create a new configuration file %PROGRAMDATA%\Milestone\Milestone Surveillance\DeviceProxy.ini”

1. A new file must be created with the following name: DeviceProxy.ini. Is this right?

2. Where should this file be saved?

Important to mention: I use Xprotect corporate package

  • May 11, 2015
  • ·
  • Like
  • 2

Summary

Since the 2013 release of XProtect© Enterprise (version 8.5), the system uses what is called a device proxy to camera drivers.By default, there is one proxy process per camera driver, meaning tha…

Information

Article Details

Article Number: 000001805

Version: 2

Audience: Advanced

First Published: 2015-4-7

Last Modified: 2015-5-11

Symptoms

Since the 2013 release of XProtect© Enterprise (version 8.5), the system uses what is called a device proxy to camera drivers.

By default, there is one proxy process per camera driver, meaning that all cameras using the same driver are run in a common proxy process. This has the undesired side-effect that one problematic camera can affect many other cameras (using the same driver) when the proxy process for this camera needs to be restarted.

On the other hand, having a great variety of cameras on one recording server means that there is a high number of proxy processes, which potentially causes a high memory consumption.

Resolution

This solution describes both how to:

  • isolate a camera so that it runs in its own proxy process (for debugging purpose)
  • and
  • join different drivers in a common proxy process (for reducing memory consumption)
  1. **Solution:**Create a new configuration file %PROGRAMDATA%\Milestone\Milestone Surveillance\DeviceProxy.ini
  2. To isolate a camera in its own proxy process, create a section like this in the configuration file:
  3. [ProxyServerName]
  4. <camera_IP>:0:0 = <instance_name>
  5. Example:
  6. [ProxyServerName]
  7. 10.100.50.99:0:0 = AxisOnTheTable
  8. To join cameras with different drivers in one common proxy process, create a section similar to this:
  9. [ProxyServerName]
  10. .dll = <common_instance_name>
  11. .dll = <common_instance_name>
  12. Example
  13. \[ProxyServerName\]
  14. Axis214.dll = AxisProxy
  15. Axis210.dll = AxisProxy
  16. To make the changes take effect, restart the recording server.
2

This is what the knowledge base article says about file name and location:

%PROGRAMDATA%\Milestone\Milestone Surveillance\DeviceProxy.ini

(%PROGRAMDATA% is “[C:\ProgramData](file:C:/ProgramData)”, you can wirite %PROGRAMDATA% in the address-bar in Windows Explorer, “[C:\ProgramData](file:C:/ProgramData)” is a hidden folder.)

If you have further questions on this knowledge base article ( https://force.milestonesys.com/support/articles/en_US/Troubleshootings/Isolate-a-camera-in-its-own-driver-process ) ask the Support Community. - https://force.milestonesys.com/support/MccSupportCommunity