Vouk

I don't understand what you mean with "32 bit float", can you explain this? I'm using this "32 bit float" in Voukoder Pro usually only for audio encoders to send the audio data from the NLE to Voukoder Pro, where do you see this for video? Use the next higher value when in doubt.

What if you change the "Quality" value? Does this have some effect?

Good Idea! But I installed the v143 CRT libraries for ages by default with the installer. I have upgraded this today to the latest v145 version as i have changed/updated the C++ version some times before without upgrading this file. Please give me a feedback if this helped in the 2026.2.5 version.

The likely culprit is a mismatch in the color range description. The buffer source declares range=1 (full range), but the scale filter is told in_range=tv (limited range). There's also a possible height issue — 1620 is unusual and the scale filter here isn't actually resizing, just converting format/range, so a scale init failure often traces back to inconsistent color parameters like this range conflict. Error -11 is EAGAIN, which FFmpeg surfaces when the graph can't be configured with the…

Yes, sorry, you are right. I was confused with NVidia's naming strategy and mixed up the Quadro RTX 4000 series with the usual gaming series (like RTX 4090, 4080, and so on). To be completely open, this depends entirly on the FFmpeg you are using. The listed formats in the designer are auto detected and read from FFmpeg. So you can either build your own FFmpeg (in version 8, dynamic libs, NVidia headers in at least version 13.0) or you have to wait for an update from me (if you prefer to use…

Hi, You've actually already discovered the important part yourself. Let me try to explain why it behaves the way it does, and answer your final question. 1. Why AMF replaces HLG with PQ and drops the matrix This is a limitation of the AMD AMF HEVC encoder itself, not of Voukoder or your Scene setup. The color node in your Scene (range: tv, matrix: bt2020nc, primaries: bt2020, transfer: arib-std-b67) is correct — that's exactly what you want. But hevc_amf doesn't reliably write the VUI color…

The hevc_nvenc encoder is exactly the NVIDIA (GPU) HEVC encoder. But my info reports that yuv422 10 bit got introduced with the rtx 50 series, not with the rtx 40 series. […]

Starting with this build, Ingestor ships FFmpeg with the installer. You no longer need to grab FFmpeg yourself or add anything to your PATH — a complete, matching set of libraries is placed right next to the plug-in. A few things worth knowing: It's FFmpeg 9.x (stock LGPL, no GPL/non-free components), built with hardware-decode backends enabled. AV1 works out of the box. The bundled build includes the dav1d software decoder, so AV1 clips (OBS captures, etc.) decode even without GPU AV1…

The fully featured test version will most likely be available to down load next weekend.

That's the remaining strange issue with VEGAS Pro. Technically both components are identical! Maybe @VegasSteve knows something about this?

In the Pro version only the bold printed values will be used. In fact if they still match their default values they will be ignored. you can also see the this in the preview: only the values that are mentioned there will be finally applied.

Thank you! I'll keep investigating this issue.

Ingestor - FFmpeg-Powered Media Importer for Premiere Pro Platforms: Windows x64, Windows ARM64, macOS Apple Silicon Premiere Pro: 26.0+ FFmpeg: 8.x (user-supplied, any build — GPL, LGPL, or custom) What is Ingestor? Ingestor is a Premiere Pro importer plug-in that uses your existing FFmpeg installation to bring virtually any media format into your timeline. If FFmpeg can decode it, Ingestor can import it — no transcoding, no intermediate files, no waiting. 165 container families supported…

No, the minimal driver version must be met. Any higher driver version is alright. 2026-08-21 17:11:28 (trace) [FFmpeg:0] dl_fn->cuda_dl->cuCtxCreate(&ctx->cu_context_internal, 0, cu_device) failed 2026-08-21 17:11:28 (trace) [FFmpeg:0] -> CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered I'm wondering if maybe your GPU is defective. That would explain this error (and it is also not used by VEGAS Pro). I haven't seen this before.