VoukoderPro beta in Davinci Resolve Studio - not able to select 'Scene'
-
-
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" ?
-
- Offizieller Beitrag
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".
-
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.
-
- Offizieller Beitrag
-
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".
-
- Offizieller Beitrag
You did exactly right! I tried to reproduce it and it worked fine for me.
Did you select the correct VoukoderPro-Scene?
Can you post your media info?
-
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.
-
- Offizieller Beitrag
-
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.
-
- Offizieller Beitrag
Made another fix regarding the filesize / compression. There was in fact an issue some settings were not applied.
I used your scene to export the file which was playable with MPC HC, MPC BE and VLC.
Can you provide an example DVR project I can use to investigate the crashes?
-
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 ?
-
Vouk
16. August 2023 um 15:02 Hat das Thema aus dem Forum Bug reports nach Beta-Talk verschoben. -
- Offizieller Beitrag
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 ?
If I just could remember why I removed these lines from the code ... AFAIK there was an issue with HDR export ...
Need to check this.
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.
I strongly suggest to avoid bitrate based encoding until it is absolutely neccessary. It's better to use quantizer parameter based strategies. The Voukoder presets are complex and quite more than just the bitrate.
Yes, I need to bring that into VoukoderPro ...
-
- Offizieller Beitrag
auluswang You might try 0.7.2.1. I'm setting color space, etc there.
-
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 ?
-
- Offizieller Beitrag
Thanks for your feedback.
- I removed that popup message box.
- The problem was with the YUV 422 (10 bit) format. The other formats work fine. I removed it in the latest build until I find the reason why it produces a larger file size than the source material.
-
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......
-
- Offizieller Beitrag
Great this issue is solved now!
-
-
- Offizieller Beitrag
Everything is working here. Can you please share your logfile?
-