Xaymar
commented
6 years ago If you are trying to record 1920x1080 360 FPS, your test shows that at best you'll manage 198.5 FPS. For 1280x720, you should manage 404 FPS at best. This is with a GPU test that only tests raw encoding performance, nothing else. In reality you are bound by a lot of factors.
- OBS Studio (and any libobs based software like Streamlabs OBS) does not support encoding directly on the GPU. Instead, libobs first downloads the frame from the GPU to RAM, then the plugin uploads from RAM to GPU again. This leads to a significant bottleneck called PCI-e 3.0, Chipset, RAM and CPU.
- Encoding requires VRAM throughput, which will be affected by games and OBS rendering. The test you used does not use a lot of VRAM (<1kb). This is the GPU VRAM bottleneck, which you can't get rid of without Vega or later.
- Finally, conflicting resources. While gaming a lot more tasks are required to keep the game running, and also to keep a recording running well. There is not only the GPU->RAM->GPU->RAM overhead, but also the game, file reading/writing/streaming, network, physics and tons more.
Like always, the "performance test" is a benchmark. It does not apply to real world and only shows the potentially best encoding performance with a ridiculously simple 3D scene. Seriously, open up one of the resulting .h264 and .h265 files in VLC and take a look at just how simple that scene is.
Edit: TL;DR: Your GPU might be capable of it, but you are being bottlenecked by the rest of the hardware and software running on your system. Solutions don't exist yet.
AMDJona
Roph
Hey. First off all thanks for improving this plugin more and more. Finally H265 works, before it was always stuck at "stopping recording" , that is fixed now. I can record 1080 60 aswell as 720 240, but 360FPS isn't working. Keeps getting encoding overloaded errors.
This is my obs log:
This is my h265 performance test
ResultsH265.zip
Specs: 6700k RX 580 Windows 10 64bit 16gb ddr4 OBS 21.1.2 64 bit