Beiträge von Vouk

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.

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.

Please add your voukoder log here (after doing the export), then we can take a look.

A half decent GPU is not even the bottleneck of the system. Normally the CPU can't even deliver enough frames per second to put the GPU under full load.

You might want to read this Voukoder Performance Analysis to understand the performance aspect of voukoder.

Key features:

• Intel QSV encoders for both h264 and hevc
• Initial filter support

Fixes:

• Installer: Fixed installation path error when AfterEffects is not installed
• Window sizes should be okay in HiDPI mode now
• Audio is only rendered when needed
• Hopefully fixed assertion error about wxLocale
• (libx264) Fixed 10 bit high profile selection
• (prores) Fixed pixelformat selection

Changes:

• Introducing Intel QSV hardware encoders (h264/hevc)
• Renamed encoder names so they look nicer together
• Added ZScale, BWDIF, YADIF and Unsharpen filter
• (libx265) Added 'ref'option
• (h264,hevc) Added raw muxers
• Doing update check only once on plugin startup

For using NVENC encoders driver version 418.81 or newer is required.

Good idea! I committed 160x100 to GIT.

I guess that the encoder is too new and in an experimental stage. Maybe we should just wait some time.

Zitat von Vogelforscher

But I have also noticed that opening the export window in premiere when compiled in debug mode, premiere is not responding for 1-3 seconds, but then it gets its act together again.

Zitat von Vogelforscher

I think it could be something with the C/c++ optimizations

That is correct, yes.

Version 2.2 will include experimental audio support.