Question / Help GTX760 + AMD A10 Best settings
- Thread starter Kay Meer
- Start date
Thats not about all the settings, what about the scene buffer time and the CPU Preset?
achmetha
Member
I believe if you are using CRF settings (as detailed in the link), CPU Preset only really affects how compressed your output file is. So if you have a large HDD, you theoretically could change the CPU Preset to Ultrafast, have it use significantly less CPU resources, and only result in a larger file size (this is what I do personally). I think the default for scene buffer time is 700, just leave it at that.
I also add tune=zerolatency to the custom encoder options. Many users would recommend not doing that, but it will also use less CPU resources - and since you will be using CRF settings, you again will only have a larger file size without really affecting quality.
Here is a link to another forum where these settings have been discussed.
http://forum.videohelp.com/threads/...sual-quality?p=2147976&viewfull=1#post2147976
I also add tune=zerolatency to the custom encoder options. Many users would recommend not doing that, but it will also use less CPU resources - and since you will be using CRF settings, you again will only have a larger file size without really affecting quality.
Here is a link to another forum where these settings have been discussed.
http://forum.videohelp.com/threads/...sual-quality?p=2147976&viewfull=1#post2147976
Code:
tune=zerolatency crf=17 aq-mode=2 aq-strength=2.0 subme=6
Last edited:
achmetha
Member
There is no bitrate-limited vbr encoding in that thread at all. The OP wanted to maintain the same visual quality while having increased performance gains for transcoding (which would work exactly the same with live encoding) & did not care about file size. Either way, it doesn't matter because the guide for OBS to uses whatever bitrate necessary to maintain the CRF value, the thread itself just discusses the file size relation to the CPU Preset.
And yes, I use tune=zerolatency to kill processes that use resources for compressing the file (which I do not care about) and replace the resources with subme=6 to gain back some detail lost by using the Ultrafast CPU preset. I realize this can be counter productive (as he can just leave it on the veryfast preset), but this is how I do it.
We could probably go back and forth on settings all day, but the OP of this thread will get high quality local recordings if he uses R1CH's guide alone or if he chooses to use my tweaks.
(Please don't take offense to my post, I'm just trying to justify my settings. If you have suggestions please post them, I'm always trying to improve my settings.)
Sapiens
Forum Moderator
You shouldn't experience any appreciable quality loss by using tune=zerolatency nor gain any quality by using subme=6 when you configure x264 as outlined in the local recording guide. The params affect file size, the encoder is free to use whatever bitrate it needs to hit the quality target you set. If you use less compression the encoder uses a higher bitrate to achieve the same quality level.
If you're concerned about CPU usage while recording it doesn't make sense to use both of those params at the same time. As long as hard drive space isn't a concern just opt for the larger output file and recompress afterwards with a program like Handbrake if you need a file size more suitable for uploading.
If you're concerned about CPU usage while recording it doesn't make sense to use both of those params at the same time. As long as hard drive space isn't a concern just opt for the larger output file and recompress afterwards with a program like Handbrake if you need a file size more suitable for uploading.