Beiträge von Vouk

I remember this "bug" for years now. It's difficult and not really clean to work around bugs in the host application "VEGAS Pro" in an underlying piece of software. Please check rgr s post.

Indeed. And I've found a way how x264/5 can be back legally. I'll announce it later this year.

This really looks highly advanced. I need some time to look into this.

In the designer app you need to save the scene with a proper name first. Then - if you close the designer app again - DVR refreshes the dropdown list with the scenes and you should be able to select it.

Can you show me the place where you have configured this? In Voukoder Pro or in DVRS?

You could open %LOCALAPPDATA%\VoukoderPro\scenes.json and edit the params section of the encoder/video node with a text editor:

"params": {
"g": 0,
"bf": 0
},

But i can't guarantee these settings survive a "save" action with the Designer app.

Edit: I have added the params to all h264 and hevc encoders.

I have removed the "g" parameter again. I need to figure out a more clever solution for it. i.e. a checkbox (like in the old voukoder) to enable this property.

Can you show me a screenshot where you have set these to bt709?

Thanks for your tests. I'll reply to it soon.

1. For *_nvenc encoders I'm using this private parameters:
     -qp                <int>        E..V....... Constant quantization parameter rate control method (from -1 to 51) (default -1)
     -cq                <float>      E..V....... Set target quality level (0 to 51, 0 means automatic) for constant quality mode in VBR rate control (from 0 to 51) (default 0)
   
   But you're right! I've missed this for AV1, thanks!
     -qp                <int>        E..V....... Constant quantization parameter rate control method (from -1 to 255) (default -1)
   
   Fixed in the next build!
   
2. Fixed.
3. I've added "bf" and "g" to all h264, hevc and av1 encoders.
4. This was introduced with FFmpeg 7.1. I've updated to FFmpeg 7.1 so that parameter appears.
5. It's nice to check the encoder params with this view. I plan to add this as well.
   Edit: Done!

Yes, it is planned to improve this.

I'm aware of this. Premiere CS6 is a 12 years old and does not support the features VoukoderPro is currently using. I'm not sure if CS6 can be still legally activated.

Documentation will follow soon! This is rather important to me too.

Please copy me a log file or a scene test that show the run attempt.

Can you tell me what's actually better with these "better" encoders? To me it seems they just use the already present fixed functions encoders in the hardware devices.

Can you provide more details please? What Encoder / Muxer / Output did you? With "regular one" you mean the classic Voukoder? What System do you use?

Yes, this is a bug. The next version will have the correct version number.

I didn't add any audio offset to VoukoderPro. It seems VEGAS Pro fixed it in the latest version.

But you can try getting rid of it in earlier versions by adding a delay filter to the scene:

The Mac version is also in progress now.

After all it was so simple. Thanks for pointing me in the right direction!

This will be fixed in the next version!

I remember I asked black magic some years ago on how to get the alpha channel data but i didn't get any feedback from them.

• I use the AYUV pixel format (which should have alpha channel data)

But the alpha channel is always 255 (or 65535) which indicates "no transparency".