# Did i buy the wrong card? No NVENC capable devices

**URL:** https://discussion.mcebuddy2x.com/t/did-i-buy-the-wrong-card-no-nvenc-capable-devices/3349
**Category:** Hardware Encoding
**Created:** [December 31, 2019, 5:09am UTC](https://discussion.mcebuddy2x.com/t/did-i-buy-the-wrong-card-no-nvenc-capable-devices/3349 "2019-12-31T05:09:42Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Goose](https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/g/5f9b8f/32.png) [@Goose](https://discussion.mcebuddy2x.com/u/Goose)
#### Post date: [December 31, 2019, 8:14am UTC](https://discussion.mcebuddy2x.com/t/did-i-buy-the-wrong-card-no-nvenc-capable-devices/3349/2 "2019-12-31T08:14:19Z")

</div>

Your logs shown that MCEBuddy is detecting your nvenc encoder, however ffmpeg is unable to use it:

> 2019-12-30T21:56:20 MCEBuddy.AppWrapper.FFmpeg → [h264\_nvenc @ 00000000028e5d40] No NVENC capable devices found

However handbrake is able to use it with a decent conversion speed of about 98fps.

Sounds like your graphics driver may have changed and is causing ffmpeg some grief. Try changing your driver to a more stable version or rolling it back.

As for GPU utilization see this topic for more details.

> [@Hardware usage - low %](https://discussion.mcebuddy2x.com/t/hardware-usage-low/3335/6):
>
> Depends on the video filters being used in the profile and the hardware capabilities. Not all hardware support all filters so it ends up using the CPU for that processing activities. Remove all filters from the profile if you want to use more hardware (at the expense of quality). See these topics:

---

_[View the full topic](https://discussion.mcebuddy2x.com/t/did-i-buy-the-wrong-card-no-nvenc-capable-devices/3349)._