Sends image frames received from a camera. The image source can work in two different modes:
- Software trigger. If this input is connected, images are captured only when an object is received in it. The trigger input accepts any object type.
- The ID of the selected camera. The camera ID must be composed of a driverId, a colon and a camera id, for example "webcam:usb-Logitech_Ltd._video-index0".
The ID can also be given as a regular expression. This is indicated by surrounding the ID with forward slashes. For example, "/^webcam:.*0$/" uses the first web camera whose id ends with "0". "/./" (Automatic) matches all cameras and thus uses the very first camera found by the camera manager. See device IDs.
If the tool is run in a KuvioKamera, the first camera will always be the first integrated camera head, even if external cameras (such as GigE or USB) were found. In the Application Builder, the first camera will be the first head of the first connected KuvioKamera.
If cameraId is a colon (:), a temporary virtual camera will be created. The object received in the trigger input will then be used as a file name to read.
- If this flag is
true, the camera will be configured with settings read from the camera configuration database at start-up. Otherwise, camera settings will not be touched with the exception of trigger mode, which will be set to software trigger (and back) if the trigger input is connected.
- The method of requesting camera position parameters. While it is possible to change camera position parameters manually at run time, the position database will only be queried during start-up. Thus, changes made to the position database will take effect only after a restart.
- The position and orientation of the world coordinate system with respect to the camera. This parameter has an effect only in the
ManualPositionmode. See coordinate frames for more information.
- The method of requesting camera calibration parameters. While it is possible to change manual calibration parameters at run time, the calibration database will only be queried during start-up. Thus, changes made to the calibration database will take effect only after a restart.
- The type of the camera's image sensor.
- The focal length of the camera in pixels.
- If this flag is true, the principal point will be automatically placed to the center of each outgoing image. Otherwise, the fixed value given by the principalPoint parameter will be used.
- The location of the principal point in pixel coordinates. The principal point is the point where the optical axis hits the image sensor.
- Radial distortion factors k1 and k2. Tangential distortion factors p1 and p2 are not currently used.
- The number of milliseconds the tool will wait for an image after a software trigger. If no image is received from the camera within triggerTimeout milliseconds, a run-time error will be generated. Setting triggerTimeout to zero makes the tool to wait forever.
- If set to
false, the tool will emit images in the raw encoded color format such as Bayer or YUV provided by the camera driver. If set to
true, the images are always automatically decoded to RGB before emitting.
- The image received from a camera driver or from the image property.
- The number of images sent since last reset.
- The number of captured image frames that were missed due to exhausted computing resources since last reset. This output will be sent only when frames are missed, and it is not synchronous to the other outputs. One should use this output for informational purposes only. Attaching heavy analysis to it easily causes more frames to be missed.
Methods for getting calibration data.
Methods for getting position data.