Audio Transition v1.1 – Entering/Leaving scene triggers appear reversed in OBS 33.0.1
Hello,
I'm experiencing an unexpected issue with
Audio Transition v1.1 on
OBS Studio 33.0.1 (Windows 11).
The plugin works, but the
Entering Program Scene and
Leaving Program Scene triggers appear to behave in the opposite way to what I would expect.
I managed to obtain the desired audio behavior by reversing the trigger settings, but I'd like to report the issue and share the troubleshooting steps I've performed.
1. Intended behavior
I use Audio Transition to control my
Wave DX microphone when switching between two OBS scenes:
- Introduction: mute the microphone.
- Just Chatting: restore the microphone audio, with a gradual fade-in lasting approximately 2 seconds.
Ideally, the microphone should be muted when entering Introduction and gradually restored when entering Just Chatting.
2. Unexpected behavior
With the <span>Mute</span> action configured as follows:
- Take This Action: Mute
- Audio Source: Wave DX
- When: Entering Program Scene
- Restore audio volume and mute state: Disabled
I observed that the microphone did not mute when entering the scene, but instead became muted when leaving it.
I then changed only the trigger to
Leaving Program Scene, keeping the same audio source and action.
Surprisingly, the microphone was muted when entering the scene.
In other words, the triggering behavior appears to be reversed.
I also tested the
Restore audio volume and mute state when transitioning to the next scene option. Enabling it changed the microphone's behavior, but did not solve the underlying issue. The option is unavailable when using the Leaving Program Scene trigger.
3. Troubleshooting performed
To identify the cause, I carried out the following tests:
Test 1 – Original scene configuration
I initially encountered the problem in my regular OBS scene collection, which uses StreamUP Scenes Organiser to group scenes into folders.
The audio effects behaved in the opposite way to their intended configuration.
Test 2 – Two completely separate test scenes
I created two empty OBS scenes outside any folders, each containing its own Audio Transition source: one for muting the microphone and another for restoring the audio.
The problem persisted.
Test 3 – Streamer.bot completely closed
I shut down Streamer.bot to rule out interference from its OBS WebSocket connection and existing automations.
The issue remained unchanged.
Test 4 – Manual scene switching
All scene changes were performed directly in OBS Studio by clicking the scenes with my mouse.
I did not use a Stream Deck or Streamer.bot to switch scenes.
OBS Studio Mode was also disabled.
Test 5 – Only one active Audio Transition source
I disabled the Audio Transition source in the second test scene and kept only the microphone-muting source active.
This ruled out competing Audio Transition actions.
With Restore disabled, I manually unmuted the microphone in the second scene, switched to the scene containing the Mute action, and then switched back.
The microphone was muted when leaving the scene instead of entering it.
Changing the trigger to Leaving Program Scene caused the microphone to mute when entering the scene.
Test 6 – Restore option
I tested the Restore option both enabled and disabled.
When enabled, the microphone could become unmuted when returning to the scene containing the Mute action.
When disabled, the microphone remained muted after the action had been executed.
Neither configuration corrected the apparent trigger inversion.
Test 7 – Scene transition type
My regular OBS setup uses a custom visual transition called
Luma Glow.
Although OBS displays a transition duration of 300 ms, the visual animation lasts approximately 2 seconds. I therefore configured my Audio Transition fade durations manually to 2,000 ms to match the animation.
I suspected that the custom visual transition might interfere with Audio Transition's scene-entry and scene-exit detection.
To test this, I temporarily replaced Luma Glow with OBS's standard
Cut transition.
The trigger issue persisted, although the audio fade felt smoother with the instantaneous scene switch.
4. Current workaround
I reversed the trigger settings in both scenes.
This produces the intended microphone behavior in my setup, despite the trigger names no longer matching the apparent timing of their execution.
The workaround is functional, but I would prefer to understand why this happens.
5. Questions
Could this be an issue with how Audio Transition v1.1 handles scene-entry and scene-exit events in OBS Studio 33.0.1?
Is this a known compatibility issue, or is there another setting I may have overlooked?
I can provide screenshots of the Audio Transition properties and OBS logs if needed.
Thank you for your work on the plugin and for looking into this issue.
