You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a transition is initiated, whether via the transition button, Stream Deck, or mouse, the transition should execute seamlessly without delays or interruptions.
Responsive Transition Controls:
Transition Button: The transition button should visually indicate when a transition is in progress and return to its default state once the transition is complete.
Stream Deck Integration: Actions triggered through Companion on the Stream Deck, such as "Cut" or "Fade," should consistently initiate the corresponding transitions without fail.
Mouse Interaction: Clicking the transition button within OBS using the mouse should reliably start the transition process each time.
T-Bar Functionality: The T-bar should respond immediately to user adjustments, allowing for smooth manual control over transition progress.
Consistent Performance:
Users should be able to perform multiple transitions in succession without encountering unresponsiveness or the need for workarounds like switching scenes.
Error-Free Operation:
Transitions should complete without getting stuck in an intermediate state, ensuring that all controls remain functional throughout the streaming session.
Current Behavior
Intermittent Transition Issues:
Occasionally, during scene transitions, the transition state becomes stuck.
This occurs roughly every 10 minutes during live streaming sessions where cameras are being cut every 4 seconds.
Unresponsive Transition Controls:
Transition Button:
The transition button in the middle appears to remain pressed and does not initiate the transition.
Stream Deck:
When using Companion, clicking the "Cut" (or "Fade," or any other) action multiple times has no effect; transitions do not occur.
Mouse Interaction:
Clicking the transition button within OBS using the mouse does nothing.
T-Bar Movement:
Attempting to move the T-bar has no impact; the transition does not proceed.
Temporary Fix:
The only workaround to resolve this issue is to switch to a different scene.
After doing so, transitions function normally until the problem recurs.
Summary:
Occasionally, OBS gets stuck in a transition state where the transition button remains pressed and becomes unresponsive.
Both Stream Deck and mouse inputs fail to initiate transitions, and the T-bar cannot be moved.
Switching to a different scene temporarily resolves the issue.
Steps to Reproduce
Launch OBS:
Open the OBS Studio application on your computer.
Set Up Multiple Scenes:
Ensure you have at least two scenes configured (e.g., "Scene A" and "Scene B").
Add necessary sources to each scene to facilitate clear transitions (e.g., camera feeds, images).
Configure Transition Settings:
Navigate to the "Scene Transitions" section.
Select your preferred transition type (e.g., "Fade," "Cut," etc.).
Adjust the transition duration and type as needed.
Integrate Companion:
Ensure Companion is installed and properly configured on your computer.
Link Companion with OBS to manage transition controls.
Use Companion to send changes to transition duration and type, ensuring that these settings are actively modified during the session.
Integrate Stream Deck (If Applicable):
Connect your Stream Deck to the computer.
Use Companion or relevant software to map transition actions (e.g., "Cut," "Fade") to Stream Deck buttons.
Initiate Multiple Transitions:
Begin transitioning between "Scene A" and "Scene B" using one of the following methods:
Transition Button: Click the transition button in OBS.
Stream Deck: Press the mapped transition button on the Stream Deck.
Mouse Interaction: Click the transition button within the OBS interface using your mouse.
Companion Commands: Send transition commands via Companion to initiate transitions.
Perform Rapid or Repetitive Transitions:
Execute several transitions in quick succession (e.g., 5-10 times) to increase the likelihood of triggering the bug.
During this process, actively send changes to transition duration and type using Companion to test if these actions contribute to the issue.
Observe for Unresponsiveness:
After a few successful transitions, monitor the transition controls:
Transition Button: Check if it remains visually pressed and unresponsive.
Stream Deck Actions: Attempt to trigger transitions via the Stream Deck and note any lack of response.
Mouse Interaction: Click the OBS transition button and observe if it initiates a transition.
T-Bar Movement: Try adjusting the T-bar slider and verify if it affects the transition.
Attempt to Resolve the Issue:
When unresponsiveness is detected, try the following:
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
31.0.1
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/p4wi9WRJOgPsWxng
OBS Studio Crash Log URL
No response
Expected Behavior
Smooth Scene Transitions:
Responsive Transition Controls:
Transition Button: The transition button should visually indicate when a transition is in progress and return to its default state once the transition is complete.
Stream Deck Integration: Actions triggered through Companion on the Stream Deck, such as "Cut" or "Fade," should consistently initiate the corresponding transitions without fail.
Mouse Interaction: Clicking the transition button within OBS using the mouse should reliably start the transition process each time.
T-Bar Functionality: The T-bar should respond immediately to user adjustments, allowing for smooth manual control over transition progress.
Consistent Performance:
Error-Free Operation:
Current Behavior
Intermittent Transition Issues:
Unresponsive Transition Controls:
Transition Button:
Stream Deck:
Mouse Interaction:
T-Bar Movement:
Temporary Fix:
Summary:
Steps to Reproduce
Launch OBS:
Set Up Multiple Scenes:
Configure Transition Settings:
Integrate Companion:
Integrate Stream Deck (If Applicable):
Initiate Multiple Transitions:
Perform Rapid or Repetitive Transitions:
Observe for Unresponsiveness:
Attempt to Resolve the Issue:
Apply Temporary Fix:
Repeat to Confirm Intermittency:
Anything else we should know?
I was doing it older version too.
The text was updated successfully, but these errors were encountered: