Beiträge von Vouk

Can you try this with the latest Voukoder Pro release? I remember I have fixed this issue some months ago and i can also see this line in my logs:

2026-01-28 14:14:01 (trace) Starting second pass: moving the moov atom to the beginning of the file

I already did that.

Maybe there is also a reason why all that HDR information is not present in the SDK pdf.

What container are you using?

Can you post your log file here where this issue appears?

Zitat

P.S.: My post in Adobes forum: https://community.adobe.com/t5/premiere-pr…er/m-p/15659803

Seems my post just got deleted. Alright, that's a way to deal with questions, too.

I will investigate this.

Alright, so I reverted that change. And I have to wait for the VEGAS Pro developers response.

I did not receive any updates from the VEGAS Pro team yet, but can you guys test if https://d.voukoder.org/VoukoderPro-2026.0.19.msi helps? I've switched the region settings from en-us to neutral for the VEGAS Pro plugins.

Did you also test (an confirm this) with the built-in Adobe encoders encoders?

The reason is After Effects is a bit "special" in terms of colors.

• It treats colors as RGB (and not YUV) values. But most encoders require YUV data as input. That why a lossy color format conversion is necessary.
• Also when using the high bit depth (16 bit per color channel) export Voukoder Pro has to remove the most significant bit, because Adobe used it for something else. That's why it is actually only 15 bit. This is from the first version of Voukoder on. But it only applies to 16 bit data, and only After Effects.

I'll discuss this with the VEGAS developers.

Zitat von Vouk

Does the number parsing issue appear anywhere in Voukoder Pro or just in VEGAS Pro? If it appears in Voukoder Pro where exactly does it happen?

Can you try Voukoder Pro 2026 (the latest version)?

Does the number parsing issue appear anywhere in Voukoder Pro or just in VEGAS Pro? If it appears in Voukoder Pro where exactly does it happen?

miki1hr Can you please try if this issue has been fixed with this build? https://d.voukoder.org/VoukoderPro-2026.0.18.msi

Got it fixed! This seemed to be broken since version 2 or even longer. I'm preparing a new build ...

This is more complicated than I have thought:

Right now, the only way it is possible to define it manually:

-x265-params "master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50):max-cll=1000,300"

(for x265)

Still investigating ...

Yes, I will check tomorrow.

Edit: I have checked this. The data is written just like in version 2. But it doesn't show up in MediaInfo anymore. Maybe FFmpeg 8 is handling this differently now.

Edit: Seems like this data is supposed to be set per frame now, not per stream. Checking ...

Argonil

You should be able to register your trial again.

What was your language/country setting when this has happened?

As Marko65 noted this issue was a known issue in VEGAS Pro, not in Voukoder Pro, but I can give you ...

• Allow you to re-register for the trial version, so you have 14 days more to test
• A discount code about 10 EUR

Hello! You are right. Voukoder Pro 2026 3.0.16 is not a BETA anymore. I'm fixing this.