Module needs variables added to pull VISCA inquiry requests from cameras that can be displayed on buttons.

For example pulling current Iris (CAM_IrisPosInq) 81 09 04 4b ff values to show on button controlling those values.

Similar to the OBS Studio Instance.

Sentry Issue: COMPANION-8M

TypeError: Cannot read property 'replace' of null
  File "app:///lib/module/ptzoptics-visca/index.js", line 1050, in instance.action
    var hexData = opt.custom.replace(/\s+/g, '');
  File "app:///lib/action.js", line 439, in null.<anonymous>
    instance.action(action, extras);
  File "app:///lib/instance.js", line 75, in EventEmitter.<anonymous>
    cb(self.active[id]);
  File "app:///lib/action.js", line 431, in EventEmitter.<anonymous>
    self.system.emit('instance_get', action.instance, function(instance) {
  File "app:///lib/action.js", line 411, in EventEmitter.<anonymous>
    self.system.emit('action_run', a, { deviceid: deviceid, page: page, bank: bank });
...
(5 additional frame(s) were not displayed)

Module is present in the 3.1.1 stable release (6229), but not in the beta release 3.2.0 (6442).

The Command Packet for preset recall speed is incorrect for the 20x-SDI.

It needs to be 81010601pFF. p: speed grade, the values are (0x01~0x18)

Hello. What's the status of this module?

I have some PTZOptics clone cameras and I wanted to try out some features of Companion V3 Beta. However, I noticed that this module isn't currently bundled, presumably because of errors (though I'm not sure how to see what those errors are).

So I decided to check out the sony-visca module and it turns out it is already compatible with V3, and under active development. Unfortunately, that module doesn't support TCP connections, which this module does (and which I need for my cameras).

So I submitted a PR to add TCP functionality. There was also a conversation under another issue.

My PR adds the option of using the TCP protocol and after a lot of testing this weekend I can confirm it works well and does everything (and more) that I need it to do.

After some careful consideration the maintainer(s) have decided to not accept my PR because it could begin to diverge that module away from being specific to Sony cameras. And whilst the idea of a creating generic VISCA module that works for all VISCA cameras seems attractive, it appears it's not without its downsides too.

So I guess this module will need updating to work for V3. And there are also quite a few useful features that are implemented in the Sony module that aren't in this one.

There are also several other VISCA modules that are in need of similar modernisation if they are to survive beyond v2.

Is anyone already working on a V3 upgrade for this module?

I'm happy to help out, and also would love to port some of the Sony module features if it would make sense to do so (don't know how we would decide), and reduce waste/duplicated effort where at all possible.

The prepared buttons "Save Preset n" saves camera position in "PTZ preset (n-1)" which makes things confusing when operating the PTZ cameras with other interfaces. Also it is not obvious how to store the special "PTZ preset 0" that is used as "home position" if stored.

I have the camera AV-E20-NDI from AVKans. They tell me it is PTZoptics visca compatible. Using there software it will control but only with UDP 1259. If I put port 1259 in the PTZoptics connection it fails to connect with no entry in the log file of companion. Is there a way to force the PTZoptics to use UDP and not TCP

I would really appreciate if you could please add the Kelvin WB and Gain control to the module.

https://ptzoptics.com/wp-content/uploads/2020/11/PTZOptics-VISCA-Commands-Rev-1_4-8-20.pdf

I'm running into an issue where I'm unable to recall any camera presets through the companion action. I can control other camera features and can even save presets through the companion action. The only thing that isn't working is the ability to recall a preset that I've saved.

I've confirmed that the presets are stored in the camera through the web interface of the camera and everything works there.

Any ideas?

Describe the feature
There are lots of features missing in this module. One could help a lot to solve many, the OSD control ones. Through these 7 commands, one can easily change white balnce, shutter speed ...

Is this platform dependent (windows, mac, ..)?
No
If documentation is required to implement, do you know where to find it?
https://cdn2.hubspot.net/hubfs/418770/PTZOptics%20Complete%20VISCA%20over%20IP%20Commands%20(Packet%20Sender).ini

Usecases
See above

Hello, would it be possible to get some active feedback on the lens settings like what my iris or shutter are currently at?

I think it would be great if you could create an instance based on a variable name. Commands would then be sent to the IP address set in the variable name.

The PTZOptics cameras have support for 255 presets (most likely 256, stored as preset position 0-255), according to manual:

The companion module dialog dropdown for presets is limited to 0-63, the request is to extend this list to 255:

I am very happy with all the functionalities but i am missing one thing...
The pan & tilt function has the possibility to adjust the speed of panning & tilting.
I don't see a function to set the speed of the zoom. Is it not there or do i not see it?
It would be awesome to have control over the zoomspeed in the same way as it can control pan & tilt.

Unable to add custom command as it isn't working. Command for Power On is 8x 01 04 00 02 FF. Command for Power Off is 8x 01 04 00 03 FF.

i use companion for 4 ptz-optics cameras.
pan, tilt, zoom, focus, presets and so on work perfectly, BUT focus mode (auto focus or manual focus) and exposure mode (full auto, manual, iris priority, shutter priority, and bright mode) doesnt work.

i would expect when in manuel mode i can adjust settings, end then when i push auto it should find optimal settings (like find focus or find right exposure) more or less right away, but nothing happens

Hi,

Not sure if Håkon Nessjøen still maintains the module but I'll post here in case anyone else has this issue.

Setup:
Windows 10 21H1
Streamdeck XL running latest firmware 5.2.1
Companion 2.1.4 Stable
2x PTZOptics class cameras 30x and 20x using VISCA
OBS

Issue:
Companion buttons that are configured to trigger camera presets become unresponsive after a varible period of time.

Trigger:
It appears that if the cameras are turned on after the PC running Companion, that the module, whilst constantly listening for the camera to respond, is using up some memory and not releasing it back to the module. That once the resources for a specific module reach a certain level, the module stops responding.

Tests:
We've seen this happen individually with both cameras. We started both cameras then the PC and the module didn't hang. Started Camera 1 and not Camera 2, then the PC, then Camera 2. The module of the Camera 2 hung around 45 mins later. Ditto when starting Camera 2 first and not Camera 1.

The cameras are fine. We can control them with other third party devices over VISCA whilst the Companion module has hung. This is not ideal as the whole purpose of the Streamdeck was having these preset buttons working on it.

Temporary Workaround:
Going into the Companion Connections screen then disabling / re-enabling the hung PTZOptics VISCA module. Companion buttons using the module then come back on line. The workaround isn't a solution given you're in the middle of a live performance and having to leave the video mixer to restart the Companion module.

Additional info.
We upgraded the system to Companion 2.2 which didn't solve the issue. Given the latest v.1.1.6 module release date of 5th April 2021, it would be included in Companion 2.1.3 / 2.1.4 and 2.2

Severity 1.
If there is a memory leak in the module, we don't want to be on tenterhooks not knowing if the module is going to hang esp during a long live service.

Thanks

companion-module-ptzoptics-visca currently supports "standard" lens speed, which makes it very hard to precisely set zoom and focus.

My request is to implement the variable commands instead:

and a mechanism similar to pan/tilt to set the speed

But as long as I'm here I'll ask that speed for pan, tilt, zoom, and focus should be options on those controls rather than just a separate setting.

The module completely stops working after being idle for only half an hour or so. This issue has been present for quite a while and still hasn't been fixed.

Is this a feature relevant to companion itself, and not a module?

• I believe this to be a feature for companion, not a module

Is there an existing issue for this?

• I have searched the existing issues

Describe the feature

It would be helpful if Companion could make calls to PTZOptics using a variable and calculation for Camera number and Preset Number. Thus I could recall a preset with ( + 1) for Camera ( + 1). Believe this is a Companion issue for making the call rather tag a PTZOptic request, hence posted here. This would make coding of saving and loading preset configs a lot easier.

Usecases

Different camera presets for different types of events; different camera presets for different users with their favourite shots.