Beiträge von Vouk

It is called libsvtav1.

I'm working on my todo-list. But if this get's implemented it'll be be in version 3.x which will most likely get released in the next year.

Still, It's not so complicated. Read the quickstart section of the documentation: Create a simple scene, double click on both encoder nodes and the UI is pretty much the same from there on.

All encoders in the Nvidia, AMD and Intel groups are GPU based encoders. All others are CPU based encoders.

Works for me. I tested it with h264_nvenc/aac/mp4 just now. It's playing flawlessly. I just fixed muxer settings were not applied before 2.0.12.

Edit: Do other users experience this too?

What issues do you have with v2.0.12?

I am in contact with the Magix guys now.

The original Voukoder was able to do this for x264 by exporting first the analysis file and then reading it in again with the 2nd and final render. But not many people are using this nowadays.

That's really interesting. I just don't understand if there are any connections. I'll upgrade to Build 248 first.

You should open one of the provided Voukoder Pro templates first and edit it and supply a "Scene" there first. This is required due to the different VEGAS Pro workflow.

Alright. That means the FFMpeg installation is also correct!

I have sent an eMail to Magix about this. I'll keep you informed.

Does the startup of the "Designer" app work? It should have been installed on your windows desktop.

That's strange. If it was ...

• indeed your first installation,
• you selected the correct VEGAS directory in the Voukoder Pro installer
• you followed all the installation steps exactly
• you did install one of my provided MSI installers
• and the Designer.exe app starts up correctly

... 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:

• I can reproduce the issue.
• I found the reason, fixing it now ...
• Fixed! Preparing a build ...

Thanks for notifying me about this. This bug had actually very much more consequences.