Posts by Vouk

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.

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:

pasted-from-clipboard.png

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.

We need to be really carefull with SVT. It seem it is highly experimental. Building the libs work fine now. But when doing an FFmpeg build ...

• VP9 is using pthreads.lib and m.lib (Does not exist on windows)
• The libs conflict with eachother
• There are unresolved symbols from some missing dependencies

We should be wait for a stable release.

Edit: svt-hevc has been successfully compiled in.

After Effects ist aber generell recht langsam beim Rendern der Frames. GPU Enkoding macht dort nicht viel Sinn.

Welcome to the forum! What is your current GPU?

The vRender times are way too high. Unfortunately you cut off your system information.

Ideas:

• Clones a local GIT repo
• Shows a grid that contains the translation key, the english translation and a field for the new translation value in the target language
• Helps the user with a suggestion of an automatic translation (from i.e. Google Translation or deepl.com)
• Commits changes to the local repo
• Once the translations are completed create a GIT pull request
• Make it as easy as possible and avoid too technical terms (i.e. just say "Save" instead of "git commit", "Update" instead of pull, etc)

I'll take a look at.

pasted-from-clipboard.png