Blackmagic Forum

bstaley wrote:Thank you! Any chance of a version for Linux?

G0bble wrote:what particular advantages do the more knowledgeable folks here anticipate from this?

jhoepffner wrote:Hello,
Thank you, thats super-smart. As you are a Windows developer, do you think it would be possible to implement HAP and LCNotch codec export?
It would be very useful for people, like me, working in an event and big projection.
All the best,
Jacques

Sergey Mirontsev wrote:unzip it to C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins

Jim Simon wrote:

Sergey Mirontsev wrote:unzip it to C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins

That location does not exist. There is a "plugins" folder (no IO, small p). Same thing?

Peter Fleming wrote:I created a IOPlugins folder in the correct location (C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins) and copied the 2 files into it, but no x264 options appear in the output render settings panel. What am I doing wrong?
Thanks

Peter Fleming wrote:Thank you, I did not see that you had to include the the folder "x264_encoder_plugin.dvcp.bundle" to get it to work.
Anyway that works really well, mind you I haven't tried the different data rates as yet.
Any possibility of having a VP9 output, as it is a common web format now.?
Thanks again

roger.magnusson wrote:Maybe it should be noted that this sample plugin has a hardcoded bit depth, set to 8-bit. Simply changing the relevant variable to 10 breaks it, so there's obviously a bit more to it that I haven't found yet. As far as I know x264 should no longer require a different binary for 10-bit.

I also note that the source code has a reference to an FFmpeg include folder that isn't used, so perhaps there's more they can release eventually.

Code: Select all

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

roger.magnusson wrote:That's no longer necessary (source). Running x264.exe --help on the one I compiled shows "Output bit depth: 8/10".

You are not allowed to post URLs!

Hendrik Proosa wrote:

roger.magnusson wrote:That's no longer necessary (source). Running x264.exe --help on the one I compiled shows "Output bit depth: 8/10".

If the dll is copied from ffmpeg. If it is built yourself, it might be disabled by default. The makefile for x264 has lots of conditionals based on this variable. Not sure which way Sergey did it.

EDIT: I can’t read, you compiled yourself and it shows 10bit there... must try myself what the problem might be then.

Dan Olson wrote:Installed on Mac, handled all the permissions, plugin shows up on the Delivery page, but export only outputs audio.

Mario Kalogjera wrote:Thank you Sergei.

What I noticed so far:

- Bitrate is in KBps...I think mbps would be better.

- I tried to render but render queue reported: FAILED, rendering never really starts but it actually reports it's rendering, could not snap it out of it even by pressing "stop", GUI becomes non-responsive, one can only press X and quit Resolve.

FuzzeeDee wrote:

Mario Kalogjera wrote:Thank you Sergei.

What I noticed so far:

- Bitrate is in KBps...I think mbps would be better.

- I tried to render but render queue reported: FAILED, rendering never really starts but it actually reports it's rendering, could not snap it out of it even by pressing "stop", GUI becomes non-responsive, one can only press X and quit Resolve.

I had the same issue. If you move your play head off of the beginning of the timeline before starting render it should render fine, albeit a little slower than DVR 16.

Jim Simon wrote:

G0bble wrote:what particular advantages do the more knowledgeable folks here anticipate from this?

I would say 'hope' rather than 'anticipate'.

For me, access to more encoding parameters which leads to better quality at smaller file sizes.

Jim Simon wrote:That said, we don't get full access to x264 parameters.

jhoepffner wrote:Hello,
Thank you, thats super-smart. As you are a Windows developer, do you think it would be possible to implement HAP and LCNotch codec export?
It would be very useful for people, like me, working in event and big projection.
All the best,
Jacques

Jim Simon wrote:Yes to both, Rahul.

That said, we don't get full access to x264 parameters.

Andrew Kolakowski wrote:x264 has too many parameters to expose all of them in GUI

Gary Hango wrote:The best option would be to provide as many settings as feasibly possible in the GUI and provide a mechanism to load a text file that will override GUI settings when needed.

Sergey Mirontsev wrote:

Peter Fleming wrote:I created a IOPlugins folder in the correct location (C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins) and copied the 2 files into it, but no x264 options appear in the output render settings panel. What am I doing wrong?
Thanks

You must copy not files, but folder, as shown on the screenshot in the first message.

Sergey Mirontsev wrote:

Dan Olson wrote:Installed on Mac, handled all the permissions, plugin shows up on the Delivery page, but export only outputs audio.

Not good. Tested on various Macs. This is not a typical error. The video is usually present.

Andrew Kolakowski wrote:For me not showing in GUI at all.
Bundle is there. I gave it full 777 permissions. OSX Mojave.

Dan Olson wrote:

Andrew Kolakowski wrote:For me not showing in GUI at all.
Bundle is there. I gave it full 777 permissions. OSX Mojave.

Have the Security and Privacy preferences open when you launch Resolve. Under General, below where it says "Allow apps downloaded from" it should display a note like "this file was blocked from running" with a "run anyway" option. That's what I had to do before I could get it to actually load in the UI.