Page 1 of 1

Recording NVENC/HDR10 Causes Big Frame Rate Hit

Posted: Tue Apr 07, 2020 10:07 am
by jasonvp
I play Battlefield V in 4K/HDR, and I soft-cap the frame rate to 140FPS in BFV's config file. I can generally keep my frame rate in the high 130s, if not bouncing off the 140 cap in most circumstances. This includes recording with OBS Studio using NVENC; but of course OBS doesn't support HDR so the results are awful.

When I record using Action! in NVENC/HDR10, the frame rate hit is noteworthy. I can barely keep my frame rate above 100FPS while recording. And as soon as I stop the recording, the frame rate bumps right back up to 140 or so. I'm not sure what I am or could be doing wrong with it, but it's not usable for me in this state. Using NVENC, even with HDR10 needs to be hitless. Completely and absolutely so. There shouldn't be a single FPS drop while recording.

Is that doable with Action!? Or am I expecting too much?

GPU in question: 2 x 2080Ti cards in SLI, and I'm using GPU 0 to do the encoding. Per my last thread, if I use GPU 1 for it, Action! crashes immediately.

Thanks.

Re: Recording NVENC/HDR10 Causes Big Frame Rate Hit

Posted: Wed Apr 08, 2020 5:53 am
by Piotr
To record in HDR we recommend diabling SLI mode. It should give you better fps.

Re: Recording NVENC/HDR10 Causes Big Frame Rate Hit

Posted: Wed Apr 08, 2020 9:29 am
by jasonvp
Piotr wrote:
Wed Apr 08, 2020 5:53 am
To record in HDR we recommend diabling SLI mode. It should give you better fps.
OK, that's unfortunate, and I'm not going to do it. I get the frame rate I'm after in the games I play only by using SLI. Disabling SLI will tank my frame rate before I even start recording.

No thanks. Get that fixed, please.

Re: Recording NVENC/HDR10 Causes Big Frame Rate Hit

Posted: Wed Jul 14, 2021 5:25 pm
by Watchman
Hi jasonvp,

The thing is that when you use SLI both GPUs are rendering video in AFR mode (Alternate Frame Rendering). But the video encoder is running only on one GPU thus we must transfer image from one GPU to another. This is where the performance hit happens :( It would be super difficult to fix it...