Resolve 17.2.1 issues

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

jallen0

  • Posts: 1088
  • Joined: Sun Jun 21, 2020 7:04 pm
  • Real Name: Justin Allen

Resolve 17.2.1 issues

PostSat Jun 05, 2021 8:40 pm

Let me preface this by saying that over the last several weeks I have not done much editing. I am currently running the latest OS x and Resolve versions and I am having multiple issues, especially regarding rendering. These issues are:

1) Multicam filmstrip and audio waves will not show up unless you start playing over a specific clip inside the multicam timeline. This makes it very hard to find the clips you are looking for.

2) I am using a few simple Fusion titles and every time I make a change to it there is a 5-6 second lag when trying to play the timeline, or change even a simple zoom elsewhere on the timeline while it tries to render. Basically if the machine is rendering then everything else comes to a stop. Before anyone says it's my machine, please look at my specs below.

3) Adding a noise filter on my footage basically renders the edit impossible to use. My noise node is first in line. I also understand that the noise node is one of the hardest ones to use, but should it really be unplayable?

I have a few other little things that are issues as well however it all leads up to the fact that Resolve is almost impossible to use for this edit. BTW the footage is two streams of 6K BRAW footage, and some fusion titles.

Is anyone else seeing these issues or have any thoughts?
2019 MacPro OS 12.1, 3.2GHz 16 Core, 160GB Mem, 4TB Drive, 8TB Internal Sonnet Raid, Dual Radeon Pro W5700X 16GB
LG UF 5k, 27" Tbolt Display, 55" LG C8
Resolve Edit Keyboard, Mini Panel, US 4K Mini
Resolve Studio Ver. 17.4.3
Desktop Video 12.1
Offline
User avatar

Jack Swart

  • Posts: 769
  • Joined: Fri Aug 15, 2014 8:09 pm
  • Location: Sydney, Australia

Re: Resolve 7.2.1 issues

PostSat Jun 05, 2021 9:27 pm

Have you updated to the latest BM desktop video driver?
It is version 12.1.
I had terrible performance until I did.
I'm running a 8 year old Mac Pro and it is fine even up to 4K Sony Raw and 8K ProRes.
DR Studio 18.6.3 b19, OS 13.2.1
2023 Mac Studio M1 Ultra, 20 core CPU, 48 core GPU, 128 GB ram
BM 3G ultra studio, 12TB SSDs in raid 0, 16TB HDD backup, 56TB archive server.
Tangent Elements panel, TV logic XVW-245W
Offline

jallen0

  • Posts: 1088
  • Joined: Sun Jun 21, 2020 7:04 pm
  • Real Name: Justin Allen

Re: Resolve 7.2.1 issues

PostSat Jun 05, 2021 9:36 pm

Yes, I do have 12.1 installed. It was a good thought however.
2019 MacPro OS 12.1, 3.2GHz 16 Core, 160GB Mem, 4TB Drive, 8TB Internal Sonnet Raid, Dual Radeon Pro W5700X 16GB
LG UF 5k, 27" Tbolt Display, 55" LG C8
Resolve Edit Keyboard, Mini Panel, US 4K Mini
Resolve Studio Ver. 17.4.3
Desktop Video 12.1
Offline

Jim Simon

  • Posts: 36138
  • Joined: Fri Dec 23, 2016 1:47 am

Re: Resolve 17.2.1 issues

PostSun Jun 06, 2021 3:24 pm

1. That's not normal.

2. That's not normal, either.

3. This is pretty normal, depending on hardware and settings.
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

ricardo marty

  • Posts: 1761
  • Joined: Wed Apr 26, 2017 4:03 am

Re: Resolve 7.2.1 issues

PostSun Jun 06, 2021 3:59 pm

Jack Swart wrote:Have you updated to the latest BM desktop video driver?
It is version 12.1.
I had terrible performance until I did.
I'm running a 8 year old Mac Pro and it is fine even up to 4K Sony Raw and 8K ProRes.


I thought that the bmd desktop video driver was only for use with exteriors monitoring as a client or grading monitor. What its purpose>

Ricardo Marty
DV Studio 20.| Asus ProArt PD5, 2.5 GHz i7 16-Core 64GB nvidia 3070 572.83| Apple M4 10-Core 24GB Unified RAM 512GB-Core Neural Engine | Lenovo 7x Snapdragon 78-100 12 core elite 32gb ram adreno gpu, Win 11.| Sony A6700. PreSonus AudioBox |Speed Editor
Offline
User avatar

Uli Plank

  • Posts: 25480
  • Joined: Fri Feb 08, 2013 2:48 am
  • Location: Germany and Indonesia

Re: Resolve 17.2.1 issues

PostSun Jun 06, 2021 11:43 pm

That's correct, you don't need it if you have no I/O device by BM.
My disaster protection: export a .drp file to a physically separated storage regularly.
Please visit digitalproduction.com/author/uliplank/

Studio 19.1.3
2017 iMac, MacOS 13.7.4, eGPU
MacBook M1 Pro and M4 Pro mini, MacOS 14.7.5
SE, USM G3
Offline
User avatar

Marc Wielage

  • Posts: 13285
  • Joined: Fri Oct 18, 2013 2:46 am
  • Location: Palm Springs, California

Re: Resolve 17.2.1 issues

PostMon Jun 07, 2021 12:07 am

jallen0 wrote:3) Adding a noise filter on my footage basically renders the edit impossible to use. My noise node is first in line. I also understand that the noise node is one of the hardest ones to use, but should it really be unplayable?

Generally, the advice is to cache whatever node you're using for NR, and then do the corrections and trims after that. I usually try to put NR in the middle of the Node tree, so I have a few early nodes that apply LUTs or CST's or Curves or Printer Light corrections to effectively "normalize" the look, then NR, then do all the trims more or less in the middle of the node tree.

When you say you're using 6KBRaw, are you doing it in a 6K timeline or a 4K timeline or what? I think you'll be fine in terms of an HD timeline just for making the decisions, and then switching it over to whatever resolution you need for the final. How exactly are you doing 2 streams of 6K? That's a pretty stressful load. If it were me, I'd use 2K proxies, get the edit done, flatten the file, and then reconnect back to the 6K camera originals.

Fusion is fairly demanding, even for a 2019 Mac Pro, so my general advice is to render those first and then deal with them as a flattened VFX file for final color, and not to render out color and Fusion in a single pass.
Certified DaVinci Resolve Color Trainer • AdvancedColorTraining.com
Offline

jallen0

  • Posts: 1088
  • Joined: Sun Jun 21, 2020 7:04 pm
  • Real Name: Justin Allen

Re: Resolve 17.2.1 issues

PostMon Jun 07, 2021 12:26 am

Thanks Marc. Let me try to answer your thoughts.

Marc Wielage wrote: Generally, the advice is to cache whatever node you're using for NR, and then do the corrections and trims after that.


Can you explain how to cache a node? Not sure what you mean here.

Marc Wielage wrote: I usually try to put NR in the middle of the Node tree, so I have a few early nodes that apply LUTs or CST's or Curves or Printer Light corrections to effectively "normalize" the look, then NR, then do all the trims more or less in the middle of the node tree.


Everything I had read said to put the noise node first. I'll try your way tomorrow and see if it makes a difference.

Marc Wielage wrote: When you say you're using 6KBRaw, are you doing it in a 6K timeline or a 4K timeline or what? I think you'll be fine in terms of an HD timeline just for making the decisions, and then switching it over to whatever resolution you need for the final. How exactly are you doing 2 streams of 6K? That's a pretty stressful load. If it were me, I'd use 2K proxies, get the edit done, flatten the file, and then reconnect back to the 6K camera originals.


I am using 6k footage in a 4k timeline. I have a dual camera set-up and one of them had a teleprompter. I learned too late that the teleprompter loses 1 to 1 1/2 stops of light and I was shooting low light anyways, so I have a lot of noise. My original ISO was 400. The footage without the teleprompter grades out nice...the camera right next to it is a nightmare for me right now. If I take the grade off os that footage I have zero issues in working with the timeline. I am not happy with that grade and am still playing with it every day.

Marc Wielage wrote: Fusion is fairly demanding, even for a 2019 Mac Pro, so my general advice is to render those first and then deal with them as a flattened VFX file for final color, and not to render out color and Fusion in a single pass.


I am using some call out titles that are loaded into fusion. ( https://groundcontrol.film/products/cle ... ght-titles ) I cannot imagine they are causing issues but I'll look at them again.

Thanks for your thoughts!
2019 MacPro OS 12.1, 3.2GHz 16 Core, 160GB Mem, 4TB Drive, 8TB Internal Sonnet Raid, Dual Radeon Pro W5700X 16GB
LG UF 5k, 27" Tbolt Display, 55" LG C8
Resolve Edit Keyboard, Mini Panel, US 4K Mini
Resolve Studio Ver. 17.4.3
Desktop Video 12.1

Return to DaVinci Resolve

Who is online

Users browsing this forum: Daniel Batinic, gregoriogalli, KevinGP, panos_mts, stevmcn and 465 guests