Hm... I'm not aware of making any changes regarding this issue and I guess this is rather a setting in DVRS.
ProRes AW and ProRes KS are different ProRes encoders. The two characters are the initials of their developers. They are both not certified by Apple. In my opinion KS is more advanced and thus marked as "Recommended".
Your NVIDIA GeForce GTX 1660 SUPER (and newer GPUs) does not support encoding interlaced videos. Either deinterlace the video or use a software h264 encoder.
I'll update it as soon as FFmpeg 6.0 is getting released.
Make sure you are using the latest connector for your application(s). For using NVENC (SDK 12) encoders driver version 522.25 or later is required.
AMD AMFh264, hevc: Set a proper default value for constant quantizer (22)av1: Set a proper default value for constant quantizer (110)
Thanks to my all supporters by either Ko-fi, PayPal, Patreon or BTC (33wJ6Jg3KbZA4ZMJMQBFMh7jxWFAnad1Lp). Also thanks alot to the translators. Special thanks to AMD for providing support with testing.
Gronkh, Todd Scarbrough, Schauerland, Michael wooldridge, Chris Woods
Seems like 12.2 has issues with the encoders. I removed it from the website again. Please uninstall and install 12.1. Should be working fine.
When I posted the "Take a look into the future of voukoder" tweet on twitter yesterday a voukoder user asked me "Is the 'Pro' part implying pay2use?". To make it clear:
But currently there are 56000 active users/month using voukoder and we have exactly 16 supporters on patreon (Big shoutout to you, guys!!), but unfortuantely that's not enough for a living.
So there is the question: Is there a better, proper and fair way to finance all of this? I might not be able to have a regular day job and do all the voukoder work in my spare time / weekends / holidays in the future. I'd like to hand this question over to you - the voukoder users: Do you have a realistic idea or suggestion on how this could be financed?
Edit: I'll watch this thread for a while and collect ideas and opinions before posting a reply.
The successor app will have a completely new concept and will be very flexible. Multiple tracks in, multiple tracks out. Just think about what might be possible with this.
... and please participate here: https://www.voukoder.org/forum/thread/1155
Can you post a voukoder log file?
The encoder (GPU or CPU) can only encode as fast as the host software is generating frames.
Yes, the sample rate has to be chosen in VEGAS Pro / the NLE.
(I could add a resampling filter but I'm not sure if it makes that much sense.)
Is it possible to use it in Adobe Media Encoder? If so, how? As I've seen nothing about it on the installation guide.
I just added this information.
And second question. Is Vokouder really faster/Better then just H.265 using Adobe Media Encoder?
Yes. 
Most modern codecs require a frame size where
So a resolution of
[01:58:11] Frame size: 2560x1067might be the issue.
[16:54:44] Timebase: 2116766131/-1841018880 (-0.87 fps)
Can you try to select 60 fps in premieres famerate selection dropdown box?
Looks okay to me.
[20:50:10] Exported 404645 frames in 3627 seconds. (avg. 111.54 fps)It encoded 404645 frames with 60 fps frame rate: 6744 seconds or 112 minutes
What frame rate is it supposed to have?
Please see the pinned thread in this forum.
That (and even more) will be possible, yes.
You can use this table to find the right substitute value: https://docs.nvidia.com/video-technolo…igration-guide/
When installing the connector make sure the path to the Adobe "MediaCore" folder is correct. Sometimes the auto detection is not working properly.
Strange, when I installed the Adobe suite on my new PC all registry entries were properly created.
I'll have a look at this when I am back home again.