Beiträge von Vouk

  • NVidia Hardware Encoding (NVENC)

    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.

  • Container / codec combinations (was R2_beta2)

    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.

  • Released Voukoder 2.0

    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

  • vokouder r2.0 beta3 - GPU at 20% ( beta2 95/98%)

    There are some issues with your system, yes. I have no clue why it is like that. It could be many things:

    Maybe ...

    • with AMD CPUs at all
    • with Threadripper CPUs
    • with high core counts
    • with specific Premiere settings? Hardware decoding?
    • ...

    I did not get any hardware donations and I can't afford buying any test equipment. So I can just guess here.

    But as you have a working Visual Studio IDE and the voukoder sources I'd recommend that you try to find the issue. Try to find that slow spot.

    Try to profile it.

    Edit:

    My i7-4770 looks similar but still faster than your Threadripper:

    Code
    [20:01:44] Video frame #2297: Render: 808 µs, Process: 6 µs, Encoding: 1884 µs
[20:01:44] Video frame #2298: Render: 56 µs, Process: 3 µs, Encoding: 2543 µs
[20:01:44] Video frame #2299: Render: 19 µs, Process: 4 µs, Encoding: 1799 µs
[20:01:44] Video frame #2300: Render: 16 µs, Process: 3 µs, Encoding: 1747 µs
[20:01:44] Video frame #2301: Render: 9 µs, Process: 3 µs, Encoding: 3062 µs
[20:01:44] Video frame #2302: Render: 17 µs, Process: 3 µs, Encoding: 2303 µs
[20:01:44] Video frame #2303: Render: 8254 µs, Process: 6 µs, Encoding: 1191 µs
[20:01:44] Video frame #2304: Render: 654 µs, Process: 5 µs, Encoding: 1199 µs
[20:01:44] Video frame #2305: Render: 991 µs, Process: 5 µs, Encoding: 1220 µs
[20:01:44] Video frame #2306: Render: 227 µs, Process: 5 µs, Encoding: 1145 µs

  • vokouder r2.0 beta3 - GPU at 20% ( beta2 95/98%)

    It's interesting to see that every 4th frame is slow.

    [18:46:11] Video frame #12935: Render: 14392 µs, Process: 6 µs, Encoding: 861 µs

    [18:46:11] Video frame #12936: Render: 75 µs, Process: 3 µs, Encoding: 768 µs

    [18:46:11] Video frame #12937: Render: 69 µs, Process: 2 µs, Encoding: 1461 µs

    [18:46:11] Video frame #12938: Render: 64 µs, Process: 4 µs, Encoding: 1841 µs

    Average FPS: 205

  • vokouder r2.0 beta3 - GPU at 20% ( beta2 95/98%)

    Just to clarify:

    Render: 15 µs <- Voukoder has no impact on this, it is entirely premiere

    Process: 5 µs <- Voukoder has high impact on this

    Encoding: 676 µs <- Voukoder has small impact on this. Mostly libav / FFmpeg

    Voukoder is very performant with 8bit formats (esp. yuv420p). Formats with higher pixel depths require an expensive frame conversion and are slower.

  • vokouder r2.0 beta3 - GPU at 20% ( beta2 95/98%)

    In voukoder 1 the settings were defaulted to proper values. Even if you did not change it they were already pretty optimized. In version 2 you start completely from zero. So you can not really compare both to eachother unless you are very careful and you are very sure about what values the nvenc gets called with.

    But even then:

    gpu=0 preset=slow qp=15 rc=constqp

    Code
    [16:23:21] Video frame #13077: Render: 13 µs, Process: 3 µs, Encoding: 1429 µs
[16:23:21] Video frame #13078: Render: 12 µs, Process: 3 µs, Encoding: 1701 µs
[16:23:21] Video frame #13079: Render: 19 µs, Process: 4 µs, Encoding: 1532 µs

    gpu=0 preset=fast qp=15 rc=constqp

    Code
    [16:24:15] Video frame #10041: Render: 17 µs, Process: 5 µs, Encoding: 594 µs
[16:24:15] Video frame #10042: Render: 10 µs, Process: 2 µs, Encoding: 492 µs
[16:24:16] Video frame #10043: Render: 15 µs, Process: 5 µs, Encoding: 676 µs

    It always depends on your video sources / filters / effects / almost everything

    On my system CPU and GPU are at 100% load, and it is encoding h264 and 1152p with 430fps. I can't see anything slow there. It is all about the settings.

    I would like to really have some nice settings to create some presets, but i need to find someone who has really insight in encoder configuration to create the best presets available to make this easier for users.

  • Released Voukoder 2.0 (BETA)

    BETA 5

    Fixes:

    • (fdkaac) Fixed storing basic settings
    • (libx265) Fixed strategy selection
    • (libx265) Added 2-pass functionality
    • Creating a unique passlog file for each voukoder instance

    Changes:

    • Added german translation
    • Removed libav low-level log output and improved encoding speed
    • Added more high level logging
    • Moved language selection to settings category