Question / Help Glitchy Transition When Switching Scenes

[TheDrummingPC]

Hey, I'm new here but dug around quite a bit to find this issue and came up empty.

I've got an issue with Scene Changes, using the default fade transition. I'll explain by example. Say I have 3 scenes:
- Scene A
- Scene B
- Scene C

Switching from A to B, there's no issue; the fade works great. Now move from B to C and suddenly there will be a flash of Scene A (lasts for about 1 second) before properly fading to C. Same thing happens in reverse, go from C to B and it'll flash the old scene A, before going to B. Throw in some changes to more scenes, D, E, F and the issue will move around so A isn't the only one flashing any more, but any old scene that wasn't just in view.

This is incredibly frustrating because I'm always switching between scenes and am trying to create a professional broadcast.

I should note, I've got fairly high CPU usage and a lot of scenes with videos. The overall OBS setup is fairly complex and I'm nearly certain this wouldn't happen if I had just very basic scenes. However, I've trimmed everything down to the minimum and am making sure things are unloaded when they aren't shown on scene to the point where the stream output is smooth and looks great (aside from this transition issue).

One final note, I couldn't replicate this issue when I disabled the webcam and capture card, but once those are activated and I'm live, the issue pops up every single broadcast.

Any ideas for troubleshooting? Any ideas what the problem could be? Also wondering if this issue would just disappear if I had a better CPU or moved all media sources to M.2 for faster loading. My main priority is getting this to go away while keeping my scenes in tact.

(I can upload a log if I can replicate the issue while not live)

 

[DrDerkington]

I'm having this same issue, can't figure it out. Currently running the latest version of OBS.

 

[DrDerkington]

Update on issue. After disabling the "low light compensation" and un-checking "Deactivate when not showing" feature on my webcam I have not been able to reproduce the issue since making this change. This may have solved the issue for me.

 

[TheDrummingPC]

Update on issue. After disabling the "low light compensation" and un-checking "Deactivate when not showing" feature on my webcam I have not been able to reproduce the issue since making this change. This may have solved the issue for me.

That's interesting, but in my case "deactivate when not showing" is critical to save on CPU resources. I'll test turning off low-light compensation tonight. Will update later.

If it comes to it, might have to brute force it with a better CPU.

This does make sense though, since I could not reproduce the error with the camera disabled.

 

[DrDerkington]

Update: Further testing shows the issue did not get resolved with "deactivate when not showing", but I found a way to reproduce the issue pretty consistently. I have all of my scenes setup with hotkeys. If I only use the hotkeys, it works fine. If I switch any of the scenes using my mouse by clicking on the scene that's when the problem gets triggered for me.

Update 2: Further testing shows it only happens when I switch to a scene that I also use inside of multiple other scenes.

Example. I have a source scene z and scene y that I use as a HUD that I keep inside scene A, scene B, and Scene C. That way if I want to change an element on that HUD it changes it on all of them. If I switch to the source scene z or scene y and then back to scenes A, B, or C that is when I have the problem. I am able to reproduce this every time.

 

[TheDrummingPC]

Oh wow, that's exactly what I'm doing too. Scene z (my ripsaw, full screen) is a scene of its own, but then I frequently switch from that to another scene (scene A) with scene z inside it. I think this might be justification for a bug report.

I wonder if things will work if I make a sample set of scenes with no hotkeys. Did you try that? That might be a test I attempt a little later.

Does low-light compensation have anything to do with what you've found still, or was that just a coincidence?

 

[DrDerkington]

I think it may have just been a coincidence of how I was testing it at first, but ultimately it had no effect on the actual issue we are experiencing. It did give me a bump in my cameras frame rate however so I am leaving it off.

 

[Jammy_Dodgerr_]

Hi guys,

was a solution ever found with this?

I am getting an issue where I am changing from scene A to B, after the transition I get a frame pop up from A for a brief time then it disappears

 

[MMedia]

I wonder if this issue has to do with the version of OBS? I am using the same setup for scenes for couple years and now the problem is occurring. I have accepted a couple of latest OBS updates more recently.... but I couldn't say exactly when the issue started. I do know that I have installed the latest OBS on a brand new computer, but I copied the \appdata\roaming\obs-studio folder (Windows) to the new computer to transfer all my settings and the exact same issue is occurring on the new computer.

Guess I may have to blow away the setting folder on the new computer and see if the issue occurs in a virgin setup. *sigh*

 

[MMedia]

I wonder if this issue has to do with the version of OBS?

Okay you'all. After that last post I decided to roll up my sleeves and figure this bit*h out. Here is what I found.
Any single source in the scene that has the "deactivate when not showing" option selected can cause the effect we complain about here. In my case I had a Twitch Extension browser URL source configured as such. Uncheck and problem solved!

The only use I could ever see for the option is when you are using underpowered machines. With all the capability of today's OBS, unless you are doing some overly simplistic broadcast, you aren't using a capable computer if you have to use the feature to save CPU cycles and memory.

 

[synthercat]

I fixed it in a crazy way, I had scene A & B
A : part of my monitor + audio
B : part of my monitor + audio + cam
...and I had that glitch. I duplicated A & B as C & D which had NO GLITCH!!!
I removed A & B and renamed C & D and I it was done, working like a charm.