⏵ Home ⏵ Join The Aitum Discord ⏵ Getting Started ⏵ FAQ
Rules
⏵ Rules ⏵ Triggers ⏵ Checks ⏵ Actions ⏵ Queues
Concepts
⏵ Devices ⏵ Integrations ⏵ Global Variables ⏵ Extensions ⏵ Settings
Advanced
OBS Trigger: Source Visibility Changed
The Source Visibility Changed trigger is used to detect when a sources visibility has changed. This trigger is very versatile and can be used in a variety of ways depending on how you fill out it’s Trigger Input fields! Below are a few examples of some different approaches.
If all of the Trigger Inputs are left empty or unselected, the Source Visibility Changed trigger will activate anytime ANY source in OBS has it’s visibility changed.
If all fields are left empty but the Visibility field is set to Hidden, the trigger will activate anytime ANY source in OBS is set to hidden.
Finally, if the Scene, Source, and Visibility fields are filled out, the Source Visibility Changed trigger will only fire for that specified source on the specified scene when it’s set to the chosen visibility state.
Trigger Inputs
Scene
The name of the Scene that the desired source is present in within OBS.
Type | Text (Dropdown) |
Default Fallback | 'Unknown Scene’ |
Required | No |
Local Variable | Yes |
Source
The name of the target Source.
Type | Text (Dropdown) |
Default Fallback | 'Unknown Source’ |
Required | No |
Local Variable | Yes |
Visibility
The state of the source visibility change.
Visible = True
Hidden = False
Type | Switch (Boolean) |
Default Fallback | False |
Required | No |
Local Variable | Yes |
Hidden Variables
Hidden Variables are available as Local Variables within the actions of a rule, but you will not see these fields visually on the Trigger. These can also be used with a New Rule Check, more info here on Checks.
There are no hidden variables for this trigger type.