Thank you so much for the many suggestions and your feedback!
I really do appreciate it a lot! :)
>Multiple trigger organization
I agree, visually it could definitely be improved. I am just not sure how, yet.
At the moment the order of operations will be the following assuming you have 4 conditions and they are linked with "and", "and not" and "or":
((((Condition 0) && (Condition 1)) && (!(Condition 2))) || (Condition 3))
>Audio source trigger
I think I might have implemented that already as part of the version you tried, by allowing you to control the master volume in the audio action.
>Source/Scene filter trigger
Scene visibility and hiding filters per source is part of the test build, but I assume you want to disable "all filter with name abc" and "all item in scene 123" at once right?
>Wait/delay
No, it is just a simple wait for now.
The whole plugin goes to sleep during this time.
Good suggestion, but might be a bit complicated to implement.
>Pause, stop, next/previous tracks
Media source actions were already implemented but on a different branch.
I merged it into the pause-branch in case you want to give it a try:
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
>Variables
That seems very advanced indeed.
I will keep it in mind, but I doubt that I will introduce it any time soon ;)
>Delete/change order of any actions/trigger
Good suggestion - That is already on the todo list.
>I've set the macro to disable a global source
I think that behavior is intended from the point of view of the OBS API - I will see if there is a API call more fitting.
Just to clarify: What would you have expected to happen? (Audio, video and UI)
Would the scene visibility action maybe be more suited to this particular case?
>This could work but a much better solution would be to have an option to "only run it once"
What do you think about adding a "count" condition, which limits how often a macro can be run?
I agree that the current pause action is a bit more complicated to set up, but at the same time it should also be more powerful.
(There should be no harm in having multiple ways to achieve this besides UI clutter ;))