Can you please share the MediaInfo of the exported video?
Beiträge von Vouk
-
-
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.
-
I'll leave the CROP & CROPDETECT now as it is.
The 2nd MATROSKA has been removed / fixed.Edit: I'll prepare the new builds soon.
-
Also fixed the errors:
- With input nodes not connected to an output node.
- Transkoder: Avoid displying horizontally compacted columns if no scenes.json file is there
- Transkoder: Prevent running the transcoding if no scenes are available.
- Transkoder: Using a QFileSystemWatcher that triggers reload of the scene selections and removed the manual actions (That solves also the Blocking Transkoder all when the Designer is open)
-
About the CROP / CROPDETECT filter:
ZitatThis isn't a bug in your code — it's a fundamental limitation of how FFmpeg's cropdetect works. cropdetect is an analysis-only filter: it detects crop boundaries and writes them to frame metadata (lavfi.cropdetect.x/y/w/h), but it doesn't modify the video stream. The separate crop filter doesn't read that metadata — it uses static parameters.
In the FFmpeg CLI, the typical workflow is a two-pass approach: first run cropdetect to detect values, then apply crop with those values. In a single-pass filter graph (as Voukoder Pro uses), there's no mechanism for cropdetect to feed its detected values back to crop dynamically.
-
This looks like a DaVinci Resolve decoding the source file issue to me. You might want to report this to Black Magic.
-
Yes, I'm discussing this topic with VegasSteve and @VegasDerek right now.
-
Zitat
Can confirm. 4:2:2 worked. 4:2:0 didn't. This was the reason my yesterday tests failed. Looks like a bug.
I'll investigate this.
Edit: Will be fixed in the next build.
-
As an aside, do you think it's possible to incorporate adding external file attachments to the Matroska muxer at all? I use that for youtube's 3D LUT-guided HDR-to-SDR tonemapping system. At the moment I need to re-mux after I've finished with voukoder to attach my LUT. Not the end of the world just time consuming for large files and it would be nice if that was part of the node system.
Yes, it should be possible. But I need to read into it.
-
The thing is: You don't have to mark it falsely as bt709.
Just create a real bt2020 (HDR) project and export it with that Voukoder Pro version. I did this with the "Bars and Tone" clip and it got exported just as it got displayed in the Adobe export preview. Can you check back?
Code
Alles anzeigenVideo ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L4@Main Codec ID : hev1 Codec ID/Info : High Efficiency Video Coding Duration : 5 s 0 ms Bit rate mode : Variable Bit rate : 580 kb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 25.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.011 Stream size : 354 KiB (83%) Writing library : x265 4.2+5-7b3d1f51:[Windows][GCC 15.2.0][64 bit] 8bit+10bit+12bit Encoding settings : cpuid=1111039 / frame-threads=5 / numa-pools=32 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=3 / input-csp=1 / input-res=1920x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / temporal-layers=0 / open-gop / min-keyint=1 / keyint=12 / gop-lookahead=0 / bframes=0 / b-adapt=2 / no-b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=6 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=28.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=255 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf / no-alpha / no-sbrc / no-frame-rc Color range : Limited Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : BT.2020 non-constant Codec configuration box : hvcCTo me it looks like KIRO / AI has figured out what Adobe didn't want to tell me.
P.S.: I'm usually working on my development system over remote access and I doubt HDR is mapped correctly there. I also don't have an HDR capable PC monitor screen.