Beiträge von Vouk

This is not a bug. These are encoding artifacts and mean you have to optimize your settings.

You try to encoding with 20 Mbit/s. I don't know the resolution or the fps, but most likely this is not enough.

• Try to avoid bit rate based rate controls and use quality / quantizer based rate controls instead (unless you aim for a specific file size i.e. for DVD/BD authoring).
• Don't set a level if you just want to upload to youtube. Levels are needed when your rendered videos should be played on certain hardware decoders. But YT re-encodes all videos again anyway.

Try this simple settings:

profile=high qp=23 quality=quality rc=cqp

And if the quality is bad decrease the "qp" value until you are happy with the video quality.

I will add a taskbar icon in the next version. I'd like to add a download and update notification there and also a popup menu to it.

Do you guys have other ideas for it? Maybe moving the logging view there or something?

Seems this is only happening with x264/x265 encoders. It should be fixed in the next release.

I did some testing and I compared the "Bit Rate" entry in both MediaInfos of ffmpeg and voukoder. In the end voukoder was even lower than ffmpeg.

I had to disable all filters and side data entries in voukoder. I also had to set Color Range to Limited, because it is most likely limited in the source material.

In the end I had:

Voukoder: 1 067 Mb/s

FFmpeg: 1 226 Mb/s

Maybe it is also related to the alpha channel compression.

Fixed.

This will be fixed in the next release.

You can test this. Download and install "Vouk's Render Performance Test". It will tell you the maximum FPS that Premiere can deliver with exporting your project. Just Pure Premier performance, no voukoder, no disk i/o. It just renders the frames with all effects, filters and so on.

Depending on that number of FPS we can think about choosing an encoding solution. Todays GPUs are pretty fast. A single RTX 2080 TI / RTX 6000 can encode like 400-500 FPS of 2K AVC video (depending on the settings). If you want more you should think about special hardware encoder solutions.

The thing is: Voukoder does not speed up rendering. Rendering is done entirely by Premiere and it's rendering engine. Voukoder starts it's work when rendering is done and does the encoding part.

And with encoding the only multi GPU support is that you can select the GPU you want to use for encoding. This is part of the NVidia design.

That is not how it works. But let's keep the dev talk out of a public thread. Lets move it to a private chat.

But that's wrong. It shouldn't happen.

NULL->Reset() is not valid.

Checked mp4 and mkv. I can not reproduce the issue, but I see the issues in the logfile. I'd guess that in your case:

if (audioRenderer)

audioRenderer->Reset();

audioRenderer is suddenly NULL and the Reset() is not called. But i'm not sure how this can happen.

First I'd like to understand it and I would like to be able to reproduce it:

When I encode with this setting:

I get working video and audio. What do I need to do to reproduce that issue?

Yes, but we need to make sure what GPU supports which format. And even... what options are supported then.

Voukoder does build from FFmpeg master and will use it once it got merged.

Too many users apply a "level" even when not necessary. This should be set only in very special case, so we move it out of the standard view.

Yes, looks like it.

So then it's a bug in FFmepg unfortunately. It's nothing we can fix here.

This looks okay from the voukoder point of view. Did you try to do this directly with FFmpeg?

I fully agree. Submit your config file when its ready via git pull.

Voukoder is using FFmpegs "prores_ks" encoder and does not do anything special with that video. Please provide the voukoder logfile and the ffmpeg command line you are using.