ProResLT is 8bit depth. However, there are no 8 bit choice inside of Voukoder plugin setup, 10 only.
No, all ProRes variants are 10bit or more. From 444 upwards they are 12bit.
Davinci Resolve now allows for third party render
-
- Done
- Nick_Lavigne
-
-
this is not my picture but it made by a top-professional colorist. This is a result of ProRes rendering of solid color. Also, he reported some problem with levels (sorry, he did not provide details).
Has that 444 16 bit mode being used for this export session?
-
I'm not able to render anything with the latest beta 0.4.1. I get the message: "Render Job X failed as the current clip could not be processed. Cannot add audio clip."
Can you attach the voukoder logfile? Where do I find the log file?
-
Can you attach the voukoder logfile? Where do I find the log file?
It looks like the issue was related to the specific timeline that I was trying to render. I'm able to render a different project just fine now. Do you want the log file from project that I failed to render?
-
Can you tell me about what was special in that project? Maybe some audio settings?
-
Maybe it's because I had a mix of 16 and 24 bit (all 48khz) in the session?
-
Has that 444 16 bit mode is used for this export session?
I believe it is correct.
But I tried to recreate this issue without success. My renders come out clean in any mode (444 16bit in DaVinci; ProRes 422HQ, 444, 444HQ in voukoder).
UPDATE: I processed the same tests as Anton, the author of the original screenshot, but I still can't reproduce his result. But he used DaVinci 17.0, and I use v. 17.1 - so it may be DaVinci's bug. -
one annoying problem.
Voukoder is ignoring low space
Yesterday I occasionally set a long batch (individual clips rendering) to a full disk.
With regular render, DaVinci would stop render with an appropriate error message.
But with Voukoder, it took full time for render (about an hour and a half for one batch and two hours for another) and finished without error messages, created 5 properly rendered clips (till disk space was exhausted) and 35 empty, 36K-size-each clips for all others
-
Awesome to see this happening. It's the first thing I'll try once I get my Davinci Resolve Studio dongle on Tuesday
-
Vouk
Added the Label DaVinci Resolve -
Also, I have some conflicts with Resolve's NVIDIA encoder. This was seen in the early betas of the MainConcept plugin.
One of the discussions about this.
Same problem in last version.
-
Привет. спасибо за работу! У меня есть несколько вопросов.
1. Why are these choices of bitness left in the Davichi interface, if all the same, if necessary, the codec does the bitness reduction itself?
I left it at the default of 8 bits and got streaks of artifacts on the gradients. Why don't you always send the maximum color depth to the codec?
2. кодек имеет возможность установить контейнер - avi, mkv или mov, но нет возможности изменить выбор по умолчанию. Например, я всегда кодирую mov. Хотелось бы, чтобы мне не приходилось каждый раз устанавливать это значение.
Можете ли вы заставить кодек запомнить мой выбор?
Еще раз спасибо за отличную работу.
-
1. Basically export speed is the reason. If you export a yuv420 (8 bit) it is significantly faster to use the 8 bit output mode in resolve. Otherwise each frames data has to be converted from yuv444 16 bit down to 8 bit first, and then sent to the encoder. If resolve delivers 8 bit already we can just pass it through to the encoder.
2. It is a bit tricky because it just shows the available containers that support the current selected audio and video container. But I'll see what I can do.
-
2. кодек имеет возможность установить контейнер - avi, mkv или mov, но нет возможности изменить выбор по умолчанию. Например, я всегда кодирую mov. Хотелось бы, чтобы мне не приходилось каждый раз устанавливать это значение.
Можете ли вы заставить кодек запомнить мой выбор?
Yes, you can.
Set everything as you wish, both in DaVinci and Voukoder, then save a delivery preset in DaVinci
-
Vouk
Set the Label from Implementing to Done -
Vouk
Removed the Label DaVinci Resolve
