# Using Video AI with pre 520.xxx NVidia drivers

**URL:** <https://community.topazlabs.com/t/using-video-ai-with-pre-520-xxx-nvidia-drivers/37341>\
**Category:** General\
**Created:** [December 2, 2022, 2:35am UTC](https://community.topazlabs.com/t/using-video-ai-with-pre-520-xxx-nvidia-drivers/37341 "2022-12-02T02:35:32Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![nikhil.shringarpurey](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/n/d9b06d/32.png) [@nikhil.shringarpurey](https://community.topazlabs.com/u/nikhil.shringarpurey)\
**Post date:** [December 3, 2022, 12:51am UTC](https://community.topazlabs.com/t/using-video-ai-with-pre-520-xxx-nvidia-drivers/37341/9 "2022-12-03T00:51:11Z")

</div>

> [The reason and solution posted here.](https://community.topazlabs.com/t/topaz-video-ai-v3-0-5/37247/62)
> 
> Edit: Solution is probably too strong of word. Maybe work-around.

That’s weird since they say you need a newer card, but I am running a 3090, which absolutely, positively has NVENC hardware support via those newer APIs. Sigh.

On a related note, I am adding those command-line options to the encoders.json, but noticed that there are some non-NVENC h.264 profiles in there that do not show up in my options in the program. Is there a setting to force some profiles to populate?

---

_[View the full topic](https://community.topazlabs.com/t/using-video-ai-with-pre-520-xxx-nvidia-drivers/37341)._