search

obsproject / obs-websocket

Remote-control of OBS Studio through WebSocket
GNU General Public License v2.0
3.8k stars 701 forks source link

Bug: websocket per profile not working #1127

Closed veravsms closed 1 year ago

veravsms commented 1 year ago

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

28.1.x

OBS Studio Version (Other)

No response

obs-websocket Version

5.1.0

OBS Studio Log URL

https://obsproject.com/logs/uVUFYUaogKom2bqa

OBS Studio Crash Log URL

No response

Expected Behavior

Each profile saves its own WebSocket settings.

Current Behavior

WebSocket is saved globally instead of the profile as stated here. https://github.com/obsproject/obs-websocket/issues/269

Steps to Reproduce

1.profile 1, websocket = 1 2.profile 2, websocket = 2 3.use profile 1 and change websocket to 1000 4.restart obs result: profile 1, websocket =1000 profile 2, websocket =1000 expected behavior: profile 1, websocket =1000 profile 2, websocket =2

Anything else we should know?

https://github.com/obsproject/obs-websocket/issues/269

tt2468 commented 1 year ago

This is not a bug, it's by design. To mimic behavior of per-profile obs-websocket settings, please use the available startup command line parameters). On Windows, I recommend creating shortcuts which specify parameters to override the WebSocket port and the profile/scene collection.