Mobile Cameras and Matrixes Control ^ ^  BACK  TO API MAIN PAGE ^ ^
 

In order to control the mobile cameras and matrixes connected to remote VisorNet equipment, the VisorNet API software needs the module corresponding to each type of camera and/or matrix, from which the necessary data frames are obtained in order to remotely control these devices. Each module contains the implementation of the communication protocol with the corresponding device (camera or matrix). The VisorNet API defines a series of operations so that any developer can develop these modules (dll - Dynamic Link Library) and install them in the system. During development, these modules must comply with the general construction rules for dlls and the exportation of functions and there are no further considerations in this respect. In the examples provided for each function the developer can find help in order to develop his protocol using these functions.

 

Changes in version 6.0.0 ^ ^  BACK  TO API MAIN PAGE ^ ^
 

This version includes two main changes in its internal operation that imply some modifications in the API's interface with the application.
The first change is the internal use of QuickTime to receive live video from the VisorNets, what allows the use of new video codifications, such as MPEG4, and to use HTTP as a transport for streaming, what allows most users behind firewalls to receive video streams.
This means that it is necessary to install QuickTime 6.0 or higher in order for the API to work, although its usage is internal in the API and it is transparent for the user, who will not have to use the QuickTime Player or Plug-in to access any functionality of the API.
The last version of QuickTime Player can be found at www.apple.com/quicktime/download. The QuickTime components needed by the API are QuickTime Essentials and QuickTime Authoring.

The second change is the use of RTSP encapsulated in HTTP for all the communications between the API components and the VisorNet, what means that only TCP connections to a single port are used, and therefore communications can be established through firewalls or proxies.

Changes from 5.0.0

New control

In this version, a new control called ImageView is included in the API, which provides imaging capabilities to the application, and it can substitute the control ImageGear, used by API users in previous versions. It can be used, among other functions, to display the images received from the API with the event NewImage.

New properties

short VideoDate;

Changed methods

There has been small changes in some of the API methods, due to a different internal design. However, the adaptation of code using previous versions of the API to the new methods means a minimal work following the instructions in this document.

The next two methods are new, and are used to establish or close a connection (session) with any centre. More information can be found in the documentation.

 

Log Mode ^ ^  BACK  TO API MAIN PAGE ^ ^
 

The VisorNet API has a log mode in which you can obtain some important information about the internal operation of the controls. It is useful for debugging and allows a better understanding of how the API works.
Currently, only the WatchEngine control supports the log mode.