Vouk, will the prores_ks profile be implemented?
Yes, it is already.
Is the alpha channel already working? If so, how to check?
Currently UYVY422 is used to exchange frames between DVR and Voukoder. AFAIK this does not have an alpha channel. I still need to find out how I can use different color models / pixel formats.
It seems this is an error with the video levels (Limited / Full). I'll provide a fix soon.
I'm getting around half the speed from Resolve's Nvidia Encoding.
Resolve 1440p 60fps: ~240fps while encoding (4:01 for a 15min Vid)Voukoder 1440 60fps with h264 nvidia preset: ~114fps while encoding (7:56 for a 15min Vid)
Well, this is just a first prototype of 2 days work. Nothing has been optimized yet. But I don't think voukoder will ever be faster than the native DVR implementation. The goal is to have more encoders available in DVR - the existing encoder implementations seem to be quite good actually.
Currently the plugin gets the video as 422 and voukoder needs to convert it down to 420. That's something I can still optimize and it should give some more speed.
You have an active filter btw (gamma correction). Removing it gave me 40 more fps.
It runs stable, but I have to restart Resolve after using Voukoder, because the normal encoder wouldn't work anymore.
Looking into that.
Edit: This seems to be working after todays DVR update (17.1.1 Build 9)
My GPU also only gets 50% Usage while enconding with Voukoder. Maybe I did something wrong here? Normal Resolve encoding uses around 99% GPU.
If you set the preset to "slow" it uses 100% GPU.
Still: Voukoder is not the magical tool to make everything faster. But it might offer you more encoders and more options. And I guess DVR uses CUDA in a clever way to prevent lots of copy actions from/to host and gpu.
Here is the first prototype to test. Please tell about your findings / issues here in this thread. (You need to have Voukoder installed, of course).
Extract the ZIP file here and start Resolve.
The plugin will appear here:
Please note: If you like it and if you want to have further support and development consider donating. It will really help me, thanks.
P.S.: It will only work with the studio version of DVR. The plugin does not work with the free version.
Edit: You can find the latest version in the regular voukoder download section now.
The prototype seems to be working quite nice.
After a more in-depth analysis I can say a Voukoder plugin that supports muxed video and audio is possible. Just like with VEGAS and Premiere.
It's just quite some work.
I will dedicate monday (tomorrow) to this topic.
I'll have to find some time to investigate this in detail, but ...
An encoder encodes exactly one uncompressed stream to a compressed stream. (That's what Mainconcept might do). i.e. uncompressed 4:2:0 to compressed h264.
It then returns the data back to DVR so it can package it in whatever container it wants. (i.e. MP4 or MOV)
The big question I need to find out is if DVR also supports an external muxer. So i can get both video and audio (in sync) from DVR, send both to Voukoder and Voukoder handles muxing and outputting.
But from what I've read is that this SDK is an encoder SDK only. It is not a generic File I/O SDK, which I have for Premiere, AfterEffects and VEGAS.
I'll give it a look.
Still, as i've said before, from what i know DVR does not send both Video and Audio to the same plugin. This means Voukoder might not be able capture this and encode both to one muxed output file.
Okay, I got it working now.
But can you tell what features of voukoder you would like to have in Resolve? Or what features yout are currently missing there that Voukoder might be able to add?
Thanks. That would at least give me the chance to investigate this topic. The difficulty with Resolve is that plugins have to be designed like the old VfW - simply just an encoder. No muxer, no combination of video and audio.
I believe that the difficulty with Premiere/Vegas/etc. will be getting the frame to decode at all on the GPU more than anything else, but I could be wrong
This is out of my control. At the beginning of it all I get a pointer to a frame buffer in the CPU addressable memory. So the NLE is doing all decoding, rendering, etc.
Some months ago I was investigating if CUDA could improve the speed of pixel format conversion in the high bit depth mode. I noticed coping frames back and forth between CPU and GPU memory is quite expensive and I should do it as less as possible.
I guess the "cuda" pixel format in FFmpeg contains a pointer to the GPU memory. So I guess with the FFmpeg command line above you're doing exactly what is was talking about as "way 2".
As I am using FFmpeg/libav on the C API level, I still have to figure it all out. But this will be included in voukoder sooner or later.
Yes, I see your point on this. I plan to add this to the voukoder successor actually and I would like to implement this in a smart way.
From what I understand is how the would work in the current voukoder:
I'd love to do it in this way:
I'm trying to find out if the FFmpeg accelerated filters work like the first way to the second way. Do you have any info on this?
It should appear here:
I tried to download 2018 but it is not listed anymore in the "old version" options in CC. Maybe you can check Premieres log file and/or plush its cache.
Thank you for your most intelligent post to this forum.
P.S.: You might have noticed this is not just related to one forum post.
The best way would be if someone could send a boxed version with installation media and license key.
I know there are quite alot users working still with Premiere CS6. Maybe because of the faster and more responsive UI, maybe because it doesn't require a subscription model to use it. Unfortunately Adobe removed all downloads completely a while ago and there is no way of installing it anymore as an "old version" from the creative cloud app. Adobe also rejected my request to provide me an alternative solution to somehow still get CS6.
That basically means I also have to drop supporting CS6 in the Adobe Premiere Connector, too.
But maybe there is one last chance: If the CS6 community would be able to donate me a (fully legal) Premiere CS6 package I would be able to continue testing to make sure later versions of Voukoder are still compatible with it. Illegal ways to solve this matter are not an option!
Thanks.
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.
As Voukoder is very popular in china I'd love to make it more (easy) available for chinese users. I need a chinese contact person that helps me to understand the chinese situation better and support me with setting up various services in china that I can also access from europe. Please contact me if you have experience with this, you can speak good english (or german) and want to help. Thanks.
Thanks to my all supporters by either PayPal or Patreon.
Gronkh, Schauerland, Michael Wooldridge, Kai_307 (Kai C. Ternes), Chris Woods
Remember: It is a good practice you use the trial license first and you test your workflow with it before buying the real license.
You need to install FFmpeg in version 8 first. This package is doing the actual encoding work. Due to licensing (and software patent) reasons this can't be bundled anymore.
Existing Voukoder Pro users might have to uninstall version 7 and install version 8 of FFmpeg.
For windows you can use available FFmpeg 8 DLL installers: Just install it, they'll do everything for you in either GPL or LGPL version. Select only one of them, download it and install it. If you are not using my provided packages you have to make sure the installation directory has been added to the PATH variable.
NOTE: Only the GPL version contains the x264 and x265 encoders.
The macOS version is not ready yet, but will be released soon.
Next you need to install the package below. It also contains the NLE plugins. Just select the NLE Plugins in the "Voukoder Pro" installer and verify the installation directory is correct.
Note: On some systems a reboot might be necessary.
Finally you need to get a license key by clicking on the top "License" menu which you can then enter in the registration dialog.
Please take a look at the Getting Started section in the documentation.
I actually built the new version yesterday evening. The release will be very soon.
