Vouk

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.

Thanks, that was helpful! (Code, 15 lines) A few things for you to check: Restart the machine (clears GPU state) Check your driver version (nvidia-smi) — make sure it's ≥ 560 for NVENC SDK 13.1 If it persists after reboot, update to the latest Game Ready or Studio driver Run nvidia-smi -q and check for "ECC Errors" or "XID Errors" in the output

Please share the MediaInfo where/when you have changed it.

Can you change the "Codec Tag" property from "apch" to "ap4x"?

Can you please share the MediaInfo of the exported video?

To my knowledge Resolume Alley identifies the codec tag for the correct ProRes variant. Can you test if this build fixes the issue? https://d.voukoder.org/VoukoderPro-x86_64-2026.2.4.msi

Please try the 2026.2.3 build again. I have reused the same version number.

Can you try this build: https://d.voukoder.org/VoukoderPro-x86_64-2026.2.3.msi

Yes, I have to add these global parameters manually. Everything else is auto discovered. I'll keep you updated.

If everything is working fine at your side you don't have to test it. This is just addressing issues other people might have.