Beiträge von Vouk

Geht es dabei ums Projekt "Voukoder" oder um "Voukoder Pro"?

With the next release I'm leaving my hands out of FFmpeg. It won't be part of Voukoder Pro anymore. You can install any variant (with any supported encoders) you like best. I'll provide a GPL and LGPL variant to download though.

Got it running on my M1 MacBook Air!

Got the components working with eachother.

• Voukoder Pro - Core
• Voukoder Pro - Designer
• Plugin: DaVinci Resolve Studio

its time now to package it all in one installer app and fix smaller issues.

With the next version of Voukoder Pro you'll be able to install any variant of FFmpeg 7.1 DLLs you like.

Sounds really like it's a VEGAS issue.

Why did you add this filters to your filter chain?

w3fdif
format=pix_fmts=qsv

yuv420p can't be converted to qsv. One is a host device pixel format and the other a gpu (Intel) device pixel format

I'm currently working on the Voukoder Pro version for Mac.

Okay, please perform a scene-test and click the blue "Play" button. Add one video and audio-track. After performing the test copy and paste the output here.

Can you try if Voukoder Pro works?

Are you using "Voukoder" or "Voukoder Pro"?

x264 will be also supported!

Thanks for this detailed analytics. My replies refer to: https://ffmpeg.org/doxygen/trunk/…_accessors.html

1) I need to access the color information from the filter chain. The methods av_buffersink_get_color_range() and av_buffersink_get_colorspace() have been added recently (I guess). I'm using them in the next version. But I didn't find the methods av_buffersink_get_color_primaries() and av_buffersink_get_color_trc() yet. I have asked the libav devs.

3) The vendor tag should be written correctly (as reported in MediaInfo)

4) I'd also need a method to access the field order of the resulting frames. There are filters to change field order or even deinterlace filters. So I guess I'd need that buffersink_get method to get the final field order. Currently this is hardcoded to "progressive".

So, actually you configured it in DVRS and have it set to "Auto" in Voukoder Pro, right?

The color information in the input node tells each frame in what format data is received from - in your case DVRS. The output format can match this data, or it can be different. I need to check this a bit deeper.

With DaVinci Resolve Studio? It'll be fixed in version 2.0 - the next version.

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.