Short explanation, what component might cause this: Theses lines only appear, if there were any rendering, encoding or bandwidth problems. Number of dropped frames due to insufficient bandwidth/connection stalls:.Number of skipped frames due to encoding lag:.Number of lagged frames due to rendering lag/stalls:.When you see "Total frames output", the interesting part begins.Īfter the Total frames output and Total drawn frames you might see one (or many) of the following lines: "= Recording Stop" or "= Streaming Stop". "= Recording Start" or "= Streaming Start" and Google will tell you how to do that, but here is a guide: If you are using Windows 10, check the beginning of your log file and make sure that you run OBS as an administrator, disable Game Bar and Game DVR:Īero is Enabled (Aero is always on for windows 8 and above) How to check your log file for ~4 common problems From my testing, the difference between "very fast" and "medium" is visible but not very impressive, where as the CPU load on my 8core 16thread Ryzen CPU will jump from barely noticeable to pretty high.ģ. Switching down to "fast" preset will increase the CPU load quite drastically.ĭon't expect wonders here. Keep in mind, that "very fast" preset is the best compromise between CPU load and quality/efficiency. If you have a fast processor or way more CPU cores than you game will utilize, you might be able to choose a slower x264 preset (faster or medium for example) to get even better encoding quality. So GPU based encoders are ideal if you want to do local recordings, where Bitrate is not limitied (in that case I would choose quality based encoder settings like CRF/QCP instead of constant bitrate).įor streaming or lower bitrates in general, x264 will deliver better quality on Very Fast preset than the GPU based encoders, although actual Nvidia cards with Pascal architecture are not far behind. They have only a small impact on your gaming performance, but they are not efficient when it comes to encoding on low bitrates. The GPU based encoders have on thing in common: In most scenarios you might have to test and decide if you prefer the smoothness of 720p 60fps or the less pixelated / blurry quality of 720p 30fps.ĭepending on your CPU and GPU you can choose between x264 (CPU), Quicksync (integrated GPU), AMD AMF or VCE (don't know which one is the newer one) and Nvidia NVENC. Recommendation: Never use 1080p 60fps for streaming, if the content is bitrate-hungry. The higher the resolution and frame rate, the more bitrate is needed, to get decent quality. That's why a setting that might look very good for one game, might look very blurry/pixelated in other games. Your content can be very hungry for bitrate (shooters with many details and a lot of fast movement) or very compression-friendly (Hearthstone, League of Legends.). Of course, bitrate has a huge impact on the quality, but for streaming your bitrate will be limited in some way (upload speed, stream-service guideline, internet speed of your viewers etc.). The quality of your recording/stream is influenced by many factors: Make sure to start your test recording/stream and don't forget to stop that recording/stream, before you upload the log file. If people provide their log file, they often use an empty one (sure it's not completely empty, but the recording/streaming attempt is missing). Here is the guide, how to create and upload your OBS log file: I will try to give a guide-line with this thread. Maybe some one could make a sticky thread for the most common problems and how to avoid them. It seems that many people do the same mistakes over and over again, because they don't understand how game capture, scene rendering and video encoding works. Over the last weeks I was reading and posting in this forum a lot.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |