dqm

Member
i have updated to 28 and we have some controlling back for our ptz camera. the arrows for up down left right will not work and lost the speed control. how can i fix this so all the controls work in obs? i can email picture of what the controls look like if needed
I believe the speed control is gone by design: replaced by algorythm that gradually increases the speed the longer you hold the button down. The arrows may be working, only slowly. Hold the button down longer to see if the pan/tilt speed ramps up.
 

glikely

Member
I believe the speed control is gone by design: replaced by algorythm that gradually increases the speed the longer you hold the button down. The arrows may be working, only slowly. Hold the button down longer to see if the pan/tilt speed ramps up.
left/right/up/down no longer working is probably a separate issue. Some VISCA implementations don't behave well when told to only move in one axis. It was a quirk I had fixed before, but I probably broke it again when I overhauled the state machine. I'll see if I can get it working again.

The speed slider removal is indeed by design, but it has caused regressions or unworkable behaviour for some cameras. I'm going to add configuration options to limit the minimum and maximum move speeds.

For anyone having trouble with the latest version I recommend going back to v0.12.2 until I can get the speed ramp to be more usable
 

glikely

Member
Hi dqm. Thanks for the feedback. Comments below...
I understand that you've previously contemplated starting with an empty preset list that can be maintained similar to the Scene and Source lists. This would allow fewer/more presets and flexible ordering. While I upvote that idea, I'd like to propose taking it to the next level.

What I had in mind was refactoring the preset list as an "action" list, supporting multiple action types, each action type configurable with the supporting values it needs. Calling a preset would, of course, be one action type, supported by a configurable preset number. A second action type, which sort of drives this proposal, would be calling a scene, supported by the scene name. Given the complexity with which scenes can be constructed, this would be an enormously powerful feature. For example, it would enable camera changes with transitions from the ptz control pad. (Confession: calling raw presets without transititons to mask gross camera movements is too risky for my workflow.)

One can imagine other action types with potential for lots of extensibility. Think about an action type that issues a generic camera command, configurable in the settings. Or many OBS commands, for that matter (though I urge caution about getting too distant from camera control). Down the road, one could even support a multi-step action type--one that issues a sequence of actions, similar to what Stream Deck and Companion support.
Great ideas, thanks! I'm concerned however that implementing these features in the PTZ plugin could make it quite limited. I've been thinking instead about exporting API hooks that can be used by the Advanced Scene Switcher, and possibly allow the plugin to trigger Advanced Scene Switcher actions since the scene switcher has far more functionality than I'll ever add to the PTZ plugin.
Finally, think about the relationship between an item in a device's action list and the action that it invokes. In its simplest form (as with presets now), it's 1-1. In other words, each item invokes a single action and that action is associated with a single item. With the mult-action feature mentioned above, that relationship becomes 1-many: one item invokes multiple actions, but each action is still associated with only one item in the list. The most robust design is many-many. That means separating device settings from action settings in your underlying configuration structure. Then, the same action can be used for multiple devices. For example, an action for "call preset 1", could be assigned to any or all cameras. Or, invoked in other ways--like by assigning it to one of the buttons under direction arrows. FWIW, the relationship between Scenes and Sources follows that design principle.
So something like a preset triggering a named action, correct? I think this also leans towards defining the action list in a more generic tool, and then merely triggering the action from the PTZ frontend.
 

renancs

New Member
Hello, its possible adapt this plugin to work with USB PTZ cameras? Like Logitec Rally? Im trying to create custon scenes in diferents places in a room, but cant figure how... i think your plugin might works, if can be customized to usb cameras.

Thnx!!
 

Dav0

New Member
Have been streaming a church service using OBS 27 for over 12 months using two Tenveo Cams over RS232 links. Upgraded today to OBS 29 with PTZ Controls V0.13.0. Everything good except that the cameras keep moving for 2 or 3 seconds after actuation of the up/down and zoom controls ceases. This delay did not occur in the previous configuration, and it makes the system almost unusable. Can you please advise what I can do to solve this problem, please? Should I go back to OBS 27?
 

Dav0

New Member
Have been streaming a church service using OBS 27 for over 12 months using two Tenveo Cams over RS232 links. Upgraded today to OBS 29 with PTZ Controls V0.13.0. Everything good except that the cameras keep moving for 2 or 3 seconds after actuation of the up/down and zoom controls ceases. This delay did not occur in the previous configuration, and it makes the system almost unusable. Can you please advise what I can do to solve this problem, please? Should I go back to OBS 27?
I uninstalled V 0.13.0 and installed V 0.12.2 (still with OBS 29). Camera behavior has reverted to the original i.e. without the delay.
 

DonA.N4TH

New Member
New to the forum. We've been using OBS and Zoom under Win10 at church for about a year. Since the Win11 update OBS has become unstable. I've been trying to set up an Ubuntu 22.04 environment. I have OBS 29 installed. I can't get the OBS-PTZ plugin to install, either from the .deb file or compiling from source. I'd this a known problem? Any workarounds? Thanks.
 
Top