Instruction manual

92
8 Notes
8.1 DVR management
8.1.1 DVR connection & Nethunter ports limitation
Due to memory limitation, NHServer is not able to connect unlimited dvrs. Each dvr model has different memory
requirements. Ask for help to your Mitsubishi distributor to manage more than around 100 dvrs.
8.1.2 On-Demand connection & disconnection
All the DVR requests that are different from Live are undertaken on-demand when any client requests them.
Special operations (PTZ, remote configuration, play) will connect and disconnect extra DVR ports on-demand.
8.1.3 Get Events not available for old DVR models
Due to DVR SDK limitations it is not possible to synchronize alarm events with the old DVR models (Models that are
not supported: DX-NT400E, DX-NT430E, DX-TL950E, and DX-TL2500E)
8.1.4 Disconnection effect: frozen images
During DVR ports disconnection, Nethunter server display capabilities will have a “frozen” effect. All the connected
clients displaying video could observe videos are stopped for few seconds.
8.1.5 Decompression CPU: discarding images
DVR video decompression (live) is a high CPU usage operation.
When viewing multiple DVR cameras together at the same client, the CPU consumption could be close to 100%. At
this time, to be able to display all the cameras in a reasonable time and ensure client interface response time,
Nethunter will start discarding images by decreasing the display frame-rate.
To minimize this effect, it is possible to reduce the DVR camera quality settings and also the client decompression
settings to a lower quality.
8.1.6 Visual defects in TL304/304EX/308/5716
Images with sudden changes might show some visual defects (horizontal lines). This only happens when picture
size in recording settings is set to CIF or 4CIF
8.2 Client-Server
8.2.1 Server disconnection
If the connection with server is lost (network issue, server shutdown …) all the affected clients will be informed
about the connection failure. To connect again with the server, Nethunter client needs to be closed and started
again to start a new connection with the server.
8.2.2 Settings administration
Once a client connects to settings screen, all the client extra monitors screens will become blank in order to help
the administrator to change the settings as appropriate, avoiding synchronization issues between screen
components and new or deleted objects.
To update the devices section all clients need to be locked in order to apply correctly the recently changed settings,
parameters, new devices or removed devices. This will simplify the device changes synchronization to all the clients
immediately after the settings operation. During the settings operation time all the clients will be “locked” until the
device control is released.