>I was thinking about the source and scene visibility actions: not sure how disabling a source would help, since you cannot control it using OBS UI, comparing to the current scene visibility. Don't you think it might confuse people and cause more problems than help?
I thought it might be useful if one would want to disable a source on every single scene, but I do agree that it might confuse people.
For now I added a warning clearly stating that disabling a source globally cannot be controlled via the regular OBS UI.
>Also, not sure if scene visibility is the best name, since it only changes sources. Maybe just calling "source visibility" would be more clear to understand :)
What about "scene item visibility"? (The name used in the API)
>Another small suggestion: as you can see on my latest screen grab, would it be possible to sort the sources the same way it is shown on the source list? That would help to find what source you need to set if you have many items and you had them organized it before.
Good point. This is stems from the way I am enumerating through the different sources.
I resorted to just sorting it alphabetically as even the using the order of sources might become confusing with a lot of sources.
I now implemented the source activity, visibility and settings conditions as well as the macro action to stop the plugin.
(Sorry that it took me so long to get around to it)
View attachment 71572
A build will be available here in a few minutes:
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
Let me know if it works as expected and what you think, if you should get the chance to give it a try! :)