Beiträge von Vouk

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:

Zitat

This 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.

Zitat von morphinapg

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?

Video
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        : hvcC

To 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.

Here you are.

Edit: Removed the download. Please use the official version 2026.1.12 instead.

Would that help you? I have managed (with the help of KIRO) to select PQ and HLG HDR content directly from Premiere. No SETPARAMS filter necessary anymore!

I'm preparing builds right now ...

Of course I will support you with this. I'll debug the entire workflow probably next weekend.

It is designed like this:

The INPUT node selects how the format from the NLE should be interpreted as.

• Either it is set to AUTO then it will be taken as it is delivered by the NLE, you can overwrite to other values though. If i understand you correctly we want to have bt709 here.

Next is the filter chain:

• We feed the frames in the filter chain.
• In:
  • in_color_matrix=bt709
  • out_color_matrix=bt709
  • in_range=tv
• Out:
  • out_color_matrix=bt709 (We want to see an HDR format here, right?)
• Next we feed this frame with the HDR format to the encoder

Is that correct?

Can you try changing this setting in the INPUT node?

I've included the first BETA - but already fully functional - version of the "Transkoder" app in the release 2026.1.10. Check it out!

Right, that was the reason. Not all formats support all encoders. Unfortunately some block even valid encoders. That's why i temporarily disabled the muxer/encoder check in the designer app.

No, this is not normal for a trial version. You should be able to use all encoders even when it is a trial version.

BUT it is necessary to exchange the license code as well each time you switch these versions, did you do that?

A good idea is to install only one version of "Voukoder Pro" at the same time. Each version of Voukoder Pro binds to exactly one major version of FFmpeg. (Version 2 binds to FFmpeg 7, version 2026 binds to FFmpeg 8).

Best would be if you delete everything "Voukoder Pro" and "FFmpeg" related and install the latest Voukoder Pro and the latest FFmpeg afterwards.

A good test to check if everything works is to run the "Designer" app and perform a "Scene Test" using the play button in the toolbar. If that is working fine then all components are properly installed.

If it is not working please send me the Voukoder Pro logs.

Hey everyone,

I wanted to give you a heads-up on something I've been working on: Transkoder (working title) — a standalone batch transcoding application powered by the Voukoder Pro encoding engine.

What is it?

Transkoder is a simple, focused tool for batch converting media files. You drop your files in, pick an encoding scene, set an output folder, and hit Start. It handles the rest.

Think of it as a lightweight frontend for Voukoder Pro's encoding pipeline — without needing a video editor.

Key Features

• Batch queue — Add multiple files via file dialog, drag-and-drop, or copy-paste
• Scene-based encoding — Uses the same Voukoder Pro scenes you already know from the Designer
• Create and edit scenes directly from within the app
• Sequential or parallel encoding — Process one at a time or multiple simultaneously
• Per-item configuration — Each queue item can have its own scene and output directory
• Auto-rename — No overwriting, files get unique names automatically
• Real-time progress — Color-coded progress bars for each item
• Media info — Double-click a file to see detailed codec/stream information
• Cross-platform — Windows (x64 & ARM64), macOS (ARM64), Linux (x64) soon
• Light and dark theme — Follows your system appearance

Current Status

This is currently in beta. The core functionality works already — I've been using it myself for testing.

Some things I'm still working on:

• Polishing the UI/UX
• Better error reporting
• Installer integration

Screenshots

When can I try it?

I'll share a build once I'm confident it's stable enough for broader testing. If you're interested in early access or have feature ideas, let me know in this thread.

Cheers, Daniel

Thanks for your feedback. I have sent you an email.

I have missed to update the the changelog link. Thanks for pointing me to it.

You can see all changes here: https://docs.voukoderpro.com/changelog.html

Out of curiousity: What did you do to make it appear in VEGAS Pro after it did not appear? Many people are still struggeling with this issue and I can't find the reason for it.

To your question: Can you switch the log level to "trace" and recreate the log file you showed above? The original low level error should be between this lines.