That's strange. If it was ...
... maybe you can check this:
In VEGAS Pro go the Help > About and click on the Components tab. Does Voukoder Pro appear here?
It's quite difficult to find this issue. My guess is it doesn't load because an old Voukoder (Non-Pro) component has been installed earlier, although I developed it in a way so this couldn't happen. But I can't attach a debugger to it to debug my plugin running in VEGAS Pro. The VEGAS Pro developers are protecting it against debuggers so I can't step through my plugin. This means basically they either give me help and / or the possibility to debug my plugin or I have to stop supporting VEGAS Pro. Sigh ...
On DVRS' deliver page select a color format that is at least 10 bit. It'd be YUV 4:4:4 (16 bit) in your case.
I'm aware some users having this issue (for quite some time actually). I'll investigate this asap.
I know we have talked over email before.
But I'll finally investigate this issue as this also affects many VEGAS users (though I'm not sure if this is a VEGAS Pro issue or a Voukoder issue).
What NLE are you using?
With Voukoder you are exporting in 10bit and in Voukoder Pro you are exporting in 8 bit. This can explain the non-smooth color transitions.
Use this instead:
(This is identical to yuv420p10)
Can you try if this is fixed with version 2.0.12?
Seems to be the correct usage. I'll check this.
Edit:
Thanks for notifying me about this. This bug had actually very much more consequences.
Did you read and follow the instructions on section 1 here Downloads & Instructions ?
You need to install FFmpeg first. This package is doing the actual encoding work. Due to licensing (and software patent) reasons this can't be bundeled anymore.
It is not supported yet.
This might not help, but I'll investigate it.
Can you try version 2.0.11 and re-test?
Die Fehlermeldung meldet dass er die FFmpeg 7.1 DLLs nicht finden kann. Voukoder Pro nutzt die EXE Datei nicht, sondern rein die DLLs.
Maybe you should continue using CRF 17. And if it's not good enough use a value lower than 17. The lower the value the better is the visual quality (and bigger the file size).
Normally Voukoder Pro picks the audio layout that gets exported from Premiere / Media Encoder. I will investigate this.
What error did you get? Did you check the Voukoder Pro log file?
Didn't hear about this issue anymore with the latest version.
For all future reports of this issue. This is a generic error message if something/anything is not correct. Most likely an incorrect encoder or an invalid parameter of it.
There will be a better error reporting in the next version 3.0!
Please send a Voukoder Pro Logfile or a perform a scene test and copy the log here.
I don't have access to the 2020 version of After Effects anymore, but with the 2025 version its working:
It depends on the implementation.
ChatGPT explains it like this:
Yes, technically: The MP4 container supports AV1 using the AV1 ISO-BMFF format, and tools like FFmpeg can place the moov atom at the beginning even for AV1.
However, support depends on the muxer and player:
- FFmpeg with -movflags +faststart works, but you must use libaom, libsvtav1, or other AV1 encoders that output compatible streams.
- The AV1 stream must be correctly formatted according to the AV1 codec ISO Media File Format Binding specification (ISO/IEC 14496-15:2017 + amendments).
- Some older players or browsers may not fully support AV1-in-MP4 yet, especially for streaming.
