PTZ Controls

PTZ Controls 0.18.2

Sure, here it is. I see no reference to the PTZ plugin in it.

In case this helps:

$ ls -ld /Library/Application\ Support/obs-studio/plugins/obs-ptz.plugin
drwxr-xr-x 3 root admin 96 Dec 2 08:52 /Library/Application Support/obs-studio/plugins/obs-ptz.plugin
 

Attachments

Last edited:
I'm probably doing something stoopid, but can't figure out just what. Running Ubuntu 22.04 with OBS 29. Install with the built-in package installer fails, so I tried manually with dpkg. I receive:
$ sudo dpkg -i ~/Downloads/obs-ptz-v0.13.0-linux-x86_64.deb
dpkg: error processing archive /home/don/Downloads/obs-ptz-v0.13.0-linux-x86_64.deb (--install):
parsing file '/var/lib/dpkg/tmp.ci/control' near line 8 package 'obs-ptz':
'Version' field value 'v0.13.0': version number does not start with digit

Could it really be as simple as removing the "v" from the Version field? I know nothing about editing .deb files, but it seems to require more than a simple file replace in the .deb file.

Thanks: ..DonA
This is a bug. I've not been testing the Debian packages, so I hadn't caught that I broke it when switching to git commit ids. I'm working on a fix and will get it into the v0.13.1 release
 
Sure, here it is. I see no reference to the PTZ plugin in it.

In case this helps:

$ ls -ld /Library/Application\ Support/obs-studio/plugins/obs-ptz.plugin
drwxr-xr-x 3 root admin 96 Dec 2 08:52 /Library/Application Support/obs-studio/plugins/obs-ptz.plugin
This is unusual. I've been unable to reproduce this problem. On an Intel Mac machine without OBS I just did a clean install of both OBS and obs-ptz and it ran without issue. Can you try a fresh install of both OBS and the plugin? If that doesn't solve the problem then please file an issue on https://github.com/glikely/obs-ptz/issues
 
Hi everyone. Thank you for your patience with the v0.13.0 release. I made some big changes on the back end which caused regressions and I'm hoping to have them addressed in v0.13.1. On that note, I've just tagged what I hope to be the last release candidate for v0.13.1. You can find it here. Please test and report back. If all looks good then I'll tag the full release this weekend.

Bugs fixed:
- visca: single ended connections now work again without ~1s lag
- visca: pan/tilt at lowest speed should work again on all cameras
- visca: movement speeds clamped to the valid range
- pelco: Fix uncontrolled zoom
- pelco: added focus control
- camera drift on startup fixed
- Debian package works again

 
Please try v0.13.1-rc3 and report back if it works for you. I'm unable to test it as I don't have an x86 Linux box with me at the moment.

Thanks for the reply. I see that you uploaded a couple newer RCs. I tried rc5. It appeared to install without error. But I don't find an obs-ptz directory under ~/.config/obs-studio/plugins. Also I find nothing PTZ related under the Docks or Tools pulldowns. Am I looking in the wrong place?
 
Thanks for the reply. I see that you uploaded a couple newer RCs. I tried rc5. It appeared to install without error. But I don't find an obs-ptz directory under ~/.config/obs-studio/plugins. Also I find nothing PTZ related under the Docks or Tools pulldowns. Am I looking in the wrong place?
V2: OOPs! I looked at the obs log file and found that I was missing a qt6 file. So I installed the missing dependency, uninstalled rc5, then re-installed it. Now I find PTZ Controls under Docks, and PTZ Devices under Tools. But still no new directory under ~/.config/obs-studio/plugins, so obs-ptz must install elsewhere. At the moment I'm using my home PC with no PTZ camera. I can't wait to try it on the "real" system at church. Thanks tons! ..DonA
 
I was getting ready to file a ticket for my HCSTVCON HC-HD35S saying that illegal pan and tilt speeds were causing it to misbehave in interesting ways, when I noticed you note about v0.13.1. I installed rc5 and it seems to be working well for me (at least it has addressed the problems I was seeing). Here is my system info to round out the picture:

11:34:02.232: CPU Name: Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
11:34:02.232: CPU Speed: 2600MHz
11:34:02.232: Physical Cores: 4, Logical Cores: 8
11:34:02.232: Physical Memory: 8192MB Total
11:34:02.232: OS Name: macOS
11:34:02.232: OS Version: Version 10.15.7 (Build 19H2026)
11:34:02.232: Rosetta translation used: false
11:34:02.232: Kernel Version: 19.6.0
11:34:02.233: hotkeys-cocoa: Using layout 'com.apple.keylayout.US'

Thanks for the update!
 
I was getting ready to file a ticket for my HCSTVCON HC-HD35S saying that illegal pan and tilt speeds were causing it to misbehave in interesting ways, when I noticed you note about v0.13.1. I installed rc5 and it seems to be working well for me (at least it has addressed the problems I was seeing). Here is my system info to round out the picture:



Thanks for the update!
Glad to hear the new version is working well. Out of curiosity, what behaviour did you see with the older version?
 
glikely updated PTZ Controls with a new update entry:

OBS PTZ Controls v0.13.1 - Bug fix release

This is a bug fix release for the v0.13.x series. All users of v0.13.0 should upgrade as it fixes many of the regressions in v0.13.0. It fixes a number of longstanding problems with the way the VISCA support was implemented. Transmit only serial connections should be usable again instead of having >1s delays in the camera responding. The unexpected drift of pan/tilt/zoom on startup is now fixed.

If you're still using v0.12.2 because you like the discrete speed control slider, then you don't...

Read the rest of this update entry...
 
Glad to hear the new version is working well. Out of curiosity, what behaviour did you see with the older version?
A few things. Using VISCA serial (RS-232) for the camera control, the UP, LEFT, RIGHT, DOWN arrows did nothing and I was seeing errors in the logs. I tracked that to the camera not liking '7f' in the unused pan or tilt (respectively) speed fields of the pan / tilt commands. The UP/LEFT, DOWN/RIGHT, etc. buttons would make the camera run continuously to its limits without ever stopping. I tracked that to the camera not liking '7f:7f' in the pan and tilt speed fields of the STOP command. HOME worked perfectly as did the zoom operations. I went so far as to grab a copy of the code in order to maybe make a PR to fix it before I noticed your update.

It turns out, my MacBook is too old to be able to build OBS, so I would not have been able to test a PR on my MacBook. I could have tested it on a Linux system, and, if I do decide I want to try to contribute to this project, it will probably be from a Linux system, but it was good in this case that I didn't have to go there.

Thanks for the very thorough logging. It made it very easy to figure out what was going on with my camera.

I am attaching my logs and my log analysis for your enjoyment.
 

Attachments

A few things. Using VISCA serial (RS-232) for the camera control, the UP, LEFT, RIGHT, DOWN arrows did nothing and I was seeing errors in the logs. I tracked that to the camera not liking '7f' in the unused pan or tilt (respectively) speed fields of the pan / tilt commands. The UP/LEFT, DOWN/RIGHT, etc. buttons would make the camera run continuously to its limits without ever stopping. I tracked that to the camera not liking '7f:7f' in the pan and tilt speed fields of the STOP command. HOME worked perfectly as did the zoom operations. I went so far as to grab a copy of the code in order to maybe make a PR to fix it before I noticed your update.
Awesome work on the analysis. Thanks! Those bugs are due to a number of off-by-one mistakes that I made which set the magnitude incorrectly. The cameras I have were happy enough to still accept those packets, so I didn't notice until I got bug reports.

BTW, for future investigation, I've added a visca camera emulator script in the scripts/ subdirectory which helps for tracking down protocol problems. You may find it useful.
It turns out, my MacBook is too old to be able to build OBS, so I would not have been able to test a PR on my MacBook. I could have tested it on a Linux system, and, if I do decide I want to try to contribute to this project, it will probably be from a Linux system, but it was good in this case that I didn't have to go there.
I would really appreciate the help! I've got limited time to work on this project and a long list of todos and issues that need some love. You can try pinging me, 'glikely' on the OBS Discord server if you want to talk a bit about what is needed. If I'm around and have time to talk I'll respond.

I find Linux is an easier environment to work from anyway. My primary development machine is an M2 Mac, but I switch back and forth between native Mac and a Linux VM. Very little of the code is platform specific so it often doesn't matter which platform you develop on.
 
Hey man! I am unable to configure my NEOID PTZ USB camera without a network cable. I only use the camera via USB but in OBS I don't know how to configure it. Can you tell me if it is possible to configure without a network cable? If so, would you tell me how?
 
Awesome work on the analysis. Thanks! Those bugs are due to a number of off-by-one mistakes that I made which set the magnitude incorrectly. The cameras I have were happy enough to still accept those packets, so I didn't notice until I got bug reports.

BTW, for future investigation, I've added a visca camera emulator script in the scripts/ subdirectory which helps for tracking down protocol problems. You may find it useful.

I would really appreciate the help! I've got limited time to work on this project and a long list of todos and issues that need some love. You can try pinging me, 'glikely' on the OBS Discord server if you want to talk a bit about what is needed. If I'm around and have time to talk I'll respond.

I find Linux is an easier environment to work from anyway. My primary development machine is an M2 Mac, but I switch back and forth between native Mac and a Linux VM. Very little of the code is platform specific so it often doesn't matter which platform you develop on.
At the moment (and for the foreseeable future) my paying job has me pretty wrung out intellectually at the end of the day, but, if I get my teeth into something I want or need with obs-ptz, I will definitely pass the result on to you. When it came to this bug, I figured I could probably pop in and find the problem without too much trouble, and the system I am setting up needs to get done, so I started to jump in. Could easily happen again, now that I have the code. It looked like it was well structured for platform independence, so I can probably work from my Linux system, which is even older than my Mac, but should work for this kind of stuff.

Thanks for providing this thing. It really makes it nice to have ptz built into OBS.
 
Hey man! I am unable to configure my NEOID PTZ USB camera without a network cable. I only use the camera via USB but in OBS I don't know how to configure it. Can you tell me if it is possible to configure without a network cable? If so, would you tell me how?
Sorry, control over USB (UVC cameras) is not supported yet. I’d like to add it, but haven’t had time, and I don’t have any hardware to test with.
 
Hi guys,

I would like to ask you it will be a function to use auto motion tracking for ptz cameras? Sorry my knowledge is poor of this topic but it would be great to use if its possible.

Thanks for answer
 
Hi guys,

I would like to ask you it will be a function to use auto motion tracking for ptz cameras? Sorry my knowledge is poor of this topic but it would be great to use if its possible.

Thanks for answer
Are you asking about turning on some kind of motion tracking feature built into some PTZ cameras? Or having a feature in the plug-in itself to track an object?

For the former, I don’t have anything in the plug-in currently, but if you can point me at a specific camera that you want supported then I can take a look.

For the latter, take a look at the face tracker plug-in by @norihiro . It works with this plug-in to control a camera. You can find it here:

 
Back
Top