Page 1 of 1

Resolve 17.2.1 issues

PostPosted: Sat Jun 05, 2021 8:40 pm
by jallen0
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?

Re: Resolve 7.2.1 issues

PostPosted: Sat Jun 05, 2021 9:27 pm
by Jack Swart
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.

Re: Resolve 7.2.1 issues

PostPosted: Sat Jun 05, 2021 9:36 pm
by jallen0
Yes, I do have 12.1 installed. It was a good thought however.

Re: Resolve 17.2.1 issues

PostPosted: Sun Jun 06, 2021 3:24 pm
by Jim Simon
1. That's not normal.

2. That's not normal, either.

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

Re: Resolve 7.2.1 issues

PostPosted: Sun Jun 06, 2021 3:59 pm
by ricardo marty
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

Re: Resolve 17.2.1 issues

PostPosted: Sun Jun 06, 2021 11:43 pm
by Uli Plank
That's correct, you don't need it if you have no I/O device by BM.

Re: Resolve 17.2.1 issues

PostPosted: Mon Jun 07, 2021 12:07 am
by Marc Wielage
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.

Re: Resolve 17.2.1 issues

PostPosted: Mon Jun 07, 2021 12:26 am
by jallen0
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!