Program Settings

For MxMC, you can choose from various options and set preferences. To do so, open Settings in the MxManagementCenter  > Settings (Mac) or File > Settings (Windows) menu.

Fig. 100: General Settings

Language: Sets the program language. You may have to restart the software in order to apply your change.

Behavior: Deactivate this option to prevent that a double-click triggers the full-screen view on the main monitor or on other monitors.

Display Area: If you are working with the Camera/Group bars or the Alarm/Export bars, you can change the width of the bars. Use this option to automatically resize the display area in such a case.

Graphics Mode: If you want to correct hemispheric images, make sure that this option has been activated. A prerequisite for using this feature is a graphics card with OpenGL V2.1 support, since it performs the actual distortion correction of transferred hemispheric images. Deactivate OpenGL if your graphics card does not support this mode or if you experience problems when displaying the camera images.

Fig. 101: Network

Proxy Server: Select the desired proxy here.

No Proxy, a direct connection will be established.

System Proxy will apply the proxy settings of the system, including the exceptions defined.

Fig. 102: Software Update

MxMC can use the update feature to automatically search for new program versions. To do this, check the Check for Updates checkbox and set the polling interval. The update function requires an Internet connection.

The search for new versions can also be performed manually. To do so, click on Search Now. If a new program version is available, you will see this here.

Fig. 103: Notifications

Alarms: In addition to the event notifications in the Alarm bar or the Alarm Info bar, you can set up an alarm notification and/or alarm sound that signals new alarms. Enable Alarm Notifications to receive an alert. Select the desired alarm sound and set its duration and volume.

Bell: When the bell is rung, a ringing notification is displayed. Select the desired ring tone for the notification and adjust its volume using this option (see Operate Door Stations).

Fig. 104: Monitoring

Lost Connections: If the connection to a camera is lost (e.g., due to a network failure or changed camera access data), the application can show a warning.

This is where you configure the warning. Activate the Lost Connection Detection checkbox and specify how you want MxMC to react if the connection to a camera is lost (warning sound and window).

Action Log: MxMC can log any action, such as starting playback or export actions, activating the sound, etc. This means that you can log all user actions and thus deliver the entire chain of events for legal purposes. Activate the Action Log checkbox and specify the interval at which the action log is to be archived and a new log created. After enabling this feature, you must restart the application for the activation to take effect.

The action log can be accessed from the menu via Window > Action Log.

Application Error Report: After an unexpected program termination, a service report is usually created. If you do not want this, uncheck the Show Dialog checkbox.

 

Fig. 105: Audio

Use the slider to set the sensitivity for recording the sound from the camera microphone. The default setting has been optimized for Intercom connections and should only be touched in very noisy or very quiet door station surroundings.

Hands-Free Talking and Push to Talk
The Hands-Free Talking option is activated by default. If the surroundings are very noisy or if intercom problems persist, you should try to use the Push to Talk option.

Fig. 106: Data Volume

Maximum Number of Events/Maximum Time Range: The number of events and the time range are controlling how far into the past MxMC will look for event information after the next launch of the application. The settings apply to the event counter in Live View and the event preview images in Events View. This avoids long loading times and saves storage space when initially loading the event information.

Fig. 107: Caches

Recording Path Cache Sizes: To improve playback performance, you can set the internal cache sizes for playback here. This applies to both playback via the camera and playback from a file server. Please be aware that the cache size set here will reduce the available RAM for other processes, which in turn can influence the performance of other applications.

Event Images Harddisk Cache: To load event images faster and reduce network load, you can increase the disk cache for event images. If you do not want the system to save event images to disk, clear the Event Images Harddisk Cache checkbox.

Fig. 108: Snapshot Images

You can save individual camera images as snapshot files. These settings control the location and the quality of the snapshot images stored by MxMC. If you do not specify a folder, the files will be created on the desktop.

If you observe a suspicious situation that you want to record, you can start a manual recording in Live view as well as in Grid view. While you keep track of the situation in the live image, the images are recorded and saved as an MXG file. Here you can configure where the clips are stored and how long they are recorded. If you do not specify a folder, an MXG file will be created on the desktop.

Fig. 109: Remote Control

MxMC can be remote-controlled from other programs using HTTP requests. Activate this feature and set a proper port if you want to use this feature. Click on one of the example links to see a list of executable commands.

Fig. 110: Joystick PTZ

You can adapt the joystick behavior to your personal requirements. Start by setting the PTZ type, then set the behavior for each axis.

PTZ Type

Axes

Invert
Use this option to invert the joystick actions for that axis.

Sensitivity
If the PTZ actions are reacting too slowly, you can increase the sensitivity. If the reactions are too fast, reduce the sensitivity.

Progression
Click on the button to change the progression of the joystick movements. The default setting is linear progression.

Fig. 111: MxMessageSystem

This setting is currently required for the MxThinClient. Since the live camera images are switched to the MxThinClient via the MxMessageSystem, you must first activate the MxMessageSystem here. Make sure that the same parameters are set as in the MxThinClient.