Hello
@Warmuptill, thank you very much for this great plugin, now with the macro tab, your solution helped me to get rid of 2 other OBS companion software for automating.
I truly believe that 90% of the functions of your plugin could be transferred to the macro tab and work so much better. Since this is just the beginning, I'm using Noobs Commander (OBS Commands) to create bat files with some actions that are still not supported at the moment, but I'm sure eventually it will be added to it :)
I have just one question/suggestion for you, if you don't mind: opening the current logs window, I could see a couple of macros running over and over because of its trigger matches the current scene. For example: mute an audio output when this scene is currently showing. Since I've set it to run every 1000ms, it keeps muting the output audio at every 1 second. I know that it works since the audio is muted over and over but I have a couple of macros that executes a bat file that I just need it to do it once for every trigger. I also understand that audio level triggers should execute every x milliseconds, makes sense, but maybe an "execute once" or automatic identification of actions that only needs to run once would be brilliant. Also, the logs files at the end of my streams are almost 2mb TXT files haha
Do you think that this could be sorted somehow?
Again, thank you very much for your great work!
Thanks for the suggestions!
>some actions that are still not supported at the moment
I would be very much interested in what additional actions you are looking for, so I can improve the plugin!
(I already implemented actions for scene item visibility, global source en-/disable and filter en-/disable options)
>an "execute once" or automatic identification of actions
Great suggestion.
I plan on supporting additional actions which let you pause (or unpause) macros, which could be useful here.
(So the macro can just disable or "pause" itself once it was run)
I also already implemented the "interval" condition which lets you control how often a macro is able to be triggered.
>Also, the logs files at the end of my streams are almost 2mb TXT files haha
Good point :)
I will try to reduce the logging a bit more when not running in verbose mode.
If you want to give the above mentioned features a try you can choose any recent build on GitHub from the master branch.
But these might of course still contain some bugs as they are still under development.
Hi and thanks for the awesome plugin. Need a little help here. I have all my scenes setup under the media tab to go through 1 -8 scenes, in order. It works great but I frequently need to restart it because it will randomly start switching between ALL random scenes back and forth until I start and stop it several times then randomly it will work and start playing in order from SCENE 1-8 start to end. I dont know what setting it is or what I am doing wrong. Please help as I dont know what setting is causing this or is it a bug?
I think the state "Played to End" might work better here.
I think what is happening in the "error" case is that multiple media sources are in the state "ended" at the same time.
Then once the plugin switches to a specified scene the playback for the media source is started again - meaning the condition is which lead to this scene change is no longer true and the next one in the list is checked.
This will trigger another scene switch.
This in turn might lead to the playback that was started by the previous scene switch to end once again.
And this finally results in a loop of seemingly random scene switches.
Let me know if this works!
