Hello Vouk,
I haven't been logged for a long time 
I discovered a rather unexpected diffusion of Voukoder, on a French pirate site! 
It's difficult to understand any interest for a such diffusion. I don't know how to interpret it, maybe a form of growing popularity? 
On the other hand, it might be useful to have a checksum on official files? it seems futile to me to fight against this, even largest companies cannot manage it.
Hi,
Range QP17 QP16 to QP23 is for H264 (AVC) not for H265 (HEVC) what I spoke about.
This page Youtube's specifications are out of date, it speaks about H264 where as Youtube correctly handle H265 for a long time now.
H265 with B-Frame is the main reason why i bought a GTX1660.
Quantizer 23 is to low for HEVC (H265) ; 23 is standard value for AVC (H264).
The key value for QP is 27 for HEVC, give it a try.
??
There are millions of people who want to upload videos created with Premiere to Youtube but have problems either because their file is too big or because final quality on Youtube is not enough good.
What do you not understand in this simple concept of wanting to upload a video of a reasonable size to have a satisfactory rendering on Youtube?
To say that there is no solution is not an acceptable answer; So I offer mine to the community,
Hello, I disagree with your message...
I'm talking about the weight / quality ratio for Youtube destination, so by also considering upload time which is a problem for many people, therefore lossless formats are irrelevant.
No, the GTX1000 series is not the most efficient for the quality / weight ratio since it does not support B-Frames for HEVC. The object of the discussion is not the encoding speed which I consider sufficient with Nvenc.
GTX 16x0 and RTX cards have almost same performance and quality for encoding,
(and
GTX 1650 Super with GPU TU116 4Go GDDR6
GTX1650 with GPU TU106 4Go GDDR6
GTX1650 with GPU TU116 4Go GDDR6
GTX 1650 Ultra with GPU TU106 6 Go GDDR6
But not
GTX1650 (original) with GPU TU117 4Go GDRR5
GTX 1650 G6 with GPU TU117 4Go GDDR6
)
for the smallest file size possible, use hevc yuv4:4:4, its in voukoder but for now you have to manually input a hundred settings in this post
I do not see the point of doing 4:4:4 starting from 4:2:0 which is largely what is more popular on Youtube. The normal user is not going to do this, he will be content with the complexity of the settings of software like Handbrake.
I think that you are lost in your settings and that you forget the main thing which is not to have fun with tons of parameters but to have an effective generic solution for the majority of users who want to quickly put a video on Youtube and get a good quality.
After many tests and analyse about Handbrake's files, here what I get with what I think it's best setting ratio quality/weight for Youtube. Note that quality is enought for art like painting. The key value for QP is 27.
So here is my EPR file to find these settings in Premiere. It must be placed in your folder:
Windows: C:\Users\UserName\Documents\Adobe\Adobe Media Encoder\12.0\Presets
Mac: Documents/Adobe/Adobe Media Encoder/12.0/Presets
Note that you need a GTX 16x0 or a RTX card, otherwise file will be approximately 2.5 times larger (The reason is the availability of B-frames) that is almost the same size than with H264.
A sample, I get a 207MB file for a 4mn17s video HD1080 at 25fps :
and the original file from Voukoder uploaded to Youtube : https://fromsmash.com/tIhB3eaAMN-ct(available for one week)
Thanks for your feedback if you think there is still room for improvement
I investigate a little about nlmeans denoiser. So the same nlmeans developped by Dirk Farin is implemented with FFmpeg and Handbrake.
There has been an evolution for the version implemented in Handbrake with the support of multithreading. Interestingly enough, the Handbrake source code is available under GNU 2.0 license.
On the other hand I don't know if there is a release of FFmpeg with a nlmeans multithreading version.
Maybe Vouk or someone else is able to find this information?
Dirk Farin's site about nlmeans :
https://www.dirk-farin.net/projects/nlmeans/index.html
About specifique release for Handbrake :
Hello,
I just remade tests with the 3 filters of denoising proposed by Voukoder.
Starting with one minute of HD1080 video at 25 fps, I get the following times with Nvenc :
HQDN3D filter: 31s
removegrain filter: 27s
nlmeans filter: stopped at 3 minutes 35.772ss for 7% of the treatment, i.e. 3071 s for the whole, or an estimated time of 51min 11s
From a point of result, HQDN3D is satisfactory in particular by decreasing its default parameters a little which remove a little too much detail.
Nlmeans gives the best visual result but it is unusable due to a rendering of 0.5 fps, in particular because it exploits a single thread.
There is nlmeans in the Handbrake converter, the processing increases the encoding time but in a more acceptable way since I go up to 12 fps in encoding, this is due to the support of all CPU's threads whose overall load varies from 50 to 75%.
Currently with support for a single thread, this version of nlmeans which requires a lot of computing power is unusable. May be there is another version of this filter, including the one used by Handbrake?
error, message to delete
Also, does the new Voukoder allow for using multiple GPUs to encode simultaneously (aka SLI or NVLink)? I have two GPUs but only one is used during encoding.
Hello,
it seems that only one GPU can be use ; "Multi-GPU" section :
https://devblogs.nvidia.com/nvidia-ffmpeg-transcoding-guide/
Error : message to delete
Hi,
A typo error in your print screen ; it's "available" not "availible"
A detail For encoding...
It's not a GTX1650 but a GTX1650 Super with the same chip for encoding then Turing series, by the way without interlaced support.
The GTX 1650 has the same encoding capabilities as the old GTX10x0 series.
Adobe Photoshop is really effective in optimizing GIF. I used only one very old dedicated GIF software which was more efficient, but I forgot his name and it no longer available.
Vouk develops Voukoder in addition to his work and in the current situation on a completely voluntary basis.
Your comment is therefore particularly unpleasant to read ; He needs help and not that kind of derogatory remark.
His work and the energy put in are remarkable, and everyone must accept his pace of development.
Good luck to find a better encoding plugin.
By reading Vouk's setbacks regarding the site and looking at the home page of the site, IMHO I find that it could be more welcoming, more lively, more attractive. M2C, it is too austere since everything is text. A few images, animations, colors, etc. could make it more attractive and more explicit like some others sites.
It is a real knowledge to achieve this, but by trusting the volunteers perhaps there can be a good surprise ?
Yes I think it would be good for Hitfilm, but I guess why they have trouble answering. The free version Hitfilm Express is voluntarily limited in terms of export capacities, so Voukoder would conflict with their commercial strategy.
For VirtualDub I do not think that the choice of this version is wise, there are more recent forks which allow to import many video formats with many filters included. I have several versions on my PC by cons I can not find anymore the source sites 
Me too, all parameters are saved with the build-in Premiere's function to save setting in export dialogue box.
Tested, it's fixed 
Hi,
I noticed a display bug with the last two releases (1.0.3 and 1.1.0) of the connector for Premiere. It does not cause a problem of operation but of display and it does not directly concern Voukoder but the export window. Special characters in French are not interpreted correctly as if it's not the correct character coding table.
This problem does not exist with the 1.0.2 and earlier of the connector.
Ok :
Wrong :
