This "Type" setting here defines in what pixel format DaVinci Resolve sends the frame data to VoukoderPro. Voukoder then defines which other format should be used for the encoder. You can have speed improvements if both formats match up.
But as I think about it ... I could actually automate this and make this a bit more simple.
I've added xiph/vorbis but still have to check the the others.
I'm using the official FFmpeg repositories for building the DLLs. Everything is OpenSource. So you could check the sources I am using, but also the FFmpeg sources itself. They are always linked with each build/release. The Norton Utils had a good reputation in the 90s, but nowadays the reputation is rather dubious. Can you verify this with a different tool?
"Norton Power Eraser is much more aggressive than comparable programs - it may therefore also suspect harmless but unusual software and files on your PC. It is therefore advisable to make a backup before using the program."
For using NVENC (SDK 12.2) encoders driver version 551.76 or later is required. Using FFmpeg 7.0 / LGPL.
Thanks to all supporters by PayPal and Patreon.
Gronkh, Schauerland, Chris Woods, Decoherent, kunzd, Ben Fotovich and Michael
Can you either post a "Scene Test" output or a VoukoderPro log file here?
Thanks for the input. I will try to reproduce it over the weekend and see if i can't provide a quick fix.
FYI: If you set the encoder to use a "cuda"-pixel format you first need to upload the frame from the cpu to the gpu memory using the upload filter. But that only makes sense if you to use more or less complex filter chains on the gpu (and not on the cpu). For a standard GPU accelerated workflow you don't need this.
"alac" is the lossless compressed codec.
"pcm" is the uncompressed codec. There are quite some variants of it:
i.e." pcm_s16le"
Some encoders require a width and height dividable by 4,8 or 16. I guess that has something to do with the macroblocks. I really need to fix this issue.
Does it work if you render it to a resolution of like 1088x1920?
These setting should work:
The download link for 13.1 is: https://github.com/Vouk/voukoder/releases/tag/13.1
VoukoderPro works a bit different than the standard DVRS behaviour.
You need to open the "Scene Designer" first and configure the output workflow first. i.e.:
Then save that scene and select it here:
Its more a less like a preset or template.
It should look like this if Voukoder (Both the main Voukoder app and the DVRS connector) is successfully installed:
Note: You need to configure all settings (codecs, formats, ...) through Voukoder (Configure Voukoder ...)!
In the encoder options you also need to select the 16bit pixel format:
Yes, the plan is to bring VoukoderPro to Windows, MacOS and Linux.
Bringing it to linux is currently in progress. MacOS will follow.
That's what i expected. I'm building the VEGAS Pro plugin with the SDK for Version 18. I need to use an older SDK for 15,16 and 17.
It has not the highest priority at the moment.
And it gets a bit tricky. With switching to the autodetecting method (encoders, muxers and their options) the text is taken directly from FFmpeg (in english). Translating the UI should be possible though.
It's not a bug, this has rather ... never been implemented.
Any hope of Vegas 15 support for VoukoderPro?
Can you please test if it works if you copy the files manually over to the VEGAS Pro 15 directories? I don't have this version myself.
Any hope of Vegas 15 support for VoukoderPro?
Can you please test if it works if you copy the files manually over to the VEGAS Pro 15 directories? I don't have this version myself.
