Beiträge von Vouk

Released Voukoder 2.0.7

Fixes:

• (libfdk_aac) Fixed vbr options
• (h264_amf,hevc_amf) Fixed both AMD/AMF encoder and added all missing options
• Selecting default encoder once an encoder is suddenly not available anymore (i.e. GPU change)

Changes:

• (libx265) Added HDR/UHD related options
• (libx265) Added option to enable or disable the HIGH tier
• (libvpx, libvpx-vp9) Added 2-pass encoding option (Vogelforscher)
• Added more performance logging
• Reading PrPixelFormat only once as it's not going to change again

Thanks to the top-tier patrons for the extraordinary support: Gronkh

Yes, This piping feature supported only RGB which is not relevant for the implemented encoders ...

If you select any non 8bit pixel format in the encoder settings ...

• Premiere will render it in YUV 4:4:4:4 with 32bit float precision.
• It will then be converted to yuv444p16 to feed it into FFmpeg/libav.
• And finally converted to the target format (yuv420p10)

This is most likely the reason. Decoding UHD HEVC (with maybe no GPU acceleration) can be tough. But this is a Premiere issue, not a Voukoder issue. You might ask Adobe if there is a way to improve this.

The High render times (3/4 s per frame) could mean that premiere has a hard time decoding the source video. I guess it is a HEVC video, right?

Disabling CUDA is an option if you don't use any effects or filters. If you use effects and filters CUDA could still be faster.

Your render times are extremly high.

Do you use lots of effects and video filters? Please post a media info of your source files.

For your config the performance is okay. The render times in your logfile are pretty low - which is good.

In this case the GPU is relevant, yes.

AMF h.264 is available in 2.0.7!

The encoder "h264_amf" is not available in voukoder when having an AMD video card.

Seems to be libav related:

• http://ffmpeg.org/pipermail/libav-user/2019-May/011838.html
• https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/159

Added the tier option again.

It is not shown in the line you mentioned, but it is shown below in the x265 encoding options.

Tier will be in 2.0.7

In Version 2.0.7 there will be these additional fields (with all their parameters according to https://x265.readthedocs.io/en/default/cli.html):

"colorprim",

"colormatrix",

"transfer",

"output-depth",

"chromaloc",

"hdr-opt",

"master-display",

"max-cll",

"uhd-bd",

"sar",

"range",

"aud",

"hrd",

"repeat-headers",

I guess that will be helpful to you, right?

Updated to 1.3

It autodetects the pixel format and shows it in the result dialog.

Did you try changing the color space too?

Depending on your project and sources you might need to change it.

Made it as small as I could. Also Set some new compiler tweaks. Is it faster than vrpt-1.1?

Working on that right now. Not really easy to get everything set up in Xcode.

Might look into this later. I noticed there are a couple of different mods around.

The question is: Which one is the best? or is it best to have the plain vanilla x264?

I am not sure how do to this and there is no real use case for it. Rejected until there is a good reason for it.

Yeah, Intel contacted me and then want to have it included too. But I need some time for this. Not many people ask for QSV. But I'll keep it on the list.

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