Posts by smirontsev

Quote from Vouk

There is also an issue with the latest version 17.4.5 (See other forum thread).

Cannot find other thread. But have issue too.

Quote from salone

Hi,

I installed Voukoder on my DaVinci Studio but in Deliver menù, when i click on Configure Voukoder button, nothing happens.

Please, can somebody helps me?

You must install the program itself.

https://www.voukoder.org/forum/thread/783

Quote from diego89ta

Hi, did you resolve it? I have the some problem. Timcode start from 00.00.00.00 every time

This works in the latest version of the program (Voukoder 9) and connector.

Quote from smirontsev

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.

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=128517

Same problem in last version.

Quote from Vouk

I'm not sure how the timecode information is stored

Is it possible that this is a separate stream in Resolve?

The x264 plugin saves timecode but has no code to explicitly handle it.

Vouk

Daniel, what is changed in 0.4.0?

What should we select here for ProRes?

Quote from Vouk

Actually pIOPropBitsPerSample (not pIOPropBitDepth) is controlling the bit depth for video.

Oops. I found use of this in dummy_container.cpp (from line 125 and below. If (isVideo) ... else

So, I concluded this is not being used for video. Sorry.

Quote from rotem

I dont have "IOPlugins" folder

You definitely need to create IOPlugins folder.

Quote from Andy

All those setting should be there as well, no? So it just needs mapping.

Not exactly. We do not have some kind of "file" for encoding with ffmpeg-like options. We need to "ask" Resolve (with C++ code) to get us the stream in the correct format. And this part of API is not documented at all. So, we can't "Let Resolve do proper RGB->YUV conversion based on project settings etc." until learn how to properly command Resolve via API. The second part - encoding to differents codecs - is not a problem then.

Quote from Andy

For ProRes you want to add extra bits to ffmpeg command

Andy, the plugin does not use the ffmpeg executable and its command-line parameters. The library libav and API is using.

Quote from Vouk

Do you know how I can get high bit depth pixel data

I don't know for sure. But the next code does not generate errors in s_RegisterCodecs (Pixel Format was not defined for plugin encoder fourCC) or when I try to render (Color mode is not supported). I choose 16 bit because for fourCC codecs it is 4/8/16/24/32 (https://www.fourcc.org/rgb.php). But I am not experienced in programs like this.

P.S.: pIOPropBitsPerSample is for audio, you know, right?

val = clrUYVY;
codecInfo.SetProperty(pIOPropColorModel, propTypeUInt32, &val, 1);

uint8_t hSampling = 2;
uint8_t vSampling = 2;
codecInfo.SetProperty(pIOPropHSubsampling, propTypeUInt8, &hSampling, 1);
codecInfo.SetProperty(pIOPropVSubsampling, propTypeUInt8, &vSampling, 1);

val = 16;
codecInfo.SetProperty(pIOPropBitDepth, propTypeUInt32, &val, 1);
val = 8;
codecInfo.SetProperty(pIOPropBitsPerSample, propTypeUInt32, &val, 1);

Quote from Roger Singh

Just an update. I downloaded version 0.3, and I still get unknown colorspace.

When I render an uncompressed MOV from Resolve, and render a prores out of Premiere, it shows ITU-R BT.709

Connector: 0.3.0

Resolve: 17.1.1

Quote from Vouk

Native DVR NVENC fails after Voukoder ran

MainConcept's plugin also has NVENC support. But I have no idea how they fixed en error. Closing NVENC session in the destructor?

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.

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=128517

Ooops. No timecodes in mov.

Quote from Vouk

Currently UYVY422 is used to exchange frames between DVR and Voukoder. AFAIK this does not have an alpha channel. I still need to find out how I can use different color models / pixel formats.

val = clrUYVY;

codecInfo.SetProperty(pIOPropColorModel, propTypeUInt32, &val, 1);

Did you try clrRGBA (or clrRGBAp)? Or you need to change something on the Voukoder side?

Quote from Vouk

enum values in the DVR SDK

What do you exactly call DVR SDK?

Quote from Vouk

Looks plausible. I always got "1" when having a bt.709 project. I'm just wondering why that values in the bbc code matches up with enum values in the DVR SDK. Coincidence or some kind of standard?

QuickTime format?

Quote from Vouk

So I don't know how to map these values.

It is very likely that the values are described here: https://github.com/bbc/qtff-parameter-editor, Video Characteristics section.

Quote from Vouk

Yes, it is already.

And it is used by default, right?
P.S.: I already understood from the settings - yes.