Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings don't update when set via a WebSocket request #84

Open
Vegamm opened this issue Mar 18, 2024 · 2 comments
Open

Settings don't update when set via a WebSocket request #84

Vegamm opened this issue Mar 18, 2024 · 2 comments

Comments

@Vegamm
Copy link

Vegamm commented Mar 18, 2024

I am using OBS WebSocket to remotely update the 'url' and 'request_data' settings. I notice that when observing the data in OBS, the properties are not updating. I am trying to do this to dynamically update the URL value for a stream. This is an idea I had for getting text-to-speech working with different voices from ElevenLabs but I cannot seem to dynamically update the url.

OBS: 30.1.0
obs-urlsource: 0.2.6
obs-websocket: 5.0.1

Expected Behavior:
When calling 'SetInputSettings' via a WebSocket connection, the settings are updated and persist for the source.

Actual Behavior:
When calling 'SetInputSettings' via a WebSocket connection, the settings do not persist and are not consumed by the source. On a call to 'GetInputSettings', I see the setting values are updated but OBS does not show the updated settings when opening the 'Properties' window.

@royshil
Copy link
Collaborator

royshil commented Mar 18, 2024

Yes the URL setting on the source is "just for show" the actual request data (url and all the settings) are serialized in a hidden setting called "request_data"

You possibly could deserialize the data, edit the url, and serialize again and update the settings on the source. That would likely work.

The only way to make this seamless is to allow multiple inputs. I've began to implement that but the UI overhead is big... Gets messy.

@Vegamm
Copy link
Author

Vegamm commented Mar 18, 2024

You possibly could deserialize the data, edit the url, and serialize again and update the settings on the source. That would likely work.

I did try this too but the data did not persist in this case either. Anyways, I appreciate the response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants