FPS drops in-game

[crisvdn]

OBS is relatively lightweight. However, adding the plugin severely increases CPU usage. So much that in-game FPS drops by almost 10 (75->65).

I'm wondering if more people encounter this. And if optimization is possible (maybe specific settings?) so that it hogs less resources.

[phandasm]

You're the first to report this, and I've gone to significant lengths to make sure Waveform is as lightweight as possible (the majority of the CPU workload is already vectorized).
Modern hardware should not struggle with it in the slightest.

Without knowing your setup I can only speculate but it's possible for issues to arise during composition depending on OBS settings (e.g. colorspace conversion), so it might be worth checking your settings.
Also if you're using a CPU based video encoder (x264) it should be noted that scene complexity has a direct impact on performance.
You'll want to set up a controlled test environment to help isolate performance variables.

[crisvdn]

Hi there, thanks for the quick answer.

I have configured OBS to use the NVIDIA NVENC H264 encoder. Scaling the output bicubic 16 samples. Since it uses GPU, I dont think it matters.
I have several sources like streamelements, browser inputs and game capture in the scene.
Regarding plug-in configuration, I can't really give any information. I uninstalled after I saw the performance drop. And my streaming will not be focused on audio that much, so its not that much of a big deal for me to not use it. I just wanted to let you know.

If there's "recommended" plug-in settings that lower the usage, I would definitely try it out. I also wanted to let you know my experience.

For reference:
Windows 11 Pro 64 bit
AMD Ryzen 7 7700X
ASUS ROG Strix B650E-F GAMING WIFI
ASUS TUF Gaming GeForce RTX 4070 12GB OC Edition

[phandasm]

Interesting.
Gaussian filter, FFT size, and volume normalization are the most expensive settings.
You can try turning those down/off, but something is definitely not right if it's actually eating that much CPU.

I'll keep an eye out for any more reports like this, but I don't see it in testing so I'm not sure there's much I can do at the moment.