Beiträge von Vouk

Strange ... normally voukoder 1 and voukoder 2 shouldn't conflict with eachother.

I hacked a little tool / plugin together to find out how fast premiere could actually render frames without anything interfering. This is tool is as small as possible and just renders video frames and throws them away again. No file output, no export, no nothing. It tests the premiere part only!

In the end you'll get a little popup telling you the theoretical max. frames per second that premiere is able to deliver for the loaded project / sequence:

(Considering that I am getting like 430 fps with nvenc h264 this is really not bad!)

Discuss the tool and your results here: Vouk's Render Performance Test

With this tool you can also find out if h264 hardware (iGPU) or software decoding is faster on your system. Or is it faster to use the mercury engine, or not? Feel free to test and share your results on twitter.

Please note I am "abusing" the error message functionality at this point to display the results. There is no rendering error. It is just a handy mechanism to display the results right now.

DrumeoRoss Where do you exactly see this resolution?

It might have to do with 32x32 macroblock size. Same is with 1080p and 16x16 blocks. It is actually compressed with 1088 lines in that case.

Edit: Vogelforscher already mentioned the same thing, Thanks.

What happens if you create a fresh, new project?

Yes, i experienced the same issue recently.

i.e. You have saved some NVENC settings for one projects, remove the card (or replace it with an AMD card) and then that encoder is not available anymore voukoder will crash.

I have fixed that already but did not release a new version yet.

Good! If you know how to work with GIT you can clone the repository, copy english.json to polish.json and start translating. You can skip the filter section for now as it is not final yet.

Note to myself: Check the FFmpeg build!

Currently there is no way to hide the parameters for x264/x265. The encoders add it by themselves.

Currently there is no version for Macs.

Edit: But i agree: It's a neccessary step for the plugin. I will look it in the near time.

Unfortunately there is no description of this project. Whats the difference to the regular x264?

You can already encode in 10bit, but its rather slow:

I might look into it once i finished the filter implementation.

Note to myself: https://github.com/obsproject/obs…reaudio-encoder

Salut,

Hey, thank you. I like the "Tornado" logo on the right. I always liked the idea of a "V" style logo, just like "merging many streams, tracks, things,.." into one (file). I will contact you next week after my vacation.

Merci bien!

Zitat von poo

Workaround for this is to use ("VBR" In Voukoder) Quality Mode 5. Downside to this is that it has lower maximum bitrate.

I just realized i did not include vbr=5 in the encoder config. I had options vbr=0 to vbr=4 instead of vbr=1 to vbr=5. Fixed that.

Thanks for this analsis.

There is a possibility to change the cut off frequency of fdk_aac to higher value. But i still recommend to use a lossless codec (if possible) if you really want outstanding audio.

The FFmpeg team recommends to use the builtin aac encoder. If sound quality is absolutely important for you you should use a lossless codec (i.e. FLAC) or uncompressed audio instead.

The old log file is problematic when you are running two (or more) instances of voukoder at the same time.

Please update your NVIDIA video card drivers.

That's what 2 pass (VBR) is for and why you normally choose 2 pass. It first analyses the video for its visual complexity and then adjusts the required bitrate for it. So you can save some filesize. This is not a bug, it is good!

Just like one user said: "I don't like using CRF, I can't reach my usual bitrate with it."

Lets say "The Turing architecture added supports for b-frames with hevc."

Unfortunately b-frames in hevc are only supported with RTX cards.