Posts by jasonvp

    The question is how to integrate this into os x or the NLE's. And how to separate GPL from proprietary code. On windows I am doing this with the COM interface/protocol but there is no such thing on mac os (AFAIK).


    Erk. OK, that's a bit beyond my knowledge.

    Hey Vouk -


    I just recently got myself a new 2019 Mac Pro here at home. It's got the Vega II GPU, which has a hardware VCE on it, if I'm not mistaken. I'd love to help you get this ported over to MacOS properly, if you're game. I'm not all that good with code; my Comp Sci degree has long since gone to waste. But I can keep trying and provide a solid platform for builds, etc.


    If you're interested, that is. :-)

    Hey gang -


    I have both 2.2.0 and 1.1.3 installed with Premiere, and I'm attempting to export a 25Mbit/sec 4K/59.94 video that's about 8 or 9 minutes long. I'm doing so with the HEVC hardware encoder on my 2080Ti card. When I use the older 1.1.3 plugin, it takes about the amount of time I'd expect; if the video is time t, the encoding/exporting is about time t. But with 2.2.0, when I hit the export button, it takes upwards of 2t if not longer.


    17:31:22] ---------------------------------------------

    [17:31:22] Export started

    [17:31:22] ---------------------------------------------

    [17:31:22] Frame size: 3840x2160

    [17:31:22] Pixel aspect: 1:1

    [17:31:22] Frame rate: 59.94

    [17:31:22] Interlaced: No

    [17:31:22] Color range: pc

    [17:31:22] Color space: bt709

    [17:31:22] Color primaries: bt709

    [17:31:22] Color TRC: bt709

    [17:31:22] Sample rate: 48000

    [17:31:22] Audio channels: 2

    [17:31:22] ---------------------------------------------

    [17:31:22] Opening codec: hevc_nvenc with options: b=25000000|bufsize=0|gpu=0|rc=cbr

    [17:31:22] Opening codec: aac with options: b=512000|profile=aac_main

    [17:31:22] Requesting pixel format: yuv420p

    [17:31:22] Applying video filters: colorspace=range=jpeg:space=bt709:trc=bt709:primaries=bt709

    [17:31:22] Frame #0: vRender: 97463 us, vProcess: 5 us, vEncoding: 22738 us, Latency: 120240 us

    [17:31:22] Frame #1: vRender: 187 us, vProcess: 4 us, vEncoding: 8948 us, aRender: 1415 us, aEncoding: 6 us, Latency: 10583 us

    [17:31:22] Frame #2: vRender: 34220 us, vProcess: 4 us, vEncoding: 8214 us, aRender: 70 us, aEncoding: 142 us, Latency: 42676 us

    [17:31:22] Frame #3: vRender: 16161 us, vProcess: 4 us, vEncoding: 8218 us, aRender: 85 us, aEncoding: 132 us, Latency: 24623 us

    [17:31:22] Frame #4: vRender: 32195 us, vProcess: 5 us, vEncoding: 8067 us, aRender: 70 us, aEncoding: 123 us, Latency: 40496 us

    [17:31:22] Frame #5: vRender: 16429 us, vProcess: 4 us, vEncoding: 8353 us, Latency: 24799 us

    [17:31:22] Frame #6: vRender: 33156 us, vProcess: 4 us, vEncoding: 8286 us, aRender: 73 us, aEncoding: 122 us, Latency: 41667 us

    [17:31:22] Frame #7: vRender: 16899 us, vProcess: 4 us, vEncoding: 8364 us, aRender: 74 us, aEncoding: 125 us, Latency: 25491 us

    [17:31:22] Frame #8: vRender: 33480 us, vProcess: 4 us, vEncoding: 8382 us, aRender: 73 us, aEncoding: 126 us, Latency: 42101 us

    [17:31:22] Frame #9: vRender: 14932 us, vProcess: 5 us, vEncoding: 8301 us, aRender: 74 us, aEncoding: 125 us, Latency: 23462 us

    [17:31:22] Frame #10: vRender: 34720 us, vProcess: 5 us, vEncoding: 8372 us, Latency: 43109 us

    [lots of stuff clipped]

    [17:32:10] Exported 1350 frames in 47 seconds. (avg. 28 fps)

    [17:32:10] Flushing encoders and finalizing ...

    [17:32:10] Video and audio buffers flushed.

    [17:32:10] Trailer has been written.

    [17:32:10] Closing encoders ...

    [17:32:10] ---------------------------------------------

    [17:32:10] Export finished

    [17:32:10] ---------------------------------------


    I usually cancel it out, which is why it doesn't run that long. It feels like it's trying to do a 2-pass for some reason, but I don't see that option anywhere in the plugin menus.


    I'm sure I'm doing something stupid here; any guess as to what it is?


    Thanks!

    You can disable pre compiled headers and remove that files.

    That only got me to the next round of errors: it's looking for the SDK_xxx files as inputs (headers and C++ files). Nowhere to be found.

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

    Let me know if I can help as a guinea pig. I'm not much of a programmer so I can't help with the code. But I can build it w/XCode and test stuff out.


    I've been trying so far and failing because it can't find the file SDK_Exporter_Prefix.pch. Is that something that's supposed to be built before hand? Or was it supposed to be included with the source?

    Hey folks -


    I know that this may affect a relatively small number of Voukoder users, but heads up: If you have an SLI system and you upgrade to the new 416.xx driver train from NVidia, you probably won't be able to use the NVENC libraries for any application at all. That means things like:

    • OBS Studio
    • Playclaw
    • and yes: the Voukoder plugin


    will not work with NVENC. Disabling SLI system-wide will allow you to make use of the NVENC libraries again. Also, downgrading back to 411.70 will make everything work again.


    I've spent a couple of days going back and forth between 411.70, 416.16, and 416.34 now. I've confirmed it as much as I'm able to: the 416.xx driver train is risky to upgrade to if you're using NVENC for anything. So beware.


    And yes, I already have a case open with NVidia. Within an hour of me opening it, they already raised it to their Level 2 support folks. I think they realize they screwed up. Stand by.

    Currently the gpu selection parameter is not exposed to the UI, but you have a valid point here. I will add that to the next version.

    You will have a selection to choose between GPU 0-3 but you need to try which one is which.


    I plan to autodetect GPUs with voukoder 2.0.

    I figured out a ... work-around. I think. I was having problems with Premiere Pro latching onto the GT1030 as well, and using the CUDA resources in it (HAAAHAHAHAHA) to try and process the video. It actually caused my PC to crash. Not good.


    Fortunately the NVidia control panel has a way to software-disable the CUDA processing on any given card. So: I did just that. Disabled the GT1030's CUDA processing (HAHA) and re-ran the test. The Vouk plugin snagged ahold of the Titans and encoded my h.265 in no time.


    So apparently by disabling the CUDA processing, I'm essentially telling Premiere something like, "Just ignore that card for anything." Including, apparently, your plugin (which has nothing to do with CUDA).

    Heya -


    Is there a way with the plugin to select with GPU is actually being encoded on? I have an interesting and probably one-off setup here:


    A pair of GTX Titan X Pascals in SLI

    A single GT1030


    The reason for the GT1030 is to power two 4K/60Hz ancillary displays. My main display is the new Asus 4K/144Hz panel, and I also have an Elgato 4K60 Pro capture card connected to the primary Titan's HDMI output. This means, in total, I have 3 4K/60 displays (including the Elgato) and 1 4K/144Hz. A single NVidia card can't push enough bandwidth through itself to power them all at their max refresh/res. So I added the puny 1030 to handle the two 60Hz panels.


    The problem is: Now the plugin is latching onto that GT1030 and... every export is failing miserably. It sends the GPU load up to 100%, and temperature starts climbing, and eventually the GPU says, "Nah. I can't do this".


    I need to force the plugin to latch onto the Titan, not the 1030. Is there a way I can do that? Perhaps with some encoder arguments or something?


    Thanks!