Home Explore Help
Sign In
noah
/
diy_ptz_switch
1
0
Fork 0

2 Commits a88a4f4677 ... a43758d22a

Author SHA1 Message Date
  Noah Vogt a43758d22a fix broken camera transport when too many commands are sent in a short time + update README.md 3 days ago
  Noah Vogt a88a4f4677 fix broken camera transport when too many commands are sent in a short time 3 days ago
1 changed files with 2 additions and 2 deletions
Unified View Show Diff Stats
  1. 2 2
      README.md

+ 2 - 2
README.md
View File 

@@ -2,9 +2,9 @@
 
 
 
 For a typical livestream production environment consisting of 2 ptz cameras and one joystick / controller board, most commercial options like the [Skaarhoj PTZ Fly](https://shop.skaarhoj.com/products/ptz-fly-w-blue-pill-inside) are
 
 For a typical livestream production environment consisting of 2 ptz cameras and one joystick / controller board, most commercial options like the [Skaarhoj PTZ Fly](https://shop.skaarhoj.com/products/ptz-fly-w-blue-pill-inside) are
 
 - expensive
 
 - expensive
 
-- offer no API
 
+- offering no API
 
 - nearly impossible to automate
 
 - nearly impossible to automate
 
-- offer no rs485 serial connection support (basically only IP via RJ45)
 
+- offering no rs485 serial connection support (basically only IP via RJ45)
 
 
 
 To fix this, I thought why not connect the ptz cameras via their rs485 to a rs485 <-> usb serial converter to a computer and use a server that selects which ptz camera is sent the current joystick input. It also has a http api that allows seleting the current camera target and ptz commands like save_preset or goto_preset.
 
 To fix this, I thought why not connect the ptz cameras via their rs485 to a rs485 <-> usb serial converter to a computer and use a server that selects which ptz camera is sent the current joystick input. It also has a http api that allows seleting the current camera target and ptz commands like save_preset or goto_preset.