Bug Report Scenes not transitioning properly

L

luxurysedan3030

New Member
I am having an incredibly frustrating problem with my scenes not transitioning correctly. I mainly use two stingers between my scenes. Within the last week or so, I've noticed my transitions are broken. This was before the version 24 update. I have since update to version 24 hoping that it would fix my issue but it did not. I have the log file at the end of this post and a sample of my video output showing the problem while changing scenes. Side note, I did create a new profile and test with new scenes, but I had the same result.

Issue description: There are times I click on a new scene to fire, but the video output stays locked on the current screen. You can hear the stinger audio play, but the scene doesn't change. When I finally do get scenes to change, I may be showing a game play scene and I'll fire the transition and it flashes my facecam screen before the stinger fire, then you see the stinger, then you see the next scene I was actually trying to go to. I've observed this happening with other scenes. Its like OBS gets fixated on a specific scene that will briefly flash in before a stinger fire, a scene that is not what I'm trying to go to, so it shouldn't be coming up at all. All of my scenes should have a stinger (I have a global and then several overrides), so if you see a screen change with either a cut or a fade, it is not playing the correct transition.

https://obsproject.com/logs/qSFaroiN10e6tHbN

https://youtu.be/2rFq-rO3B34
 
Narcogen

Narcogen

Active Member
I don't use stingers so I have limited experience with them, but...

Your stinger media sources are set to use hardware decoding and to not close when inactive, and your logfile shows a small amount of GPU overload:

21:49:06.104: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 31 (0.8%)

That's not much, but I wonder if it could be related to triggering your stingers and then not seeing them play.

You've also got a render delay on your game capture source which also increases load.

21:48:04.414: ==== Recording Start ===============================================
21:48:04.414: [ffmpeg muxer: 'adv_file_output'] Writing file 'C:/Users/deloz/Videos/2019-09-25_21-48-04.mp4'...
21:48:06.616: User switched to scene 'Game Screen'
21:48:10.589: warning: Could not update timestamps for discarded samples.
21:48:10.885: User switched to scene 'Facecam Screen'
21:48:12.582: User switched to scene 'Game Screen'
21:48:15.136: User switched to scene 'Facecam Screen'
21:48:16.555: warning: Could not update timestamps for discarded samples.
21:48:16.595: User switched to scene 'Game Screen'
21:48:18.847: User switched to scene 'Desktop Capture'
21:48:22.527: User switched to scene 'Game Screen'
21:48:25.187: User switched to scene 'Facecam Screen'
21:48:26.522: warning: Could not update timestamps for discarded samples.
21:48:26.698: User switched to scene 'Game Screen'
21:48:28.798: User switched to scene 'Facecam Screen'
21:48:29.980: User switched to scene 'Game Screen'
21:48:32.505: User switched to scene 'Stream Ending'
21:48:35.202: User switched to scene 'BRB'
21:48:37.997: User switched to scene 'Desktop Capture'
21:48:40.719: User switched to scene 'Stream Ending'
21:48:43.927: User switched to scene 'BRB'
21:48:47.830: User switched to scene 'Facecam Screen'
21:48:47.926: warning: Could not update timestamps for discarded samples.
21:48:49.559: User switched to scene 'Bumper Video'
21:48:50.534: warning: Could not update timestamps for discarded samples.
21:48:51.134: User switched to scene 'Facecam Screen'
21:48:52.103: warning: Could not update timestamps for discarded samples.

The above errors are OBS having trouble decoding a media source. It seems to trigger on your facecam screen and the bumper video, and the facecam is one of the problematic ones, yes?
 
L

luxurysedan3030

New Member
Yes, facecam is definitely a problem. I do think I set a rendering delay recently, or at the very least increased the delay somewhat. I can play with that or eliminate it altogether. Is there something I can do to my stingers like not using hardware decoding or to close when inactive? I’m not sure how to do those two things?

Thanks for the help so far!
 
Narcogen

Narcogen

Active Member
In the properties for your media sources you can turn off hardware decoding as well as indicate that the files should be closed when they are not active. Right click the sources and choose Properties.
 
L

luxurysedan3030

New Member
The properties page for stingers is different than a media source in a scene. When you click the gear next to the stingers section, you can choose properties. In there, the properties you are adjusting are things related to the stinger like the transition point and how the audio should be monitored. There are no options for hardware decoding or closing the file when inactive.
 
L

luxurysedan3030

New Member
So I removed OBS and OBS.Live and reinstalled with just OBS Studio. It is still doing the same exact thing. I have noticed that it is only happening with one specific stinger, the one from a new video below. The log file for a different session is also below. In this session, I spent the first half with a stinger that works fine and then the second half of the session with the stinger that is messing up. Now that I know this, I can live without this stinger, but I'd really like to know what the heck is going on and why it's all of a sudden doing this. It could help me avoid this in the future.

Video: https://youtu.be/4HZEbjJFAaU
Logfile: https://obsproject.com/logs/X1uUbpuKS-uiM-hP
 
P

Pedestrian

New Member
I had the slow frame rate issue in OBS 26.0.2 on windows and fixed it by setting transition settings to duplicate scene and sources. No idea why that relates, but it removed the render lag for me. I don't know about it cutting off early. I'm testing 26.1 now, we'll see if it holds. I was moving versions to see where this was introduced, but couldn't figure it since it seemed to be in all versions back as far as 24 for me. Really odd issue. I'm curious if this works for anyone else.
 
P

Pedestrian

New Member
It seems to be fixed in 26.1 using this same method. I can now recreate the render lag at will by turning duplicate sources off. Duplicate scene doesn't seem needed, but I'm still messing with it.
 
gourav_kolhatkar

gourav_kolhatkar

New Member
I am a windows laptop user, I tried everything.. Changing the Stinger format, changing the Transition point, Changing the FPS of Stinger but nothing worked.

FIX FOR ME -
But what worked was so weird, after plugging my laptop to charging everything worked... no lag, no stinger transition cutting.
 
You must log in or register to reply here.
Top