You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any update regarding: Transitions.CreateSceneTransition and SceneItems.SetVisibilityTransition?
Currently i am setting those by modifying the profile & scene collections config files at $HOME/.config/obs-studio using a template that replaces what i need changed, and creates the files.
This while it works is very limiting, and i find myself setting up some things through config file templating, and some other things (mostly the event driven ones) using the websocket api.
Is this what most people do? Utilize the websocket api only to modify what they have already setup manually or through config files?
It would be nice if most features could be set through the websocket api, ideally not as a plugin but offered directly from the obs project (maybe the ui can also use the same api behind the scenes)
Requested Feature Usage Scenario
Drive everything through the websocket api, including transitions.
The text was updated successfully, but these errors were encountered:
Feature Request Type
RPC Request
Feature Request Type (Other)
No response
Requested Feature
Google Docs Features
Is there any update regarding: Transitions.CreateSceneTransition and SceneItems.SetVisibilityTransition?
Currently i am setting those by modifying the
profile
&scene collections
config files at$HOME/.config/obs-studio
using a template that replaces what i need changed, and creates the files.This while it works is very limiting, and i find myself setting up some things through config file templating, and some other things (mostly the event driven ones) using the websocket api.
Is this what most people do? Utilize the websocket api only to modify what they have already setup manually or through config files?
It would be nice if most features could be set through the websocket api, ideally not as a plugin but offered directly from the obs project (maybe the ui can also use the same api behind the scenes)
Requested Feature Usage Scenario
Drive everything through the websocket api, including transitions.
The text was updated successfully, but these errors were encountered: