Posts by auluswang

Quote from Vouk

Windows版本将于明日发布。
macOS版本的代码签名和公证工作仍存在问题，后续将陆续推出。

Why you can speak Chinese language ?

Dears,

I'm using Voukoder Pro (2.0.12.0) + FFmpeg (GPL) 7.1 to create the AV1 codec medias.

My system has AMD Ryzen AI 9 HX 370 w/ Radeon 890M, which has the ability of AV1 codec (yuv 422 10bit level), and the Nvidia RTX 4070 Laptop which has AV1 codec also.

NV version media color playing is correct, but AMD version media playing shows the color very strange.

Rec 709 media: AMD AV1, YUV 420, 10bit

Rec 709 media: Nvidia AV1, YUV 420, 10bit

I using the MediaInfo to check the medias, found the color of AMD media only has 'color range' parameter as Limited, actually it is not correct, my NLE is Davinci Resolve Studio output was set output color of Full range.

Meanwhile the NV version media has 'color range' + 'color primaries' + 'matrix coefficients' defenitions.

See bellow:

AMD configurations:

NV configurations:

Maybe I set the not correct AMD AV1 codec configurations, I'm not sure about it.

Any suggestions are hightly appriciated.

Thanks a lot!

Best regards.

Hi Vok,

In the Media Encoder 2024, I've installed both VKPro 0.7.8 beta and VK 13.3, try to output the .WebM format videos, but all failed in both.

VKPro 0.7.8 beta testing not able to finish.

I think so.

I'm making a new project, and try to output as .dra format for your analysising.

I make output again, now it seems correct, can play out by media player.

Acctually I update the Win11 to the lastest Win11 23H2 22631.2265, others nothing change.

vkpro I have is : 0.7.2.8 beta

Sorry for the late reply.

Yes I have multiple audio output devices.

Computer mainboard embedded audio card (Realteck audio output device), my Sony audio speaker using Sony audio driver installed (Sony ASIO output), my portable screen (via type-c cable linked to Nvidia rtx 3090 24g card) has it's own two speakers.

I will send you the short DVR project soon via google drive access link.

Uninstalled the traditional vk13, and also vkpro.

Then restarted the computer, and install the latest vkpro 0.7.2.8

But... my side here still not able to render out proper size files.

Hi Vouk,

Sorry to use this thread to feedback output file size topic not the VRAM leakage topic.

I've installed the 0.7.2.8, the output mov file size still has problem, and not able to be played correctly by MPC-BE.

Here is the log zip file for your analysising.

VoukoderPro_0.7.2.8.zip

here is the logfile VoukoderPro.zip

Hi Vouk,

I've installed the latest 0.7.2.6 beta, the output file size abnormal problem happen again.

Video player (MPC-BE) cannot open it again.

Would you please kindly check the code ?

BR / Aulus.

Hi Vouk,

Yes, indeed.

I installed the new released 0.7.2.2, and choose YUV 4:4:4 (16bit) in Resolve pannel as the source, and do the same in Scene Designer, now final created output HEVC 420 10bit mov file with the reasonable size.

Maybe forget about YUV 422 (10bit) topic, just let us choose YUV 4:4:4 (16bit) for ever. hahaha......

I've installed the vkpro 0.7.2.1

Also installed the traditional vk 13

the vkpro 0.7.2.1 can show the 'color range' etc information. Thanks a lot !

But concerning the file size with file visiable quality topic, I compared the vkpro 0.7.2.1 with vk 13, found the similar parameters output files size has huge difference and the image quality in same level.

If I modify the vkpro's QP value to limit its output mov file size, let it's size similar with vk 13 created file size, then the image quality of vkpro's will be huge huge downgrade, much worse than vk 13 created mov image quality.

vk 13:

vkpro 0.7.2.1:

The file size has around 10 times difference.

Could you please kindly check ?

BTW, after I installed the vkpro (no matter 0.7.2.1 or previous versions), why always pup-up a small window like this ?

Hi Vouk,

Thank you very much!

The 0.7.1.11 version works now for I want HEVC-420-10bit output, and the created mov file size also in reasonable level.

I have 2 questions:

1. VoukoderPro created mov file, during checking by MediaInfo app, the mov files cannot show 'color range' and so on parameters, any plan to add the showing function to VoukodePro ?

2. During the similar "bit rate" level compare DRS (18.5.1) created mov file with VoukoderPro (0.7.1.11) created mov file, during playing from image quality perspective, DRS created is visiablely better than VoukoderPro's.

So like in the traditional Voukoder 13 serials, any "Better Quality" template Scene(s) will add into VoukoderPro ?

Thanks a lot for the quick reply!

I've installed the 0.7.1.10 version.

Following screen shot:

- Right side: shows the parameters I set in Davinci and VoukoderPro.

- Left side: as the rendered out two sample mov files.

I put them together, to take the screen shot.

And during my rendering of the 2nd file, the Resolve crash-out, same behaviour like I feedback previously.

I re-start the Resolve, and do the rendering, to create the 2nd mov file.

You can see, the sizes of the 2 mov files are still abnormal, and when I use MPC-BE x64 to play them, all show cannot play with warning message pop-up.

The log zip file attached also.

BR / Aulus.

Hi Vouk,

I reinstalled the latest 0.7.1.9 (Beta Version) and using in Davinci Resolve Studio 18.5.

I select YUV422(10bit), and in the Scene, double click video line, and select "YUV 420 (10bit)" and Profile as "Main 10", then start rendering.

But the output file cannot be recognized, the size is also strange, around 6MB only (should be around 200MB I think).

And when I re-do the rending process, then Davinci suddendly crash-out.

Here I attach the voukoderpro log file for your better understanding or analysising.

Hi Vouk,

Thanks for the reply.

I've installed the beta 0.6 version of VoukoderPro.

I did select "YUV 422 10bit" in Resolve 18.5 as input format for VoukoderPro, then in VoukoderPro select Format as "YUV 420 (10bit)" and Profile as "Main 10".

But final output file vis MediaInfo checking still as "HEVC YUV 420 8bit", not as I wanted of "HEVC YUV 420 10bit".

Quote from Vouk

No, you should always be able to save a scene. No matter if you tested it before or not. Thats a bug, Can you explain the exact situation when you got that error?

The second question: This is just about what format DaVinci sends to VoukoderPro. You should select the closest format. In this case "YUV 422 10bit".

I tried to select "YUV 422 10bit", but after finished selecting parameters in the scene carefully, the final output video still YUV 420 8bit.

The VoukoderPro Beta has solved the "non-playing file" problem, but the YUV 4xxx xbit seems not as good as voukoder-connectors (e.g. 0.12.4 for Resolve) does.

Via the voukoder-connector, we can select YUV xxx (8bit) or YUV higher, everytime I do select YUV higher option, then goes into voukoder parameters, always correctly avoid YUV problem.

Because if choose 'YUV higher', then in the parameter can precisely select what we need. But in the VoukoderPro style, will select 2 times YUV parameters, I think here may cause problems for normal users.

Is it possible to put voukoder-connector style (e.g. "select YUV xxx (8bit) or YUV higher") into the voukoderPro ?

BR / aulus.

I think I solved this problem.

As Vouk suggested in the forum, to click 'test' firstly, then the disigner will save the Scene.

I found another question.

VoukoderPro has :

YUV 420 8bit

YUV 422 8bit

YUV 444 8bit

YUV 422 10bit

YUV 444 16bit

YUVA 444 16bit

So in the middle, not exist " YUV 420 10bit" ?

Hi,

I've installed the VoukoderPro Beta, and in Davinci Resolve Studio can see this.

But after click 'Open Scene Desinger' and modify a bit, if click 'save' will show the error.

And in Resolve, the Scene area cannot select something.

BR / Aulus

Quote from Vouk

Is this version any better?

Unfortunately, 13.2 beta 2 even not able to do rendering, always shows "Cannot add audio track to clip" error.