Encoder plugin packs - June 2022 Update

export would be a very nice start.

Hi there.
Where can I download this codec?

I bought two licenses of Davinci Studio and I feel it is very hard to find support and information about the software.

I wish I could have an account where I can download the software with all the codecs needed to have the software run properly.

Can you help me and tell me where I can download these codecs? I am using Windows

Thank you

Hello all, we want to let you know about a new feature in v17 that allows companies to offer a plugin pack for additional and optimized render formats.

The first company to offer this is MainConcept who have a Codec Plugin which offers DaVinci Resolve Studio users the ability to directly export a number of codec types like AS-11 UK DPP SD or HD compliant content, or rendered into HEVC in up to 8K resolution. With the plugin, projects can be rendered into professional broadcast camcorder formats, allowing exported video to remain in the original recording format.

Visit mainconcept.com/bmd-beta to see how it integrates into the Blackmagic Design DaVinci Resolve timeline and sign up for the free beta, available for Windows, macOS, and Linux.


Update: This plugin pack now has a new June 2022 update.

Support now includes:

HEVC encoding up to 8K
Encode HEVC/H.265 Main and Main 10 in up to 8K in MP4 file format, widely used in OTT workflows and environments

AS-11 UK DPP Rendering
Supports AS-11 UK DPP SD (MPEG-2) and HD (AVC/H.264) project rendering with ready-to-use SD and HD presets, including metadata handling, direct from the DaVinci Resolve Studio timeline
The included XML metadata template file can be modified to set all descriptive metadata required to create AS-11 UK DPP compliant content
Metadata compliant

Pro camera formats and preset groups
Supports a wide range of professional camera formats and preset groups including:
Sony XDCAM EX, HD & IMX and XAVC & XAVC-S
Panasonic P2 DVCPRO and AVC Ultra (Intra and LongG)
MP4 HEVC (8-bit or 10-bit)
MXF (AS-11 UK DPP SD or HD & RP2027 AVC-Intra)
DVD (MPEG-2)
NEW: Blu-ray Disc
NEW: MP4 AVC (8-bit or 10-bit)

Hello there.

You can download, try and or purchase the plugin pack here.

https://www.mainconcept.com/blackmagic-plugins

BMD should buy them out

Mainconcept is doing fine and don't need any new owner.
Stop thinking that 1 company owning everything is a good thing.
It's far from it.

Mainconcept is doing fine and don't need any new owner.
Stop thinking that 1 company owning everything is a good thing.
It's far from it.

Don't assume too much It was just a joke.

But,... since Resolve is using the host capabilities to write h264/5 files (they are terrible), I wouldn't mind.
It's like having a Ferrari, but you have to buy a separate thing from a third party to unlock its full potential.

BMD is one of the good company out there with Grant's philosophy.

So, shouldn’t Microsoft buy them?
BTW, they are behind AME and I doubt Adobe wouldn’t have made a contract to avoid them being bought by direct competition.

Mainconcept is under the hood of about all professional tools out there- from Adobe, Telestream to Autodesk.

Voukoder plugin got an update to 0.13 which should fix the gamma and color space tag issue with DVR 18.6.x
https://www.voukoder.org/forum/thread/1 ... 6#post7796

Download here:
https://www.voukoder.org/forum/thread/7 ... tructions/

Connector for DVR 0.13.0
Voukoder 13.4.1

AAC audio in import & export for linux would be a game changer ....
https://sharpedgeshop.com/ Can that be added?

Adding AAC audio support for import and export in Linux would indeed be a significant enhancement.

Firstly, I'll start with how I render my x265 files.

ffmpeg -hwaccel cuvid -i "%file%%ext%" -c:a aac -b:a 384k -c:v hevc_nvenc -preset %speed% -rc-lookahead:v 64 -cq:v %quality% -pix_fmt p010le "FFMPEG___%file%%ext%"

It's part of a .bat script in the "sendTo" folder of Windows. So it appears under a right click on a file.
It prompts for the CQ quality (I use 30 for the less important thing, and 24 for what I really want to preserve. Lower sometimes), and "slow or medium" for the -preset

It works well, it's consistant, and I have great results. It's a two steps process. I export a high quality file with the DNxHR codec from Davinci Resolve, then I use FFMPEG.

I tried the trial of the plugin pack a couple month after it came out a while back. The speed was on par with ffmpeg, same with the quality. I almost bought it, but even if it's not that costly, I

But I'm starting to get tired of this two step process. Even if it works very well for me, with a very consistant good quality/manageable file size, I would like to cut down on the rendering time. And doing it all from Resolve would be nice.

If anyone has as similar type of experience (exporting a high quality/high bitrate file then using whatever 3rd party software to encode the final video with it), and switched to the mainconcept plugin, did you find and drawback? How did it go? What's the general experience?

Thanks

Shutter Encoder is based on ffmpeg and has a watch folder. What about rendering into that from DR?

Shutter encoder is indisponible. It is an excellent alternative to media encoder.
I bought the resolve MP4 AAC encoder plugin and don't regret it. Life is too short.

But I'm starting to get tired of this two step process. Even if it works very well for me, with a very consistant good quality/manageable file size, I would like to cut down on the rendering time. And doing it all from Resolve would be nice.

There's an x264_encoder_plugin sample that was created by BM, it shouldn't be too hard to create an x265_encoder_plugin using it as a base. X265 library function calls are quite similar to X264.

I'll take a crack at it one of these days - looks like you are using yuv420p10le for the pixel format. With that said, pretty sure using x265 library will be all CPU though (no hardware acceleration) but will most likely have better output.

Shutter Encoder is based on ffmpeg and has a watch folder. What about rendering into that from DR?

For now on PC this is the way to go. I’ve been using Shutter Encoder for a long time now,not only for H.265 delivery but ProRes as well. I know it’s not Apple blessed but it is just equally as good and useful.

If you don’t have Compressor, it works on a Mac as well.

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

https://github.com/UDaManFunks/x265_encoder

* Supports the main profile

https://github.com/UDaManFunks/x265_encoder_10b

* Supports the main10 profile

https://github.com/UDaManFunks/prores_encoder

* Supports Proxy, LT, 422 and HQ profiles

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

https://github.com/UDaManFunks/x265_encoder

* Supports the main profile

https://github.com/UDaManFunks/x265_encoder_10b

* Supports the main10 profile

https://github.com/UDaManFunks/prores_encoder

* Supports Proxy, LT, 422 and HQ profiles

These are awesome, thanks for doing this! I would also love to see one that lets us export AV1 using SVT-AV1. Right now, there's no way to export AV1 on an Apple Silicon Mac.

These are useful, if a little slow, but can I ask why ProRes 4444 is not an option, since ffmpeg can support it?

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

https://github.com/UDaManFunks/x265_encoder

* Supports the main profile

https://github.com/UDaManFunks/x265_encoder_10b

* Supports the main10 profile

https://github.com/UDaManFunks/prores_encoder

* Supports Proxy, LT, 422 and HQ profiles

These are awesome, thanks for doing this! I would also love to see one that lets us export AV1 using SVT-AV1. Right now, there's no way to export AV1 on an Apple Silicon Mac.

Will try it but it'll take a while (maybe a month) to do it and it'll most likely only work on windows, and linux (I don't have a mac compile env).

Main and High Profiles only as well (both 8-bit).

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

https://github.com/UDaManFunks/x265_encoder

* Supports the main profile

https://github.com/UDaManFunks/x265_encoder_10b

* Supports the main10 profile

https://github.com/UDaManFunks/prores_encoder

* Supports Proxy, LT, 422 and HQ profiles

I keep getting this error.

$ CC=cl ./configure --toolchain=msvc --disable-programs --disable-shared --disable-debug --enable-static --prefix=/C/VideoEditingUtils/prores_plugin_build/ffmpeg_pkg
cl.exe is unable to create an executable file.
If cl.exe is a cross-compiler, use the --enable-cross-compile option.
Only do this if you know what cross compiling means.
C compiler test failed.

If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help


Any Thoughts?

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

https://github.com/UDaManFunks/x265_encoder

* Supports the main profile

https://github.com/UDaManFunks/x265_encoder_10b

* Supports the main10 profile

https://github.com/UDaManFunks/prores_encoder

* Supports Proxy, LT, 422 and HQ profiles

Thanks a lot for your work! But, i have a problem with x265.

When I get to this point:

[Compile x265_encoder]

cd ~/x265_plugin_build/x265_encoder

make

I get this error:

/usr/bin/ld: ../x265_pkg/lib/libx265.a(threadpool.cpp.o): in function `x265::ThreadPool::create(int, int, unsigned long)':
threadpool.cpp:(.text+0x20b): undefined reference to `numa_available'
/usr/bin/ld: threadpool.cpp:(.text+0x309): undefined reference to `numa_allocate_nodemask'
/usr/bin/ld: ../x265_pkg/lib/libx265.a(threadpool.cpp.o): in function `x265::ThreadPool::setThreadNodeAffinity(void*)':
threadpool.cpp:(.text+0x585): undefined reference to `numa_available'
/usr/bin/ld: threadpool.cpp:(.text+0x5b4): undefined reference to `numa_run_on_node_mask'
/usr/bin/ld: threadpool.cpp:(.text+0x5bc): undefined reference to `numa_set_interleave_mask'
/usr/bin/ld: ../x265_pkg/lib/libx265.a(threadpool.cpp.o): in function `x265::ThreadPool::getNumaNodeCount()':
threadpool.cpp:(.text+0x835): undefined reference to `numa_available'
/usr/bin/ld: threadpool.cpp:(.text+0x845): undefined reference to `numa_max_node'
/usr/bin/ld: ../x265_pkg/lib/libx265.a(threadpool.cpp.o): in function `x265::ThreadPool::allocThreadPools(x265_param*, int&, bool)':
threadpool.cpp:(.text+0x9bb): undefined reference to `numa_available'
/usr/bin/ld: threadpool.cpp:(.text+0xd41): undefined reference to `numa_allocate_cpumask'
/usr/bin/ld: threadpool.cpp:(.text+0xd64): undefined reference to `numa_bitmask_weight'
/usr/bin/ld: threadpool.cpp:(.text+0xd7e): undefined reference to `numa_node_to_cpus'
/usr/bin/ld: threadpool.cpp:(.text+0xdb1): undefined reference to `numa_bitmask_free'
/usr/bin/ld: threadpool.cpp:(.text+0x1096): undefined reference to `numa_available'
/usr/bin/ld: threadpool.cpp:(.text+0x1244): undefined reference to `numa_allocate_cpumask'
/usr/bin/ld: threadpool.cpp:(.text+0x1257): undefined reference to `numa_bitmask_free'
/usr/bin/ld: ../x265_pkg/lib/libx265.a(threadpool.cpp.o): in function `x265::ThreadPool::~ThreadPool()':
threadpool.cpp:(.text+0x541): undefined reference to `numa_bitmask_free'
/usr/bin/ld: ../x265_pkg/lib/libx265.a(threadpool.cpp.o): in function `x265::ThreadPool::setThreadNodeAffinity(void*)':
threadpool.cpp:(.text+0x5c2): undefined reference to `numa_set_localalloc'
collect2: error: ld returned 1 exit status
make: *** [Makefile:34: bin/x265_encoder.dvcp] Error 1

Any solutions? I had no problem with the x264 codec, which works perfectly on Arch Linux (too bad it uses the CPU instead of the GPU, though).

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

https://github.com/UDaManFunks/x265_encoder

* Supports the main profile

https://github.com/UDaManFunks/x265_encoder_10b

* Supports the main10 profile

https://github.com/UDaManFunks/prores_encoder

* Supports Proxy, LT, 422 and HQ profiles

Thank you for your work! I had no problems with the x264 codec although unfortunately it uses the CPU and not the GPU to render. However, I was not able to insert the x265 codec because when I do Make it gives me Error 1 in creating the file which will then have to be inserted in the DaVinci Resolve Plugins folder. Can you tell me what it could be? I am using Arch Linux not Ubuntu anyway.

I had no problems with the x264 codec although unfortunately it uses the CPU and not the GPU to render.

That's by design, x264/x265 is not made for GPUs.

To be a bit more specific, your GPU is still used to render the images in Resolve, then the CPU is used to encode/compress the video in this case.

I had no problems with the x264 codec although unfortunately it uses the CPU and not the GPU to render.

That's by design, x264/x265 is not made for GPUs.

To be a bit more specific, your GPU is still used to render the images in Resolve, then the CPU is used to encode/compress the video in this case.

So there is no possibility to have rendering in AV1 or H265 with DaVinci Resolve on Linux? I also tried the studio version but could not export to AV1 (I have an AMD GPU and on Windows it works perfectly, I can export to AV1 using the GPU even with the free version of the program). As an aside, can you tell me what is that error (which I posted in the previous message) that I encounter when I try to install the x265 codec when I get to the point of using the make command? Thanks

If you switch to Video Toolbox, HandBrake is using the hardware encoders.
I don't know if that's offered with the plug-in.

Right, but then it's not x264/x265 which for some is the whole point because they are insanely optimized for image quality.

True. Quality needs time – like everywhere

Created a couple of export CODECS (works on Windows and Linux)

https://github.com/UDaManFunks/x264_encoder

* Supports the baseline, main, high, high422 profiles.

I see FHD MP4 clips exported with this and Main profile are Level 5, and are therefore stuttering when playing back on VLC for Android, even with reasonable bitrate (<= 10 Mbps). Ususally I use TMPGEnc VMW 7 to encode with x264 and it defaults to Level 4 for any profile at FHD resolution, and that plays nicely on VLC/Android. Is there a way to specify the Level when encoding with this plugin ?

Great article! Thanks for sharing.

Thank you so much for this. As a Linux AMD user it is so much more convenient to export in x264 directly to deliver to clients.

One confusion though. I read that people say this is only using CPU to encode but when exporting I check the GPU usage and it is clearly using a lot of GPU power. Meanwhile CPU usage isn't that high at all. Is it because that I put on some fusion effects on the timeline so the GPU is being used for that part of work?

One confusion though. I read that people say this is only using CPU to encode but when exporting I check the GPU usage and it is clearly using a lot of GPU power. Meanwhile CPU usage isn't that high at all. Is it because that I put on some fusion effects on the timeline so the GPU is being used for that part of work?

That's my observation too; as I am also using the x264 engine elsewhere (TMPGEnc), I know for sure it uses only CPU, and indeed, as soon as there is something else to process during the export before the actual encoding, like some FX of Fusion, the GPU is used for that if possible (and it might even be the bottleneck, causing the downstream x264 encoding to be "waiting" for frames and hence, not use all the available CPU.)

I see FHD MP4 clips exported with this and Main profile are Level 5 [...].

Is there a way to specify the Level when encoding with this plugin ?

@UDaManFunks -> ?

Thanks

I see FHD MP4 clips exported with this and Main profile are Level 5, and are therefore stuttering when playing back on VLC for Android, even with reasonable bitrate (<= 10 Mbps). Ususally I use TMPGEnc VMW 7 to encode with x264 and it defaults to Level 4 for any profile at FHD resolution, and that plays nicely on VLC/Android. Is there a way to specify the Level when encoding with this plugin ?

This causes other kind of players to refuse playing these files too, e.g. some older LCD TV sets (a.o. Sony)
It seems Main@Level 5 for HD1080 clips isn't a common thing.
I value the x264 engine and really miss the ability to specify High@Level 4.1

Any hope ?