Jump to content

DaVinci Resolve 16.2.1 released

Recommended Posts

DaVinci Resolve 16.2.1 has been released and is available to download from https://www.blackmagicdesign.com/support/

The update adds support for encoding 32-bit float audio in QuickTime clips and for trimming QuickTime audio during media management. This update also improves performance of 10-bit H.265, ProRes, DNxHR and OpenEXR clips.

Another big addition to 16.2.1 is support for Metal based R3D decode with RED 7.3 RC SDK.

This is the first implementation of R3D GPU acceleration via Metal on Mac.

What’s new in DaVinci Resolve 16.2.1

  • Support for decoding H.265 4:4:4 12-bit on supported NVIDIA GPUs.
  • Support for encoding H.265 4:4:4 12-bit on supported NVIDIA GPUs.
  • Support for encoding 32 bit float audio in QuickTime clips.
  • Support for trimming QuickTime audio clips during media management.
  • Support for Metal based R3D decode with the RED 7.3 RC SDK.
  • Support for double clicking drp files in Windows and Linux.
  • Support for performing open with on FCP7 XML files on Windows.
  • Improved decode support of H.265 4:4:4 clips up to 10-bit.
  • Improved performance with ProRes clips on high end CPUs.
  • Improved performance with DNxHR clips on high end CPUs.
  • Improved playback performance with compressed OpenEXR clips.
  • Improved performance for Dolby Vision analysis.
  • Improved stability on Windows systems with Intel graphics.
  • Addressed an issue with clean feed previews in Mac 10.15.4.
  • Addressed an issue with decoding phone camera clips with AAC audio.
  • Addressed an issue with truncated node labels on some displays.
  • Addressed issues with HDR tone mapping when using adjustment layers.
  • Addressed an issue with the sync bin work working with an empty timeline.
  • Addressed an issue with transitions when dragging clips across timelines.
  • Multiple performance and stability improvements.

Share this post

Link to post
Share on other sites

I'm not sure if anyone noticed, but the audio waveform display in the edit page is now like that in the Fairlight page and expandable. I can't remember whether the audio level was displayed previously when changing the level, but it is now.

  • Like 1

Share this post

Link to post
Share on other sites

An interesting observation. I just took some night time video of a Brushtail Possum that visits our yard to finish off what wild bird seed our parrots and rosellas leave behind. I used my BMPCC4K, BRAW 5:1, 2.4:1 at ISO3200. The possum was lit with just a single Aputure AL-F7 LED from 5.4m away (measured with a laser rangefinder). The scene was still quite dark and I naturally had to use noise reduction, something I've yet to master, but the surprising thing is that when I rendered the final 4K file it went along smoothly.

I have never previously been able to use noise reduction and get anything resembling smooth rendering and often it would just bog down or Resolve would crash, but this time it completed without a hiccup. I inadvertently rendered it as a MOV file, which resulted in a 6.5GB file (I usually use MP4) and it took about 14 min. I then rendered it once more, which again took about 14 min but resulted in an 3.1GB MP4 file.

I'm not sure what Blackmagic has done (some sort of magic), but Resolve is working significantly better every update.

  • Like 1

Share this post

Link to post
Share on other sites

@Australian Image it probably comes under " Multiple performance and stability improvements." 😁

It is great that it continues to get better with each major & minor release.

Share this post

Link to post
Share on other sites

I've discovered why I appear to be able to render so well with noise reduction in the process. Previously Resolve was utilising up 100% of CPU resources and maybe 20-30% of GPU, now it's the reverse. I'm using an MSI gaming laptop with 32GB RAM and which has a discrete GeForce GTX 1060 6 GB GPU.

I was doing another render with even more noise reduction applied and added a dissolve between two clips and unfortunately the rendering stopped at the transition. So I removed the transition and tried again without the transition. This time it worked. So I reapplied the dissolve and added background music, but again it failed at the dissolve (with a error).

So I removed the dissolve and rendered once again, without doing anything else with the computer, and this time it came out fine. I'm surprised that the transition was enough to kill the render, as I thought that the CPU usage being so low would have assisted in the process. Next time more light, so less need for noise reduction. And I'll have to remember to remove my VND beforehand as well.


Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Popular Topics

  • New Posts

    • Actually, I need to make a correction regarding the battery capacity. The Canon LP-E6N has a 14Wh rating; whereas, the Canon BP-A30 battery has a 45Wh rating. That's 3.2x the BMPCC4K/6K battery capacity. My IDX NP-F970 equivalent batteries (at 48Wh) give me 188min of 4KDCI recording time (which I gather is far more battery intensive than what the C70 can record), so that's as good, if not better than what the C70 gets out of a BP-A30. The BP-A30 is also physically not much smaller than the NP-F970 battery. Just thought I'd add that info.
    • So Canon has introduced a camera that has a similar design to that of the BMPCC4K/6K, only bulkier. I'll be curious as to whether all the criticism levelled at the design of the latter will be levelled at the former. Perhaps Blackmagic's design wasn't all that bad after all. The C70 also seems to be a bit crippled in what formats are available, but then that's fairly typical with Canon. Edit I: I notice from the comments that there are still those who can't seem to live without a built-in EVF. Edit II: I also notice that there are still people about that complain about the lack of a 5" flip-out screen on the BMPCC4K/6K, the supposedly poor battery life, and now a lack of top handle. The so-called poor battery life of the BMPCC4K (especially) is a real bugbear to me when I hear it. The LP-E6N battery is only 1865MAh; whereas, the BP-A30 is 3200MAh, almost double the capacity of the BMPCC battery. With two LP-E6N batteries, I can get close to 150min of recording time, which is not too bad. With my current setup using an NP-F970 and LP-E6N, I can get four hours of 4KDCI recording. And those NP-F970 batteries (IDX) are far cheaper than the Canon BP-A batteries. Just thought I'd get that off my chest.  
    • @Günther Göberl. I'm not sure what it is, but anything especially to do with landscapes always appeals to me more when it's in a wide format. That project, for me, would not have had the same impact in say a 16:9 format, it would have had a made for TV impression. My view is do what you want, not what someone else dictates. And if some festival dictates a format that kills your creativity, and all that you're then doing is making a film to suit the festival, why even bother?
    • I also opted for 1:2.35 for this project  
    • If you need or reply on peaking alot ,I would recommend changing to "normal" ,set a level and leave it on all the time .. I used to use color (red) but was given the same advise and its really alot better .. 
  • Create New...