Beiträge von Vouk

  • Transkoder: Various minor bugs/issues

    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)

  • Transkoder: Various minor bugs/issues

    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.

  • HDR Encoding Guide for Premiere Pro

    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.

  • HDR Encoding Guide for Premiere Pro

    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?

    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.

  • HDR Encoding Guide for Premiere Pro

    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?

  • Unknown export failure

    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.

  • Unknown export failure

    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?

  • Unknown export failure

    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.

  • Introducing Transkoder - A Batch Transcoding Tool for Voukoder Pro

    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