Can you try if this build fixes the color shift issue?
Beiträge von Vouk
-
-
-
-
I'm investigating this ...
-
I guess if you have video clips on the time line DaVinci Resolve is also rendering and sending both audio and video to Voukoder Pro, even if video track is then ignored. You can try to disable the video export in DaVinci Resolve. Is it better then?
If you have no video tracks in the timeline it doesn't render it and does not send it to Voukoder Pro.
-
I'll take a look at it soon.
I'd recommend ac3:CodeIn audio editing and transcoding tools (like FFmpeg or Shotcut), ac3 and ac3_fixed refer to two different encoder implementations for the Dolby Digital format. The main difference lies in how they perform math: - ac3: Uses floating-point calculations. It is typically faster on modern computers, yields slightly higher audio fidelity, and is the standard default for encoding. - ac3_fixed: Uses fixed-point math. It is designed for older processors, embedded systems, or devices that lack a dedicated floating-point unit (FPU). -
Sees that I basically need to take care that it also supports "Video und Audio" as Weiterleitungsoptionen.
Edit: Was ist wenn Du nach Adobe Premiere exportierst? Funktioniert das eventuell besser?
-
-
The reason might be that currently Voukoder Pro has been developed and tested with Premiere, After Effects and Media Encoder. I have to check how much effort it is to support audition as well.
What Audio format are you exporting from Audition, btw? Can you try "Float, 32 Bit"?
-
I've created the showroom sub-forum for users to show their creations, guides and more. Show us your creativity!
-
Please scroll the options a bit to the right, and look at the first entry under Vegas Pro

-
I just downloaded the file VoukoderPro-x86_64-2026.1.3.msi to make the above screenshot. The BorisFX option has to be there.
-
-
PFelby So you can see the voukoderproplug-vegas23.dll here?
even if "Show all formats" is checked?
If so, that's one of the bugs in VEGAS Pro that's the reason why VEGAS Pro is only supported with the "some users have issues" foot note. Some users have the issue, some not. I had my code check by the VEGAS Pro developers back when Magix was still the owner, and their feedback was my code is okay. I only got this fixed myself when I was reinstalling Windows and all programs.
If anybody finds the reason why this is happening this'd help me alot.
Did you install Voukoder Pro for VEGAS Pro 22 too? Does it work there? It can be installed together with Voukoder Classic.
DXV
Voukoder Pro uses FFmpeg internally for the export. But FFmpeg 8.1 does not support this format / texture with DXV yet.
CodeEncoder dxv [Resolume DXV]: General capabilities: dr1 threads Threading capabilities: frame and slice Supported pixel formats: rgba DXV encoder AVOptions: -format <int> E..V....... (from 1.14664e+09 to 1.14664e+09) (default dxt1) dxt1 1146639409 E..V....... DXT1 (Normal Quality, No Alpha)As soon as FFmpeg supports DXT3 and DXT5 with DXV Voukoder Pro will be able to export it too.
-
Yes, I've seen exactly the same when I've tried it the first time.
I opened your project file and exported exactly the region you've had selected, and it worked.
Strange. What exact version of premiere are you using?
-
No, unfortunately no news or updates. I investigated this again. As far as I know this should have displayed the FPS of the project. I checked the code again, even did an analysis with the "Claude" (Amazon Q and GitHub Copilot) AI. No success.
I also wasn't able to get in contact with anybody of BorisFX for around 6 months. I don't have a good feeling about these bugs getting fixed or about future VEGAS Pro support in general, but - we will see.
In the Magix time I was in contact with the developers, with the project lead and even with their CTO.
-
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 ...
- Customize and existing Voukoder Pro preset there and create a new one?
- If not ...
- customize the existing YUV 420 preset
- select the "4K" scene in that preset
- save the preset under a new name
-
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 created a new project with the "universial counting leader"
- I selected only the frames showing the "7 seconds" remaining
- Selected "Source in / Source out" for range
- I got a perfect export of only this section
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.
-
-
I can reproduce this and I'm working on a fix.