Also please do not select ridiculous long buffer values. So if something happens that took longer than your selected "Replay Buffer length", you can still cut it out later. I would probably recommend to do a normal recording at the same time. This would for example allow you to save the last 3 headshots you made, or that awesome block you landed, or that great heal that saved your mate, to disk, without having to edit an hour long video later.Ī word of advice though. X is of course the amount of seconds you selected earlier. When something worth saving has happened, you press the hotkey and OBS will save the last X seconds to disk. As you can see, you can of course also still record a normal video file at the same time:Īs soon as you start the buffer, OBS will start the recording but it wont save anything to your disk, until you press the "Save Replay Buffer" hotkey. Now in the OBS interface you can use the small black arrow, right of "Start Recording", to get a little dropdown menu that lets you start the "Replay Buffer" or you can also setup a hotkey to start and stop it.
Then configure the "Save Replay Buffer" hotkey so you can tell OBS to save the buffer to your disk, that is in the Hotkey settings of OBS: For example the last 30, 60 or 120 seconds: You first have to configure the amount of seconds that should be kept in the buffer, that is in the Broadcast Settings of OBS. If you intend editing the videos, a constant bit rate is easier to handle than VBR.This option allows you to save the last X seconds of Video and Audio to your disk on the press of a button. Note it's worth stopping and restarting the recordings regularly, as a crash may corrupt the MP4 file losing all the content. MP4 is more common and preferred for YT uploads so that would be my choice for recorded format to avoid quality loss when converting the MKV to MP4. If you really need small file size, then 3500 but quality suffers below that. For streaming, 3500 is normal and 6000 high but this needs to be squeezed for real-time upload for local recording a high bitrate is better - I suggest starting at 6000 and ensuring your disk drive can cope (SSD easily, a 5400 RPM notebook drive might struggle). The bitrate of 2500 is very low and likely the cause of poor quality. There's a lot of talk that NVENC is lower quality than x264, which is true if your CPU is able to cope. The 'slow' usage preset is theoretically better quality, but not if it overloads your system and causes frame drops (it loads the CPU heavily using x264, if you swap to NVENC the options change). The GTX950M supports NVENC, so setting Encoder to NVENC would move the encoding from the CPU to GPU.
0 kommentar(er)
