That is the typical audio quality used across the board. In your audio, make sure that you have your sample rate set to 48khz. Which that will help to keep your frames up and keep everything smooth. When I have nvenc on, it sits around 1% to 2%. When I had mine on the normal 264 encoder, it was using around anywhere from 7% to 11%. When you start recording, watch the percentage of your cpu that's being used in the bottom right. 4000 to 8000 is 1080p, so I picked the middle ground where it still looks great, but its not to taxing on the viewers end.Īs for your encoder, I would run the nvenc because it takes some of the load off of your cpu. When you upload, some viewers have bad internet or what their watching on can't handle high quality.
I would be very careful with having your bitrate that high. The reason for this is that realtime encoding (when you are recording) is much less efficient and needs a higher bitrate to capture more detail, but when you render your edited video you can use much more efficient, but slower, encoding which can compress the video better while still retaining a higher quality image. When you render your edited videos to upload to YouTube, you should stick with YouTube's recommended upload encoding settings, or go slightly higher, like 15mbps for 1080p60 SDR instead of 12mbps. If you want to see what bitrate it is recording at with CQP, you can open up the stats window in OBS. The smaller the value, the higher the quality, which means higher bitrate and larger file sizes. My recommendation is use the NVENC encoder with the CQP rate control, and use a CQP value between 21 and 23.ĬQP will let the encoder decide what bitrate it needs to use at any given moment to maintain a Constant Quality Profile. For a modern 3D game at 1080p60 you could easily need to record at 50mbps or higher to avoid nasty artifacts and blurry video. Personally, I slap my microphone audio with a compressor and a speech leveler afterwards to get my vocals from fading out as I continue on through a sentence, and allows me to yell without peaking the recording.ĭepending on what you are recording, and what resolution you are using, that bitrate is probably way, way too low. The other guy is right about audio levels, better a bit too quiet than too loud.
Don't set it to 48000 if you're at 44.1 and vice versa it can cause sync issues.
#Best obs studio recording settings Pc
Or just record your entire display, and hope for the best.Īudio - If your PC is set to 44100Hz, for the love of god, keep it at 44100Hz. This requires a higher bitrate to get the same quality image, but upside is that it has a lower framerate loss than CPU encoding. I used to use this exclusively, but when playing Modern Warfare 2019, I ended up constantly getting encoder lag with it and there was nothing I could do other than change my encoder settings.
You can use NVENC when you're CPU bottlenecked, as it does unfortunately, require use of a few CUDA cores. This is the better encoder because while it does use your CPU, it's more space efficient. You can use x264 if you know the game is limited to several cores and you have the spare processing power for OBS's encoder. At least it's not uncompressed AVI, be happy for that. You WILL need an SSD to record at a sufficient bitrate. Be warned- 36000Kbps is about 3 and a half minutes per gigabyte. I used to use 36000 Kbps for ALL footage, and while it's overkill for most games, some really do benefit from that extra bitrate. I can't really see any bitrate issues with it, although I'm tempted to set it to 15 again, even though it gave me performance issues. Okay, so there's two ways of actually dealing with this.Ĩ000 Kbps is a comically low bitrate for local records with editing, mine usually hover around the 12000-40000 Kbps range depending on the scene, and I'm using x264 CRF 16.
0 kommentar(er)
