Beiträge von Vouk

    The bit depth is choosen by the pixel format provided to the encoder.

    • yuv420p: YUV, 4:2:0 chroma subsampling, planar format, 8 bit
    • yuv422p10: YUV, 4:2:2 chroma subsampling, planar format, 10 bit
    • yuv444p16: YUV, 4:4:4 chroma subsampling, planar format, 16 bit
    • yuva444p16: YUV, 4:4:4 chroma subsampling, planar format, 16 bit, includes alpha channel information
    • nv12: Same as yuv420p but this time it's in the packed format
    • rgb: Colors are stored in the RGB format, 8 bit
    • gbra: Colors are stored in the RGB format but in the gbr order, includes alpha channel information
    • agbr: Same as above, but in a different order
    • ...

    Please be aware the options are being populated independently from eachother. Just because it's visible doesn't mean this combination will be working. This is a downside of the "options autodetection" feature, which may be improved later. Look at the NVIDIA documentation about the limitations.

    I will provide FFmpeg in its own package for windows under its license. There will be an GPL and an LGPL package to download. But you can create your own package as well (as long as you add the directory to the path variable).

    On MacOS you can install it via homebrew for example.

    Welcome!

    It’s been 8 years since I started writing the first beta of Voukoder. It was an amazing time when this app started making the life for over 65,000 people in so many different branches easier. People like end users working on their YouTube video channels, business users like broadcast freelancers, medical users rendering MRT videos, stock footage photographers , security camera manufactorers and many more. And thanks to all supporters over the last years, especially those on Patreon and PayPal.

    But it also got harder to manage the continuous development of Voukoder besides of my daily job as an employed software developer. So this is my attempt to start a self employed business.

    The existing versions of "Voukoder 13.4.1" and "Voukoder Pro 1.3" will keep working! Nothing will change to them! They will remain free!

    Voukoder Pro

    Now the time has come for a big change: Voukoder Pro 2.0 will switch to a commercial license.

    This was planned initially for Voukoder Pro, but it was not possible to do this in the beginning. One reason was to not include FFmpeg in this commercial licensed package because of the unsolved software patent situation. Well, the solution came to me some months ago: Remove and separate FFmpeg to its own package that is not bundled with Voukoder Pro.

    This has some big advantages:

    1. Voukoder Pro from version 2.0 on needs the FFmpeg 7.1 dynamic link libraries (DLLs) to work and everything (like filters, encoders, muxers and outputs) is auto-detected in the latest release.
    2. You are free to use any variant of FFmpeg you like. This means: You could use encoders and filters that are covered by the LGPL license, the GPL license (i.e. x264, x265, …) or even any commercial license. You decide what to install!
      I can’t guarantee each single feature FFmpeg provides will be working, but feel free to report it to the forum and I’ll see what I can do.

    Licensing / pricing / FAQ

    So, Voukoder Pro 2.0 will be commercial. How much will it cost?

    The perpetual license cost will be 69 EUR for a major version release. So, if you buy Voukoder Pro version 2 this includes all upcoming minor releases. Even if a new major version gets released you can run version 2 as long as you want (and your system is supported) but you receive updates as long version 2 is the latest major version. To continue receiving updates and bug fixes you’d need to buy the next version, and so on. I plan to release one major version per year.

    Will there be a limited time trial version?

    Yes, it is planned to provide a 2 week valid test license.

    Is there any discount?

    Yes, there will be a welcome offer with a discount of 15%. Enter the code “VKDR15” in the order form.

    How do I get the new version?

    You can download it from the website as before.

    How many editors can use that license?

    Each Voukoder Pro license is for one editor seat.

    Can developers integrate it in different NLEs / tools?

    Yes, please contact me.

    When will it happen?

    I've planned to release Voukoder Pro 2.0 on the 1.1.2025. If my lawer gets everything settled until then I'll stick to this date.

    Will there finally be a Mac version available?

    Yes, It is planned to provide a beta version for apple silicone Macs by the announced date.

    Voukoder (Classic)

    As I do not have the time to maintain two entirely different versions of Voukoder I have to announce Voukoder (Classic) has reached its end-of-life status and its successor app is Voukoder Pro.

    This means the latest version is the final version of Voukoder (Classic). You can still use it but I won’t make any more code fixes and -changes (and also no more connectors).

    The next steps ...

    As soon as Voukoder Pro 2.0 gets released ...

    • ... I'll remove the download links and GIT repos.
    • ... I'll also turn off the Google ads in the forum.
    • ... and make the website much less annoying. :)

    Thanks for your understanding.

    Got it running on my M1 MacBook Air!


    Got the components working with eachother.

    • Voukoder Pro - Core
    • Voukoder Pro - Designer
    • Plugin: DaVinci Resolve Studio

    its time now to package it all in one installer app and fix smaller issues.

    Thanks for this detailed analytics. My replies refer to: https://ffmpeg.org/doxygen/trunk/…_accessors.html

    1) I need to access the color information from the filter chain. The methods av_buffersink_get_color_range() and av_buffersink_get_colorspace() have been added recently (I guess). I'm using them in the next version. But I didn't find the methods av_buffersink_get_color_primaries() and av_buffersink_get_color_trc() yet. I have asked the libav devs.

    3) The vendor tag should be written correctly (as reported in MediaInfo)

    4) I'd also need a method to access the field order of the resulting frames. There are filters to change field order or even deinterlace filters. So I guess I'd need that buffersink_get method to get the final field order. Currently this is hardcoded to "progressive".