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?
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.
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.
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:
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
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.
It is most likely this is the usual bug Voukoder Pro sometimes has with VEGAS Pro. Sometimes it just wont work. I let my codec getting checked and verified by Magix back then, I verified it myself and had it check by an AI / Kiro. Nobody found anything wrong with it. I am clueless. For me it once helped to reinstall Windows. Reinstalling Magix and Voukoder Pro did not help.
I've added the codec tag selection in the latest release. Can you test if it helps in your case?
That log file looks good! No issues with it!
I'd try to export data exactly as in the scene log!
I found this in the DaVinci logfiles:
[0x00002158] | SyManager | ERROR | 2026-06-22 18:25:46,047 | There is no current clip, SetCurrentFrame failed.
[0x00000330] | IO | INFO | 2026-06-22 18:25:51,220 | Plugin Info :: Voukoder Pro Plugin :: Unable to open Voukoder Pro (Error code #-11)
[0x00000330] | Task | ERROR | 2026-06-22 18:25:51,220 | Error occured during recording of C:\Users\kim30\OneDrive\?????? ??????\??????????????????????????????\Timeline 1.voukoderpro : Codec is not opened yet.
[0x00000ac4] | Task | ERROR | 2026-06-22 18:25:52,842 | Error occured during recording of C:\Users\kim30\OneDrive\?????? ??????\??????????????????????????????\Timeline 1.voukoderpro : Unknown error.
Can you copy the davinci log here too?
Just a summary of the reported open issues:
Voukoder Pro 로그 파일을 공유해 주실 수 있나요? 2026 버전을 사용 중이시라면 “도움말” 메뉴에서 로그 파일에 접근하실 수 있습니다.
Can you copy/paste the error message here and please also attach the logfile.
There was an issue with yuv422p10le export this has been fixed now.
jhukig Your bug is a different bug. I'm still investigating here ...
jackpm18 Do you use yuv422 in 10bit in the V210 format?
Are you guys trying to export yuv422 in 10bit in the V210 format?
The beta version is out now. Please try it and provide feedback here.
Note: This only works with Apple Silicon CPUs (The M-series). x86_64 would be still possible but Apple announced that CPUs will not be supported anymore from 2027 on.