Alright. I can see you created and configured the "4K" scene. That looks good to me. What did you do next in the "Render ..." dialog in VEGAS Pro?
Did you ...
I tried work on this just now, but i can't repoduce the issue anymore. I'm a bit confused. I also noticed the code didn't change much in the recent years.
I used Adobe Premiere Pro CC 26.0.2 for this test and I'm still using the SDK for Premiere Pro 22.
If you can provide more details how to reproduce this issue it'd be helpful.
Can you share the log file please? You can open it via the help menu.
I can reproduce this and I'm working on a fix.
As I have announced before I was working on the alternative subscription license option. This will go into beta phase from today on. Let's compare the features:
| Perpetual Classic "Voukoder Pro" License | Subscription license | |
|---|---|---|
| Model | One time payment, use forever | Recurring payment for each month |
| Version limitations | Bound to a single major version (i.e. Voukoder Pro 2 or Voukoder Pro 2026) | You can use always the latest version |
| Internet | No internet connection required | Requires an internet connection |
| Price | 69 EUR | 6 EUR |
| Feature set | All included | All included |
| Cancellation | - | You can cancel anytime. The cancellation is effective by the end of the current month. |
| OS support | All supported OS | All supported OS |
| Cancellation | - | Click here (or go to the top menu "License" > "Cancel Subscription-License") |
Voukoder Pro 2026 (3.1.3) is available for both Windows on x64 and Windows on ARM64 systems. Windows on ARM is currently available as BETA version. Although both is Windows, so this section applies to both - regardless if it is Windows on x64 or Windows on ARM64:
Please try to create a fresh new template by customizing one of the hardcoded and supplied templates.
P.S.: Hold SHIFT+CONTROL when starting up VEGAS Pro. The you can clear the cache.
I have fixed a critical bug in the VEGAS Pro plugin for the versions 18, 19, 20 and 21.
To all users having issues with that versions before: Please test it again and report if it's working now.
Done. Thanks 
I've added support for VEGAS 2026 from the new owner Boris FX in version 2026.1.0.
The non-western characters in the email with your trial license should now be properly encoded.
Please note that the latest Vouk Pro 2026 installer (2026.0.21) does not have an option to install to Boris FX Vegas. So, this script (or manual copy) is still required.
Yes, I'm waiting for the contact with Derek Blume and if Boris FX still wants to collaborate with me regarding VEGAS Pro.
I have checked your transactions. You have bought a license for Voukoder Pro 2.x last year. You can use this 2.x license for an unlimited time.
The license is stored at %LOCALAPPDATA%\VoukoderPro\license.txt.
Voukoder Pro 2026 (or internally Voukoder Pro 3.x) requires a new license.
Added two changes to the latest version (2026.0.21)
This should have been fixed already, but there was an issue / bug with it. You can use it with the 3.0.20 version.
您可以将其安装在任意数量的设备上。受限的是同时进行的编码进程数量。该数量由您购买许可证时填写的“席位”数量决定。
是的，许可证是可以互换使用的。
I have a news for all people having a Windows on ARM64 installation:
Today I've dropped the first BETA release of the Voukoder Pro ARM64 build.
Important! You need explicitly to install the ARM64 version of your NLE! These are available for all supported NLEs. You can check it with the Task Manager (The Architecture column on the Details page) when it's running. Windows 11 on ARM64 will also run the regular x86_64 build, but its just slower because it's emulated via Prism. (88fps vs. 195fps)
Please report your findings and issues here.
Just to keep track of this Post in the Adobe Community forums (in case it gets deleted again).
Adobe did not want to tell me how to get HDR data from premiere. But you can check this post for a workaround: https://www.voukoder.org/forum/thread/505
Yes, it seems that's the old issue VEGAS Pro has with Voukoder since the very first version of Voukoder (Classic). For some reason (and only for some users) VEGAS Pro doesn't want to load the plugin as an exporter. I currently have the same issue on my currently in-work Windows on ARM64 build (Surface notebooks). I'm debugging the issue together with the Microsoft support.
