Warmuptill
Active Member
The macro should be still be executed at least once when the plugin is first started.But..., if "Perform actions only on condition change" is enabled, Adv. Scene Switcher doesn't always run a macro triggered only on day of week (my guess is that if Adv. Scene Switcher isn't running when the day of week actually changes at midnight, it doesn't recognize the macro hasn't fired yet when OBS starts on a different day).
The plugin does not need to "witness" the day actually changing.
You should be able to verify this with such a test macro:
And checking the value of the variable after starting the plugin on the variable tab:
If this *does not* work this would definitively be unintended behavior.
In that case I would be very interested in what you have configured so I can fix it.
You could share the setting by exporting them to a file.
The performance impact of those date checks / variable assignments should be minimal. (Just in case that is one of your concerns.)If "Perform actions only on condition change" is not set, there is no reliability issue because the macro is running every 300ms, 100% of the time -- which is almost certain to occur before the livestream startup macro is initiated by hotkey. But..., having a macro run 3x a second 100% of the time just to make sure a variable is set accurately based on day of week, doesn't seem like a particularly clean/elegant approach.
But as mentioned before I think the approach with having "Perform actions only on condition change" enabled should work unless something is broken.
This should be possible already thanks to @Destroy666! :)
- Having a way to set Adv Scene Switcher variables to a program's stdout output (so we can call PowerShell to produce a needed value).
- Or, a way to set Adv Scene Switcher variables to a program's exit code
Before I jump into a rather detailed set of questions I'd first like to say I greatly appreciate Adv Scene Switcher, and the time and effort you've obviously put into it.
From what I can tell the ability to do things conditionally within macro actions is currently a bit limited in this regard(?) -- unless I missed something?
It is indeed very limited.glaring omissions compared to most programming languages, one of which is inline conditionals
I understand and agree fully that this would be very useful to have.
But I always have to weigh it off against the time I have available and restructuring / redesigning the plugin to support this is unfortunately not an option for me at the moment.
What I could maybe do without too much effort is to add some of that functionality to the "Macro" action which already lets you run the action of other macros.
Adding a checkbox to only perform those steps if the conditions of the selected macro evaluated to "true" might be quite straight forward.
It is a great idea and sounds like fun project but I simply lack the time to implement this.At that point, why not add a python tab? It's already a mature language with a TON of features in addition to this, and lots of existing documentation and tutorials, and designed for beginners to pick up quickly and "just use". Each condition would then be a function with arguments/parameters that returns true or false, and you'd put them in your ownif
's and use python's logic to combine them. Actions would also be predefined functions in the new Adv. SS library...
A "code generator" might be useful as well, mostly to discover what exists to be able to use, and that could be heavily based on the existing GUI. Just limit the generator to one condition or one action, and a button to either put on the clipboard or insert at the cursor, the function call that corresponds to what it's set for at that moment.
But I do appreciate the suggestion nonetheless! :)