Beiträge von Vouk

Zitat von MyPOV

Vouk is the leader and the only developer of this plugin, it's his child. He owes nothing to anyone, he listens to what he wants ; It's the rule, even if it's not your choices, like me you have to accept it.

I see his point. I basically ignored everything version 1 related to get version 2 out. So that I don't have to work on two different versions. Now it's time to go over all pending version 1 topics and sort them out.

Back to topic, please.

As I said these presets above are not fixed. I just want to collect ideas, settings and discuss them. And later on even improve them. I personally would straight use for libx264 "crf=19" and done. But some users are just overwhelmed by all these hundreds of settings. It's too complex for some people. This is not even in development, this is just a theoretical discussion.

Contact me via PM if you want to discuss this any further.

Otherwise back to topic, please.

Agree.

Similar to: https://www.voukoder.org/forum/thread/272

I would like to show the limitations of each level some how. This also affects general video settings (width, height, ...).

At some point it relies on the users knowledge what happens when he sets a level. Still I want to show it somehow.

Zitat von Vouk

Also if you save the the final configuration and load it again you would only have the single parameters selected again and there'd be no connection to the original preset anymore.

What if you first select "slow" then "fast"? Would it set the single params for "slow" and when selecting "fast" it'd overwrite them and add more from "fast?" This is creating a mess.

I'll mark it as rejected for now. I understand your point, but there is no good UI concept. The Voukoder UI works similar to the command line parameters. And other option would be to remove the x264 preset option completely and deal with the single options only. But then... why?

Currently we have the workflow:

• You can use a preset i.e. "slow"
• But then you have the possibility of overwriting single parameters, even if they are already set with the preset.

Zitat von Digeridoo

I am here is not for discussing presets options. I show you that presets are mostly useless. Not you nor me is guru in options. This situation will produce even more useless presets and you can not control it - example is above - you have added a quite strange preset.

Then why are you posting to this topic? I am the project owner, so I decide what way this project goes. This project has both pro and non-pro users. There are alot of users who do not know to choose CRF or ABR, they just want to have a good video on YouTube. And I am trying to make it easier for them.

Zitat von Digeridoo

Also, you are not responded to my first message in this topic. Who will use your custom presets? It is more important then a lot of opened and even not responded bugs and feature requests?

I already asked you to be more respectful and professional with your posts. I am not your paid developer. You will not decide what I am working on.

Zitat von Vogelforscher

I set rc-lookahead=60, b-adapt=2, direct=auto, trellis=2 because in the Voukoder UI these settings didn't change when selecting preset slower.

They most likely never will change. I explained it in the according feature request. This is just how the x264 presets works. The UI is just a tool to build an option string. The simple solution would to not use preset slow but each single option instead. But that would not be simple.

My goal is to have some easy to use presets for users that don't have much insight in encoders, so the can just click on it and have a good, or fast, or whatever result the preset promises. So lets make then as good and as short and non-redundant as possible.

But its good you guys are discussing and improving the presets. But keep this on a respectful and professional level please.

Lets collect some useful presets per encoder here. I will make them available in the voukoder ui later on.

Simply add you reply here and we can discuss and improve presets here.

Please make sure you know exactly what these options are doing. Please don't post guesses. We want to collect really great presets here.

This is going to be really nice. Using variables and math formulas in presets for certain settings. Combined with "Match Source" this is will be epic! I am excited about it. We could even do a bitrate calculation based on width and height.

Please provide the logfile.

Fixed in the next version.

I will check that!

Please send the correct logfile. I have shown it above where to find it.

This is the correct documentation:

ffmpeg version 4.1.git Copyright (c) 2000-2019 the FFmpeg developers
  built with Microsoft (R) C/C++-Optimierungscompiler Version 19.15.26732.1 f├╝r x64
  configuration: --toolchain=msvc --extra-cflags='-MDd -I/c/TeamCity/buildAgent/work/ffmpeg_nightly_debug/build/include' --extra-ldflags='-LIBPATH:/c/TeamCity/buildAgent/work/ffmpeg_nightly_debug/build/lib' --prefix=/c/TeamCity/buildAgent/work/ffmpeg_nightly_debug/build --pkg-config-flags=--static --disable-doc --disable-shared --enable-static --enable-runtime-cpudetect --disable-devices --disable-network --enable-w32threads --enable-gpl --enable-libmp3lame --enable-libzimg --enable-avisynth --enable-libx264 --enable-libx265 --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-amf --enable-libfdk-aac --enable-libvpx --enable-libvorbis --enable-libopus
  libavutil      56. 26.100 / 56. 26.100
  libavcodec     58. 52.100 / 58. 52.100
  libavformat    58. 27.103 / 58. 27.103
  libavdevice    58.  7.100 / 58.  7.100
  libavfilter     7. 49.100 /  7. 49.100
  libswscale      5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc    55.  4.100 / 55.  4.100
Encoder prores_ks [Apple ProRes (iCodec Pro)]:
    General capabilities: threads intraonly
    Threading capabilities: frame and slice
    Supported pixel formats: yuv422p10le yuv444p10le yuva444p10le
ProRes encoder AVOptions:
  -mbs_per_slice     <int>        E..V..... macroblocks per slice (from 1 to 8) (default 8)
  -profile           <int>        E..V..... (from -1 to 5) (default auto)
     auto                         E..V.....
     proxy                        E..V.....
     lt                           E..V.....
     standard                     E..V.....
     hq                           E..V.....
     4444                         E..V.....
     4444xq                       E..V.....
  -vendor            <string>     E..V..... vendor ID (default "Lavc")
  -bits_per_mb       <int>        E..V..... desired bits per macroblock (from 0 to 8192) (default 0)
  -quant_mat         <int>        E..V..... quantiser matrix (from -1 to 6) (default auto)
     auto                         E..V.....
     proxy                        E..V.....
     lt                           E..V.....
     standard                     E..V.....
     hq                           E..V.....
     default                      E..V.....
  -alpha_bits        <int>        E..V..... bits for alpha plane (from 0 to 16) (default 16)

I just tested it. 1 bit actually works.

this one please

Your processor is already at 100% and can't produce more. Please also attach your logfile from the settings tab.

I do not see any NVENC encoders in the dropdown, what's wrong?

There can be many reasons for this.

• You need to have an NVENC compatible graphics card. (See: https://developer.nvidia.com/video-encode-d…-support-matrix)
• You need to have at least one encoder session available. In my case Premiere CC 2017 used all encoder sessions for itself, so CC 2017 did not work. Please use the latest CC 2018 version. CS6 did work, tho!
• Close all other software using NVENC (i.e. OBS)
• Update your video card drivers

How can I see live encoding stats?

How can I see how many NVENC sessions are in use?

Open a command prompt and type:

cd "c:\Program Files\NVIDIA Corporation\NVSMI"

nvidia-smi.exe encodersessions

Exporting is still slow. I expected more speed.

First, using NVENC speeds up encoding, *not* rendering. Rendering is mostly done on your CPU and generates the frames that get fed to the GPU. In most cases your CPU will limit the encoding process and the GPU hardly gets warm. Premiere also requires alot of RAM in this mode - in my case up to 28 GB (out of 32 GB available)! Last but not least a fast SSD is recommended to write the encoded file do disk quickly.

If you have a fast and recent multicore processor it might help to disable both CUDA acceleration and hardware / iGPU decoding in premiere. This could speed up encoding significantly.

It still depends on your project and your encoder settings. If you have a complex project with filters and effects rendering might takes its time. And if frames can't get rendered fast enough the GPU can't make it faster. You still have the option to do get a better encoding in this case: Use a slower encoding preset, or more expensive parameters. Watch your task manager and tune it until both CPU and GPU are on high load.

Still slow?

Sometimes it might be neccessary to uninstall your current display drivers with DDU (https://www.guru3d.com/files-details/…r-download.html) and do a clean new install. For video rendering the Studio Drivers seem to be faster than the Gaming Drivers.

I was reading this on wikipedia for years that only ac-3 and aac are supported. But ...

Zitat

Also MPEG-4 Part 3 audio objects, such as Audio Lossless Coding (ALS), Scalable Lossless Coding (SLS), MP3, MPEG-1 Audio Layer II (MP2), MPEG-1 Audio Layer I (MP1), CELP, HVXC (speech), TwinVQ, Text To Speech Interface (TTSI) and Structured Audio Orchestra Language (SAOL)

... I might have been wrong. Strange.

Welcome to Voukoder 2.0!

This will now replace version 1 which should be considered as deprecated from now on. But version 2 is not finished yet (from a feature point of view), there is more to come soon. There has been alot of beta testing and from my point of view it is stable now and ready for a public release. If you still experience some issues report them to the forum please.

Attention! Users have been reporting some issues with Threadripper processors (or maybe other processors with high core counts). Although this seems to be more premiere related I'm still investigating this. Thus ...

I am looking for a collaboration / a sponsor with a company providing me with hardware to investigate and fix issues like the one mentioned above. Please contact me (vouk@mailbox.org) if you are interested or if you know someone who might be interested in such a partnership. Thanks!

Thanks to all beta-testers, translation providers, my patrons on patreon, all donors.

Special thanks to GRONKH for the continuing support and being the first top patron!

Changes:

• Added french translation (Thanks to MyPOV)
• Added mp3 to mp4 container again

MP3 is not officially supported in an MP4 container, but as it still works i have added this option again.

Previousely discussed here: H.265 HDR