Question / Help Failed to start recording - Something wrong with the encoders and drivers

KayakWonka

New Member
Whenever I click the "Start Recording" button, this comes up.

5a94d6524ca53ac8047f24b8a25ee866.png


My drivers are fully up to date, and I am using a Nvidia GeForce GTX 1060 graphics card.

a8175d78f28bb6aa86c37ac4f8aba587.png


I've also uninstalled then reinstalled OBS Studio, and it still doesn't work. The NVENC encoder is the only one I can really use since x264 makes the video choppy. Any solutions?

Here's a log too.
 

Attachments

  • 2017-10-22 11-55-24.txt
    11.2 KB · Views: 748

Harold

Active Member
Windows update is not how to get updates to your video card drivers.

Going to the manufacturer's website is.
 

KayakWonka

New Member
Windows update is not how to get updates to your video card drivers.

Going to the manufacturer's website is.

I did. I went to the Nvidia website and downloaded drivers there for my specific model. I've already installed the new drivers...
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
sam686 is correct (I love this community): you used advanced output mode, and then changed a lot of its default settings. It won't start up if you set "level" to that value. Set the "level" value to "auto" as he said and it should fix it. I always recommend setting it to "auto".

There is a good reason why we separate these custom settings with advanced output mode -- it's because tinkering with encoding parameters like this can cause things to not function. I'd highly recommend just sticking to simple output mode and using one of the recording presets -- they automatically configure your encoding settings specifically for recording.

Also one minor thing, and my apologies in contradicting you a bit Harold: drivers directly from windows update are almost always good, Microsoft has the latest WHQL drivers that are both tested and approved by Microsoft, but sometimes they're not the latest and greatest so Harold was generally just concerned that perhaps Microsoft hadn't updated them due to our latest NVENC revision, but I'm pretty sure they have, so using windows update drivers should always always okay.
 
Top