Voukoder 9 - RC1

RELEASE CANDIDATE - NOT FOR PRODUCTION USE!

Make sure you are using the latest connector for your application(s). For using NVENC (SDK 9.1) encoders driver version 436.15 or later is required.

Fixes / Changes

• Revived the SVT AV1 encoder (still - but a bit less - experimental)
• Added "temporal mix" + "change fps" video filters
• Updated libx264 encoder to the latest version
• Added "prores_aw" encoder
• Added YUV 4:4:4 (8 bit and 10 bit) support for nvenc_h264 and nvenc_hevc (If the GPU supports it)

Credits

Thanks to my all supporters by either PayPal, Patreon or BTC. Also thanks alot to the translators.

Top Patrons

Gronkh, Schauerland, Terry Mundy, Andreas Martin Aanerud, Michael wooldridge and Chris Woods

Download

• https://github.com/Vouk/voukoder/releases/tag/9rc1

Sorry, I don't have any AMD Pro GPUs at hand. Last time I checked AMD did not react to my question if they can support me with hardware.

Sorry, I don't have time to get involved with another project. (And I also don't have NV12 capture devices).

VP9 / QSV is acually built in already. But the initialization fails always and thus it is not displayed in the UI. Last time i checked (many months ago) the FFmpeg / libav implementation was not even working properly.

It is a bit painful to work with the QSV encoders.

It will be included with Voukoder 9.

Quote from PWC

When using such hw-features one has to know what the GPU capabilities are of course

But many people don't know. There are many "bug reports" like this already.

Unfortunately I can not work full time on Voukoder. I will check this when I find some time.

It should look like this:

Then it appears like this in Resolve:

Yes, I can add this. Not too much complicated. Both yuv444 for 8 and 10 bit. For h264 and h265. But this depends on if your GPU supports this formats. Otherwise you'll get an error when the export starts.

Do you know if there is a public export SDK for AVID available?

The intention was to create a new premiere connector with a later SDK that is not CS6 compatible anymore. So we can still differentiate both - even if both connectors are installed.

I was able to reproduce this. To me it seems the frame buffer does not have the final video stream resolution. But I am not able to get some information (stride) about the image in the frame buffer. I always get "noParam(-6)" ... More hassle with undocumented code ...

That's nice to hear, but still strange.

I've just added support for additional framerates in 1.8.0 ...

The sampling frequency is just a display issue.

So the logfile is looking okay so far, besides that it just stops at some point. This is the time where it crashes?

Can you post a logfile, please? (See the sticky topic about where to find it)

You can override color settings using the "setparams" video filter.

I will also add the "setsar" filter so you can override the pixel aspect ration.

Quote from Lucky13

What time interpolation method should I use in premiere pro?

It doesn't matter as the "magic" happens in Voukoder not in the NLE.

You might want to test the dev prototype. For your purpose you'd have to configure it like that:

Adjust the values for your needs. Please provide feedback. In case of an error message uninstall the current voukoder version first.

https://d.voukoder.org/voukoder-8-tmix.msi

(Only english translation implemented)

"prores"/"prores_aw" is the less advanced encoder, though it might be faster. It accepts only one setting - the "vendor" (which you'd most likely default to "apl0" anyway).

Can add it too if you really want it ...

This will most likely never happen.

What do you exactly mean? What is "full ffmpeg support"?