Question / Help Error trying to record while streaming in Discord video call

[ThiccBwinch]

Hi, trying to record while streaming which I used to be able to do, but when I'm in a video call on Discord I get an error saying:

"Failed to Start Recording

Starting the output failed. Please check the log for details.
Note: if you are using the NVENC or AMD encoders, make sure your video drivers are up to do date."

Someone in the discord told me there are only 2 NVENC queues and something must be eating them. Turning off discord did solve the problem. I was able to do a workaround by simply switching my encoder to x264 for streaming, but I'd like to use NVENC for both if possible. I have hardware acceleration off in Discord too so I don't imagine it would be using my card for that. Log link below.

https://obsproject.com/logs/9xYCm8I1qYmuIi1H

 

[ThiccBwinch]

I figured it out, will post the solution here for future reference: the video call was eating an NVENC queue because I had the option for using OpenH264 checked on in Discord's Voice & Video settings menu. Turning this off and using whatever their default codec is stopped using my GPU.

 

[koala]

As far as I see it, not the "OpenH264" setting controls the use of nvenc, but the option below: "H.264 Hardware Acceleration". Deactivating the first automatically deactivates the second as well, so you might have not tried to deactivate the second setting while leaving the first one enabled. If you really want to only deactivate Discord using nvenc, it should be sufficient to deactivate the second option and not the first.

This might appear as nitpicking, but with technical things it's important to find the minimal amount of changes. Just find and switch the thing you need to switch, not more, to avoid collateral damage to operation.

 

[ThiccBwinch]

As far as I see it, not the "OpenH264" setting controls the use of nvenc, but the option below: "H.264 Hardware Acceleration". Deactivating the first automatically deactivates the second as well, so you might have not tried to deactivate the second setting while leaving the first one enabled. If you really want to only deactivate Discord using nvenc, it should be sufficient to deactivate the second option and not the first.

This might appear as nitpicking, but with technical things it's important to find the minimal amount of changes. Just find and switch the thing you need to switch, not more, to avoid collateral damage to operation.

It's a fair criticism, but did you reproduce the issue yourself and get it to subside by only disabling the lower toggle? Because only disabling the H264 Hardware Accel was my first move, and the issue remained. In fairness I did not restart both OBS and Discord that first time - but the problem went away without any restarts when I turned off OpenH264 altogether.

 

[koala]

To be honest, I didn't actually check this for myself - I only read the Discord settings. If you say you really need to turn off OpenH264 and it is not sufficient to only turn off H.264 hardware acceleration, then it is so and I will memorize this if someone else is asking this. Thanks for actually trying this out - it's a tedious task.