I normally use NVENC x264 and it works like a charm. But now since ive had to change graphics card for my main card to be repaired, i either get the error that nvenc x264 couldnt open or Premiere pro crashes when i use any of the other codecs.
nvenc x264 couldnt open
-
-
- Offizieller Beitrag
Yes, i experienced the same issue recently.
i.e. You have saved some NVENC settings for one projects, remove the card (or replace it with an AMD card) and then that encoder is not available anymore voukoder will crash.
I have fixed that already but did not release a new version yet.
-
In this case i had the GTX 1070 - which then had faults. So it send to dealer for repairs. But now i have a GTX 960.
But i succeeded in encoding a video this past weekend with no problems.
I too started doing some testing with my RAMs to see if they caused the problems i thought to be the GFX card, so ive done some overclocking on CPU and RAM. But this has been restored to defaults - 3GHz Ryzen 7 1700 and DDR4 2133 mhz instead of 2400mhz.
But still i have the same two errors. So you are saying there is a fix made, but not released. Can i do something in the meantime? -
Its actually worse now - now it shows this error after i cancel export. But it hangs in the system 5-10 seks after asking for EXPORT.
Ive went back one driver step to the prior nvidia driver. Nothing has changed -
uhhhh i would LOVE to have you release a temp fix
-
- Offizieller Beitrag
What happens if you create a fresh, new project?
-
What happens if you create a fresh, new project?
Trying now!
** EDIT**
Same thing! should I go as far as to reinstall my premiere pro? -
I now tried removing the drivers completely with DDU and rebooting before installing the newest drivers once more. Nothin changes at all. It is like the NEW voukoder since installed that - premiere pro is insistant on NOT being able to figure out the i actually have an Nvenc capable gfx card!
** EDIT **
Just installed 1.2.1 without removing R2 - this works like a charm!
-
- Offizieller Beitrag
Strange ... normally voukoder 1 and voukoder 2 shouldn't conflict with eachother.
-
Vouk
29. Mai 2019 um 15:43 Hat das Label Behoben hinzugefügt. -
I have this problem too! Waiting for 2.0.7 release!
-
Vouk
22. Februar 2022 um 20:59 Hat das Thema aus dem Forum Bug reports nach Closed verschoben.