Go to documentation repository
Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.
INTELLECT™ provides an opportunity to change the transport protocol used by the IP-device. The following types of protocols can be used:
- TCP-based protocols.
This protocol is reliable; safety and reliability of data delivery is provided when used at the network layer of the operating system. On the other hand, this is its fault: the packet loss will cause re-sending the data. This requires substantial additional resources and time in order to determine the loss and send the data again.
Recommended for use:- In busy networks where serious packet loss are possible (caused by the equipment, communication media, etc.).
- When the integrity of the picture is more important than speed of response (for example, when recording to the archive).
- In the high-bit-rate stream (high fps and resolution, low compression).
- For situations where a delay between the true and the observed picture is more important than the loss of a picture (for example, live video).
- UDP-based protocols.
These protocols are "unreliable", i.e. transport layer does not provide data delievery for them. On the other hand, this protocol provides a fast data transmission and low delay. Also, in case of low losses and high fps the picture is smoother.
Moreover, some UDP protocols, particularly RTP, have packet losses processed at the application layer (i.e., means of application, rather than the OS). This allows using algorithms of adjustment stream width and packet loss processing that are fitted for multimedia transmission. So sometimes these protocols better solve the problem of bad data transmission in networks.
Recommended for use:- In networks with low packet loss (in-door, office network).
- For situations where a delay between the true and the observed picture is more important than the loss of a picture (for example, live video).
- In the high-bit-rate stream (high fps and resolution, low compression).
- In busy networks where serious packet loss are possible (because of the equipment, communication media, etc.).
- When the integrity of the picture is more important than speed of response (for example, when recording to the archive).
Note.
INTELLECT™ does not support IP devices over https protocol.
In order to change the transport protocols for IP device, add the following key to the registry:
- Path: HKEY_LOCAL_MACHINE \SOFTWARE\ITV\Intellect\Video\TransportProtocols (for 64-bit system the path is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ITV\Intellect\Video\TransportProtocols). If the path does not exist, then create the corresponding section.
Key name: <Driver name>. The driver name, not the name of the IP-device vendor, is used as name of the key. Name of the driver is included in the name of the corresponding ipd-file which is located in the installation directory of Drivers Pack (for example, the file C:\Program Files\Common Files\AxxonSoft\Ipint.DriverPack\3.0.0\Ipint.Axis.ipd for Axis devices). In most cases, the driver name matches the name of the IP-device vendor. To clarify the driver name for the desired vendor contact AxxonSoft technical support.
Note.
If IP-device is connected via RTSP, use the name of the key "RTSP" without quotes, the value is case sensitive.Value: <protocol>. For example, "http" (TCP-based) or "tftp" (UDP-based) for ArecontVision, "tcp" or "udp" for Axis. The key value is case sensitive.
Note.
For some Axis devices it is possible to enable multicast in the device. The IP-device will be the source of broadcasting. Set the “multicast” value to the Axis parameter to enable broadcasting. On the moment of document writing this feature is supported by the following models of Axis cameras: 243SA, 243Q, 241Q, 232D+, 225FD, 221, 216FD and 211A.- Key type: string value.