Posts by Krakozavr

Hello.

The new 17.4.6 update has been announced, with the following fix:

• Addressed issues with IO encode plugins

So, maybe some old persisted limitations of the DaVinci support can be resolved now?

Hi! Merry Christmas and Happy New Year

I found Voukoder 10.2 in the "downloads" section but no announcements. What this release is?

Try to use video levels.

I came here to report this bug and I found it already reported But with another version of DaVinci (I didn't update to 17.4).

All ProRes clips are going out with incorrect duration after I upgraded to Voukoder 10. Here are the samples, one clip rendered with Voukoder 10 and the same clip after downgrading to 9.3

https://we.tl/t-Xhwk6aguwv
https://we.tl/t-31YTMljloN

Quote from flyingcreature

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

some additional info.

It happened with size mismatched between source clip, timeline, and delivery.

The source clips were smaller but stalled to meet timeline size, and render was set to "source resolution".

I have a project which can't be rendered. I tried everything, updated render settings, restarted the PC, updated the connector to the latest beta 5, with the same result.

The screenshot and the log are attached, the link to the video is: https://drive.google.com/file/…Ae2n2vRR/view?usp=sharing

The project itself is not "regular": it has been processed with DaVinci's media management without relinking, and clips have been relinked manually. But inside the project, everything looks fine, clips are playing correctly, and the rendering going visually normal. But the result is unusable.

Delivering as individual clips, ProRes 422 HQ, "high bit depth" setting in DaVinci.

UPDATE: I rendered the same clip in DNxHR, no problem with it.

Another project which has been just created from scratches is rendering normally.

Also, what is strange, is the video card listed in the log is Intel HD. It is made on the Dell Alienware laptop, which has a dedicated NVIDIA card. Is Voukoder can't use it?

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

Quote from Vouk

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.

Quote from Vouk

What kind of color rendering bug? I am not aware of any.

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).

I had DaVinci crashes during exporting, multiple times on the same clip in the series of many with the exact same grading (render as separate clips). I isolated it in the render queue, with no luck; then, I changed color grading slightly, and finally rendered it successfully. Vukoder 4.0 (4.1 has the reported bug with color rendering, so, I did not install it, sorry). Here are the logs made after two crashes.

Quote from Vouk

Krakozavr Strange. Can you provide logfiles? What are the exact steps for me to reproduce this issue?

Nothing wrong with the plugin. It is about hardware high loading only - the plugin use it really intensive. My laptop needed some cleanup and thermal paste replacement for a while. I did it yesterday, no more blue screens

Quote from Vouk

Yes, noticed that as well. It seems "prores_ks" does scale perfectly with cpu cores.

I tried to render a batch of 32 individual clips with the plugin. I got them in the end, but my computer got 4 blue screens on the way (Dell Alienware 17R4). Never saw anything like this rendering uncompressed AVI

Hello!
Thank you for the "prototype," It definitely works!

I just tested it on Getty, and the great news - generated ProRes passed the Getty's automatic QualityControl on ESP. Before that day, only two converters out of many I tried have been passed: Acrovid FootageStudio 4K and ProDad Mercalli (which is not exactly a converter but can be used like this).