Skip to content

globi84/TCPmessage4OBS

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 

Repository files navigation

TCPmessage4OBS

test script to send and recieve tcp messages to controll obs

Prerequisits

How to use

  • Install OBS and OBS Websocket and start it.
  • Create some scenes in obs
  • Download OBSCommand and unzip the archive. For Example c:\scratch\OBSCommand
  • Clone the git repo https://github.com/globi84/TCPmessage4OBS
  • Check the path to the OBSCommand.exe at TCPMessage4OBS_server.ps1 and run it from the command line.
  • Run now TCPMessages4OBS_testclient.ps1 from the command line.
  • Now you should be ready to remote controll your OBS.
#Start VirtualCam
Send-TCPMessage -Port 29800 ` -Endpoint 127.0.0.1 -message "=StartVirtualCam"
#Stop VirtualCam
Send-TCPMessage -Port 29800 ` -Endpoint 127.0.0.1 -message "=StopVirtualCam"

#Switch to Scene "Speaker"
Send-TCPMessage -Port 29800 ` -Endpoint 127.0.0.1 -message "=SetCurrentScene,scene-name=Speaker"

It should work with every command, that are defined at https://github.com/obsproject/obs-websocket/blob/4.x-current/docs/generated/protocol.md

Help

If you get an error, when you start the powershell script, then you need enable to run it.

c:\temp\TCPMessage4OBS_server.ps1 : File C:\temp\TCPMessage4OBS_server.ps1 cannot be loaded because running scripts
is disabled on this system. For more information, see about_Execution_Policies at
http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ c:\temp\TCPMessage4OBS_server.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess

then you sould run the following command on a elavated console.

Set-ExecutionPolicy RemoteSigned

after this. should everything work.

About

Remote Controll Obs with TCP messages

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published