Control Visca-over-IP based cameras

OBS Lua Control Visca-over-IP based cameras 2.8.1

Stability fixes and new features for the script plugin: support Pan/Tilt and Zoom in scene actions.

This update adds new capabilities for animation actions in the scene configuration dialog (thanks to a user contribution by christinoleo). The actions Pan/Tilt, with configurable direction and speed, and Zoom, also with configurable speed, are now available as action in a scene. This way you can pan the camera over a crowd automatically in a scene. When you switch scenes, the animation is canceled.
In addition, presets can now also be recalled via a hotkey assigned in the OBS Hotkey configuration. This can be used together with animation to position the PTZ camera to the beginning of the animation before starting an animation in a scene.

Small other improvements are a 'debug' checkbox in the settings to easily enable verbose logging to find errors or issues. The connection handling has been addressed. The Power-On and Power-Off actions now explictly close and re-open a connection to the camera. This fixes unreponsive cameras in certain cases.

For more details and usage instructions, see obs-visca-control on Github.
New features for the script plugin: support for PTZOptics and Hotkey actions.

- PTZOptics support: The script settings have two new configuration items: the port and protocol mode. The port defaults to 52381 and can be changed when needed (e.g. to 1259 for a PTZOptics camera). The protocol needs to be set to 'PTZOptics' to make the script talk the Visca dialect of PTZOptics.
- Pan, Tilt & Zoom actions can now be performed using a hotkey (for camera's that support pan, tilt or zoom). The action will start when the key is pressed and stops when the key is released.

For more details and usage instructions, see obs-visca-control on Github.
This updated improves the Visca implementation:
  • Fix for a resource leak; socket connections were not closed, claiming a new connection for every send command.
  • Connections are now re-used for each camera. This also means that the message counter (part of the Visca protocol header) is now used properly.
This updated includes a few enhancements and minor changes to the documentation:
  • The visibility (enabled/disable) of the Visca plugin source is now respected. When the plugin is disabled in a scene, the action is not executed.
  • A new options is added to the source settings of the plugin to run an action on preview only when the camera is not active on program. This prevents accidental changes to the camera as long as it is live for broadcasting.
Back
Top