So what can you do to help with the problem? To be clear, these sources are continuously taking valuable resources from your computer. The problem with this, for most sources at least, is that these sources remain active regardless if they are in the scene that is currently active. For example, you might have numerous camera feeds, images, browser components, etc., each doing something different or appearing different between scenes. If you’ve got a lot of scenes in OBS, you’re probably going to have a lot of sources.
Create Less Sources and Re-Use More Sources The Twitch Inspector should be used prior to starting every stream. While this inspector doesn’t let you see the actual stream, it acts as a test mode with metrics in terms of frames per second, bandwidth, and a bunch of other useful things. In this tutorial, I’m going to walk you through some of the things that can be improved in Open Broadcast Studio to give you better stream performance on the popular content streaming networks.īefore diving into the what should we change and how should we change it, I wanted to point out that Twitch offers inspector tooling to help measure the quality of your stream. I was able to resolve these problems by changing the way I streamed with Open Broadcast Studio (OBS). The first few streams had a large amount of framerate stuttering, audio and video synchronization issues, and computers sounding like airplane jet engines. I stream a few times per month on Twitch using The Polyglot Developer. The reality is that there’s a little more to it, more so around stream quality and performance. Streaming is so popular that you might think it’s as easy as opening your web camera and clicking stream.
When I say streaming, I mean live streaming, not publishing pre-recorded videos to be watched on-demand. So you’ve decided that you want to start streaming content to Twitch, YouTube, or similar.
0 kommentar(er)
