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.
Beiträge von Vouk
-
-
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 out of the box, covering formats Premiere doesn't natively handle.
Key Features
Format coverage that keeps up with FFmpeg Ingestor discovers formats at runtime from whatever FFmpeg build you have installed. New codecs land in FFmpeg long before Adobe ships native support — now you get them in Premiere the same day you update FFmpeg.
GPU-accelerated decoding (NVDEC, QSV, D3D11VA, VideoToolbox) AV1, HEVC, H.264, and VP9 decode on your GPU through hardware-native decoders — av1_cuvid, hevc_cuvid, h264_cuvid, vp9_cuvid on NVIDIA, QSV on Intel, VideoToolbox on macOS. The plug-in benchmarks each backend per codec and resolution at first import, including the PCIe readback cost, and only uses GPU when it's genuinely faster than CPU. Transparent fallback to software if hardware isn't available or fails mid-stream.
Background prefetch for smooth playback A dedicated prefetch thread decodes up to 16 frames ahead of the playback position into a decoded-frame cache. When Premiere's render threads request those frames, they get a sub-microsecond cache hit instead of waiting for a full decode cycle. Eliminates dropped frames during 4K playback and cuts export time by 20-30% on decode-bound clips.
Configurable frame cache The decoded-frame cache budget is user-configurable via a simple text file (%LOCALAPPDATA%\Ingestor\ingestor.prefs). Set frameCacheMiB=512 for responsive 4K scrubbing, or go higher on systems with RAM to spare. The cache uses deep-copied frames — no GPU memory pool conflicts at any budget size.
HDR done right PQ and HLG sources are delivered through Premiere's 32-bit float pipeline with correct BT.2020 primaries, transfer function, and mastering display metadata. No baked-in tone mapping, no wrong colours — your Lumetri scopes show exactly what's in the file.
10-bit native delivery 10-bit 4:2:0 sources are delivered as P010 biplanar directly into Premiere's native pipeline. No upsampling to 4:4:4, no unnecessary float conversion. Maximum quality with minimum overhead.
Async import with keyframe-aware scheduling Background render threads get their own decoder instances. Premiere's render pipeline can request frames in parallel without blocking the UI. Seek-index acceleration snaps random access to the nearest keyframe for faster scrubbing.
Correct colour, every time ITU-T H.273 colour codes are read directly from the bitstream. Primaries, transfer characteristics, matrix coefficients, and full/limited range are declared to Premiere — not guessed from resolution or assumed to be BT.709.
Three architectures, one binary per platform Native builds for x64, ARM64 (Windows), and Apple Silicon (macOS). SIMD-accelerated conversion kernels (SSE4.2, AVX2, NEON) with scalar fallback. Golden-frame tests ensure byte-identical output across all architectures.
What It Doesn't Do
- No FFmpeg binaries bundled. You supply your own FFmpeg — use whatever build, licence, and version works for your workflow.
- No transcoding. This is an importer, not an encoder. It reads; it doesn't write.
- No formats stolen from Adobe. Premiere's native importers get priority. Ingestor only activates for formats the host declines.
Technical Highlights
- Zero third-party runtime dependencies beyond FFmpeg
- Hardware-native decoders (*_cuvid, *_qsv) selected per-codec with measured end-to-end timing including readback
- Background prefetch thread with independent MediaSource + decoder — no lock contention with the main render path
- Deep-copied frame cache prevents GPU memory pool exhaustion at any budget size
- Portable scalar conversion kernels as the correctness oracle, SIMD only where benchmarks proved it matters
- PPix Cache integration — decoded frames are cached host-side, not re-decoded on scrub
- Seek index built once per clip, persisted as an accelerator file for instant random access on re-open
- ICC profile and embedded LUT pass-through
- Closed caption scanning (CEA-608/708)
- Memory-budget aware: reports per-instance cost through Premiere's Memory Manager suite
Configuration
All settings live in a single text file — no registry, no cloud accounts, no activation servers:
Available options:
CodeframeCacheMiB=512 # decoded-frame cache budget (16-4096, default 128) enableHardwareDecoding=true # GPU decode on/off logLevel=3 # 0=off, 1=error, 2=warn, 3=info, 4=debugGetting Started
- Install FFmpeg 8.x anywhere on your system (or add it to PATH). If you have it for Voukoder Pro you don't need to do it again.
- Drop Ingestor.prm (Windows) or Ingestor.bundle (macOS) into your Premiere plug-ins folder
- Open any file — if Premiere's built-in importers decline it, Ingestor picks it up automatically
Feedback & Issues
Thanks to Schauerland for his extended testing period. This is an early release. If you hit a format that doesn't import cleanly, the plug-in writes a detailed log file with codec info, pixel format decisions, and conversion paths taken. Include that log when reporting issues and I can usually diagnose without needing your media file.
I'll keep you updated. -
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 encounteredI'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
Alles anzeigen2026-08-21 17:11:28 (trace) [FFmpeg:0] Loaded Nvenc version 13.1 2026-08-21 17:11:28 (trace) [FFmpeg:0] Nvenc initialized successfully 2026-08-21 17:11:28 (trace) [FFmpeg:0] Calling dl_fn->cuda_dl->cuInit(0) 2026-08-21 17:11:28 (trace) [FFmpeg:0] Calling dl_fn->cuda_dl->cuDeviceGetCount(&nb_devices) 2026-08-21 17:11:28 (trace) [FFmpeg:0] 1 CUDA capable devices found 2026-08-21 17:11:28 (trace) [FFmpeg:0] Calling dl_fn->cuda_dl->cuDeviceGet(&cu_device, idx) 2026-08-21 17:11:28 (trace) [FFmpeg:0] Calling dl_fn->cuda_dl->cuDeviceGetName(name, sizeof(name), cu_device) 2026-08-21 17:11:28 (trace) [FFmpeg:0] Calling dl_fn->cuda_dl->cuDeviceComputeCapability(&major, &minor, cu_device) 2026-08-21 17:11:28 (trace) [FFmpeg:0] [ GPU #0 - < NVIDIA GeForce RTX 3060 > has Compute SM 8.6 ] 2026-08-21 17:11:28 (trace) [FFmpeg:0] Calling dl_fn->cuda_dl->cuCtxCreate(&ctx->cu_context_internal, 0, cu_device) 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 2026-08-21 17:11:28 (trace) [FFmpeg:0] 2026-08-21 17:11:28 (trace) [FFmpeg:0] No capable devices found 2026-08-21 17:11:28 (trace) [FFmpeg:0] Nvenc unloadedA 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.
-
-
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.
-
Does this build help?
VegasSteve I found out Boost changes it in its logging library.
-
Users having issues like these:
- Your VEGAS Pro version is supported
- VEGAS Pro doesn't show "Voukoder Pro" in the "Render" dialog
- You have "Show All Formats" in VEGAS Pro checked.
- ... but it appears in the About dialog unter Components as a loaded plugin?
- ... and it just SHOULD appear as Render format?
Please try this build and respond here if it works or still fails.
-
I'll check the snap to grid option. I intentionally disabled the zoom in/out option.
You can change the "open on startup" options in the designer preferences.
-
-
Yes, I'll think about it.
-
Yes, I have disable the HDR modes as Premiere can't output them natively. Voukoder Pro can always down convert color formats transparently by selecting the correct "format" in the encoder properties.