Troubleshooting
There are multiple tools and ways which can help you diagnose issues with your setup, which will be described in the following sections.
You can enable additional visual indicators to highlight recently executed macros, true conditions, or executed actions by clicking on the small gear symbol in the upper right corner of the macro tab.
Recently executed macros will be highlighted in green:
Conditions which evaluate to true will be highlighted in green:
Note how the "and not" logic selection affects the value of the second timer condition compared to the first one, while both timers have not yet expired.
To track down issues you can consider pausing macros one by one, to narrow down the problematic macro.
You can also enable a much more verbose log on the General tab.
Its output will be indicating the state of each condition and which actions are performed.
But please keep in mind that these logs can grow pretty fast, so it is not recommended to leave the setting turned on all the time.
In some older versions of OBS the built in log viewer might not be able to handle the logging load.
Example output:
22:47:59.656: [adv-ss] condition timer returned 1
22:47:59.656: [adv-ss] condition scene returned 1
22:47:59.656: [adv-ss] condition audio returned 0
22:47:59.656: [adv-ss] Macro Example macro returned 1
22:47:59.656: [adv-ss] running macro: Example macro
22:47:59.656: [adv-ss] switch to previous scene 'test'
22:47:59.668: User switched to scene 'test'
22:47:59.668: [adv-ss] switched scene
22:47:59.967: [adv-ss] current scene: test
22:47:59.967: [adv-ss] previous scene: LIVE
22:48:00.169: [adv-ss] detected busy loop - refusing to sleep less than 1ms
22:48:00.169: [adv-ss] try to sleep for 50
22:48:00.219: [adv-ss] condition timer returned 0
22:48:00.219: [adv-ss] condition scene returned 0
22:48:00.219: [adv-ss] condition audio returned 0
22:48:00.219: [adv-ss] Macro Example macro returned 0
22:48:00.221: [adv-ss] try to sleep for 298