Warmuptill
Active Member
Warmuptill updated Advanced Scene Switcher with a new update entry:
Advanced Scene Switcher 1.32.5
Read the rest of this update entry...
Advanced Scene Switcher 1.32.5
Read the rest of this update entry...
- Thread starter Warmuptill
- Start date
Warmuptill
Active Member
Thanks for letting me know!
I will look into it.
Hm .. interesting.
I wasn't aware of that.
I will investigate the problem and try to resolve it.
Thanks for letting me know about this!
Want To Learn
Member
Same thing: I installed it. When I opened it, everything froze in Obs. Nothing worked. I opened it again in safe mode, clicked a few things then reopened it in normal mode. It works fine! Thanks!
Warmuptill
Active Member
A build with a fix will be available here in a few minutes:
Vertical scene filter pull request run · WarmUpTill/SceneSwitcher@bb3a9bd
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
If that should be a problem feel free to reach out and I can try to share the build some other way.
Let me know if you face any issues with this test build! :)
FabioElizeu
New Member
I tested the Linux and Windows versions, and both worked.A build with a fix will be available here in a few minutes:
Note that you will have to be logged into GitHub to be able to download it at the bottom of the page.
Vertical scene filter pull request run · WarmUpTill/SceneSwitcher@bb3a9bd
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
If that should be a problem feel free to reach out and I can try to share the build some other way.
Let me know if you face any issues with this test build! :)
Thank you very much!!!
Is Advanced Scene Switcher capable of doing what this guy has (<--- Link) in the bottom left corner of his streams? I looked for a Push To Talk type plugin that can manage multiple button presses simultaneously and the only one I found (<--- Link) requires Python coding (which is way over my head).
I tried the built in hotkey feature and that only enabled the source (would required two hotkeys to then turn off). I tried a basic macro, but that was a Push to start only or a push toggle on then again to toggle off.
Here is an example what I am trying to achieve. The left controller I will have on screen and same for mouse. As I depress buttons, they will turn red.
Like this
Then revert to unilluminated state once the button is released.
I tried the built in hotkey feature and that only enabled the source (would required two hotkeys to then turn off). I tried a basic macro, but that was a Push to start only or a push toggle on then again to toggle off.
Here is an example what I am trying to achieve. The left controller I will have on screen and same for mouse. As I depress buttons, they will turn red.
Like this
Then revert to unilluminated state once the button is released.
Attachments
Grok is the best. I asked it to rewrite that Python script to accommodate 27 buttons and within 20 seconds I had what I was looking for. I just had to troubleshoot a few minutes to determine how to resolve some conflict issues, ask Grok to adjust the script and now I am set!
Here is the new Python script for anyone hung-up on one button. If you need more, ask Grok to rewrite it for you and mention how many you need it to be.
Here is the new Python script for anyone hung-up on one button. If you need more, ask Grok to rewrite it for you and mention how many you need it to be.
Python:
import obspython as obs
import ntpath
NUM_BUTTONS = 27
# Per-button configuration
button_sources = [None] * NUM_BUTTONS # Source name for each button
button_inverts = [False] * NUM_BUTTONS # Invert flag per button
hotkey_ids = [obs.OBS_INVALID_HOTKEY_ID] * NUM_BUTTONS
hotkey_names = [""] * NUM_BUTTONS
# Global state for reference counting
active_counts = {} # source_name -> int: number of pressed hotkeys affecting it
target_visibility = {} # source_name -> bool: desired visibility when count > 0
rest_visibility = {} # source_name -> bool: desired visibility when count == 0
def script_description():
return "<b>Push to Enable - 27 Buttons (with Reference Counting)</b>\n\n" \
"Each hotkey enables (or disables if inverted) its assigned source while held.\n" \
"Multiple hotkeys can control the same source — it stays active as long as " \
"at least one assigned hotkey is pressed.\n\n" \
"Settings can be changed without interrupting active hotkeys."
def script_load(settings):
print("--- " + ntpath.basename(__file__) + " loaded ---")
for i in range(NUM_BUTTONS):
hk_name = f"push_to_enable_button_{i+1}"
hk_desc = f"Push to Enable Button {i+1}"
hotkey_names[i] = hk_name
hotkey_ids[i] = obs.obs_hotkey_register_frontend(
hk_name, hk_desc,
lambda pressed, idx=i: hotkey_callback(pressed, idx)
)
saved_array = obs.obs_data_get_array(settings, hk_name)
if saved_array is not None:
obs.obs_hotkey_load(hotkey_ids[i], saved_array)
obs.obs_data_array_release(saved_array)
def script_save(settings):
for i in range(NUM_BUTTONS):
save_array = obs.obs_hotkey_save(hotkey_ids[i])
obs.obs_data_set_array(settings, hotkey_names[i], save_array)
obs.obs_data_array_release(save_array)
def script_properties():
props = obs.obs_properties_create()
for i in range(NUM_BUTTONS):
# Source dropdown
list_prop = obs.obs_properties_add_list(
props, f"source_{i}", f"Button {i+1} Source",
obs.OBS_COMBO_TYPE_LIST, obs.OBS_COMBO_FORMAT_STRING
)
obs.obs_property_list_add_string(list_prop, "(none)", "")
sources_list = obs.obs_enum_sources()
if sources_list:
for src in sources_list:
name = obs.obs_source_get_name(src)
obs.obs_property_list_add_string(list_prop, name, name)
obs.source_list_release(sources_list)
# Invert checkbox
obs.obs_properties_add_bool(props, f"invert_{i}", f"Invert Button {i+1} (hide while pressed)")
return props
def script_update(settings):
global button_sources, button_inverts
global active_counts, target_visibility, rest_visibility
# Read new configuration
new_sources = []
new_inverts = []
for i in range(NUM_BUTTONS):
src_name = obs.obs_data_get_string(settings, f"source_{i}")
src_name = None if src_name == "" or src_name == "(none)" else src_name
new_sources.append(src_name)
new_inverts.append(obs.obs_data_get_bool(settings, f"invert_{i}"))
# Track old sources for cleanup
old_sources = set(active_counts.keys())
# Update button config
button_sources = new_sources
button_inverts = new_inverts
# Rebuild visibility mappings
target_visibility.clear()
rest_visibility.clear()
for i in range(NUM_BUTTONS):
src = button_sources[i]
if src is None:
continue
invert = button_inverts[i]
target_visibility[src] = not invert # Visible when active (normal), hidden if inverted
rest_visibility[src] = invert # Hidden at rest (normal), visible if inverted
# Update active_counts for currently assigned sources
current_sources = set(target_visibility.keys())
for src in current_sources:
if src not in active_counts:
active_counts[src] = 0 # New source, start at 0
# Clean up sources no longer assigned to any button
removed_sources = old_sources - current_sources
for src in removed_sources:
# If count is already 0, force rest state (safe to hide)
if active_counts[src] == 0:
set_source_visibility(src, False)
# If count > 0, leave it alone — some hotkey is still conceptually held
del active_counts[src]
# IMPORTANT: Do NOT force visibility changes on currently assigned sources
# This preserves visibility when holding hotkeys while changing settings
def hotkey_callback(pressed, idx):
src_name = button_sources[idx]
if src_name is None:
return
# Ensure source is in our tracking dicts (in case config changed mid-use)
if src_name not in active_counts:
active_counts[src_name] = 0
# Use current button's invert setting as fallback
target_visibility[src_name] = not button_inverts[idx]
rest_visibility[src_name] = button_inverts[idx]
if pressed:
prev_count = active_counts[src_name]
active_counts[src_name] += 1
# Only change visibility if transitioning from 0 to 1
if prev_count == 0:
set_source_visibility(src_name, target_visibility.get(src_name, False))
else:
if active_counts[src_name] > 0:
active_counts[src_name] -= 1
# Only change visibility if dropping to 0
if active_counts[src_name] == 0:
set_source_visibility(src_name, rest_visibility.get(src_name, False))
def set_source_visibility(source_name, visible):
if source_name is None:
return
scene_sources = obs.obs_frontend_get_scenes()
if scene_sources is None:
return
for scn_src in scene_sources:
scene = obs.obs_scene_from_source(scn_src)
items = obs.obs_scene_enum_items(scene)
if items:
for item in items:
item_src = obs.obs_sceneitem_get_source(item)
if obs.obs_source_get_name(item_src) == source_name:
if obs.obs_sceneitem_visible(item) != visible:
obs.obs_sceneitem_set_visible(item, visible)
obs.sceneitem_list_release(items)
obs.source_list_release(scene_sources)Warmuptill
Active Member
In case you still need it a "push to show" style macro can be set up like this:
It translates to:
If the hotkey with the name "Push to show" is pressed show the source named "Browser" on the current scene, else hide it.
I needed 30 and couldn't figure out how to do that without the Python Plugin (Which I got working). Thanks for following up. I do appreciate it!
hpanioniv
New Member
How do we clear stored advanced scene switcher settings? Even upon full uninstallation and reinstall, the settings/macros/etc. that I last created still get loaded. I accidentally created a wonky macro that created an infinite loop that crashes OBS. I have advanced scene switcher set to start automatically when OBS launches, so it crashes immediately every time, so I'm not able to go in and disable that macro or anything. Launching in safe mode doen't help as that completely disables the plugin so I can't change anything. And again, uninstalling and reinstalling just loads the same settings even after deleting all the files manually and then reinstalling. Am I just screwed and can't use this plugin on this computer anymore or am I missing something?
hpanioniv
New Member
I eventually managed to interrupt the macro at fault with another macro through an unrelated bug(?), so I was able to get rid of that troublesome macro. I would still like to know where exactly the settings are stored because I still haven't figured that out.
In regard to the other "bug," it's with the Stream Deck integration. When you press a key on the Steam Deck using your plugin, the data field remains "active" and doesn't clear after being used; it seems the data field is constantly being sent, and it's value just changes when you press a key with a different data value. So I was able to trigger a different macro that interrupted the whole thing by pressing the key before I even opened OBS. I'm calling it a bug because I'm not sure it's intend to work that way, but it may be better as is lol. Not sure what limitations there are on the Stream Deck side of things, so I'm assuming it may be designed that way for a reason.
Warmuptill
Active Member
The settings are stored as part of the scene collection.
If you are on Windows you are likely to find them here:
C:\Users\<your username>\AppData\Roaming\obs-studio\basic\scenesThe plugin's settings are stored in the
"advanced-scene-switcher" section of the corresponding .json files.Thanks for letting me know.
I will try to investigate when I find the time to.
Unfortunately, there is no complete list of variables supported by the plugin.
In general the workflow for assigning such "values" / "properties" of a macro condition or action to a variable is using the
Set to macro property option of the "Variable" action type.The name of the variable you are assigning the value to can be chosen freely.
For example, here I am assigning the user login of the user that has left the channel to the variable named "My Variable".
If you would like me to add support for additional properties let me know.
Warmuptill
Active Member
Warmuptill updated Advanced Scene Switcher with a new update entry:
Advanced Scene Switcher 1.32.6
Read the rest of this update entry...
Advanced Scene Switcher 1.32.6
Read the rest of this update entry...
Warmuptill
Active Member
That is not possible currently, unfortunately.
I will try to look into it when I find the time to, but I can't promise that support for Kick will be added any time soon.
KaroHolmberg
New Member
(Running with OBS 32.0.4 and ASS 1.32.6)
My issue is that macros over-run each other despite having a rule "and not".
I am running a "base macro" that swaps between multiple camera-scenes. Each camera-scene is active as long as "wait"-command applies. "Wait" delay is individual between 40-120 seconds depending on the scene. This "base-macro" is triggered to start every time a scene named "Trigger.*" runs.
In addition to base-macro I have additional scenes that I need to run. The idea is, that those additional scenes would interrupt the "base macro" as long as they need to run, and after that a trigger-scene is activated and "base macro" would take over and continue.
One of those interruptions is a scene that has an image-carousel. That should run 90 seconds and then activate a "trigger-scene" for the "base-macro" to take over.
The problem is that the "base-macro" takes over when ever a new scene is due to be activated within the "base macro" even though I have a rule NOT to run the macro if "Gallery" is active. To my knowledge I cannot unselect "Run Macro In Parallel to other macros" - as it needs to be running all the time.
The "Base-macro" recognizes the Gallery-carousel - it can be verified here. If I understand correctly, this macro should run if ALL the rules apply. As "Gallery.*" does not apply, this macro should not be activated(?):
Here you can see what "Gallery.Latest" contains:
It should end on "Trigger"-scene that allows the "base-macro" to take over, but instead logs "Booth.Auto"-scene taking over as it is activated by the "base-macro":
We can also see, that the "Gallery.Latest"-macro is still running under the hood: The image-size warnings still appear in the logs although the scene has been swapped to "Booth.Auto".
In some other additional macros I have multiple camera-scenes, so this behaviour causes 1) Base-macro takes over too soon, 2) additional macro takes over the base-macro when camera-scene changes, 3) base-macro takes over the additional macro again - camera angles start to jump irregularly.
What am I missing?
My issue is that macros over-run each other despite having a rule "and not".
I am running a "base macro" that swaps between multiple camera-scenes. Each camera-scene is active as long as "wait"-command applies. "Wait" delay is individual between 40-120 seconds depending on the scene. This "base-macro" is triggered to start every time a scene named "Trigger.*" runs.
In addition to base-macro I have additional scenes that I need to run. The idea is, that those additional scenes would interrupt the "base macro" as long as they need to run, and after that a trigger-scene is activated and "base macro" would take over and continue.
One of those interruptions is a scene that has an image-carousel. That should run 90 seconds and then activate a "trigger-scene" for the "base-macro" to take over.
The problem is that the "base-macro" takes over when ever a new scene is due to be activated within the "base macro" even though I have a rule NOT to run the macro if "Gallery" is active. To my knowledge I cannot unselect "Run Macro In Parallel to other macros" - as it needs to be running all the time.
The "Base-macro" recognizes the Gallery-carousel - it can be verified here. If I understand correctly, this macro should run if ALL the rules apply. As "Gallery.*" does not apply, this macro should not be activated(?):
Here you can see what "Gallery.Latest" contains:
It should end on "Trigger"-scene that allows the "base-macro" to take over, but instead logs "Booth.Auto"-scene taking over as it is activated by the "base-macro":
We can also see, that the "Gallery.Latest"-macro is still running under the hood: The image-size warnings still appear in the logs although the scene has been swapped to "Booth.Auto".
In some other additional macros I have multiple camera-scenes, so this behaviour causes 1) Base-macro takes over too soon, 2) additional macro takes over the base-macro when camera-scene changes, 3) base-macro takes over the additional macro again - camera angles start to jump irregularly.
What am I missing?
Last edited:
Warmuptill
Active Member
Correct, a macro's actions will only be executed if its conditions evaluate to true.
(Note that the conditions are evaluated from top to bottom.)
Unfortunately, it is a bit difficult for me to say for certain what the issue is.
But from what you have described I would assume that the problem might be, that, when a macro starts running its actions, the actions of the previously matching macro are potentially still running, since you have configured all your macros to run in parallel to one another.
For example, here I have set up two macros which loop through scenes "A -> B -> C" and "1 -> 2 -> 3".
They work as expected individually, but when one macro is still looping through its scenes and the conditions of the other macro become true as well, both scene loops will be active at the same time leading to erratic scene switches.
See "A -> B -> 2 -> C -> 3 ...." below:
To work around this problem I have to make sure to stop executing the other macro, which is potentially running in parallel, before starting the actions of the current macro.
This can be done by inserting a "Macro" action at the beginning of each of the macros.
For example, I would add this action to the "A -> B -> C" macro:
Here is the fixed version in action:
I hope that helps!