Blackmagic Forum

edgley wrote:on a side note, all the tutorials ive been watching have said to use NR first, then CC.
However, I read hear that users are doing it the other way around.

This has been debated for years. My take is that sometimes, I'll slam the hell out of gain to match levels, and that predictably raises the noise level within the shot (all things being equal). So to me, it's a question of how far I'm stretching the dynamic range. The NR has to happen at the end because so much happens before that that affects the noise level. In some cases, I might bypass NR entirely because the picture is already pretty clean.

this is still happening to me with a HP z820 with:
-2 Xeon e5-2640v2
-32gigs ram
-Cuadro k4000
-declink 4k BM display card
-cubix xpander with 3 titan black 8gigs each 18g total
-SSD OS win 10
-Davinci STUDIO

i've been working with no problems until davinci 14 with a lot of nodes in the projects NR included and never had this issue ... now im struggling every time i try to open one of those projects. ive done clean install, transcoded clips, the OS is perfect with every driver up to date... the 3 titans never reach to work at 100% and suddenly i get the "your gpu memory is full" error, and yes this happens mostly when i hit the NR node, which i repeat was PERFECTLY WORKING in resolve 14

Can you take the Quadro K4000 out?

VRAM is not pooled, so you are being limited to the 3GB of the K4000. I would remove that card.

Stop&Play wrote:this is still happening to me with a HP z820 with:
-2 Xeon e5-2640v2
-32gigs ram
-Cuadro k4000
-declink 4k BM display card
-cubix xpander with 3 titan black 8gigs each 18g total
-SSD OS win 10
-Davinci STUDIO

i've been working with no problems until davinci 14 with a lot of nodes in the projects NR included and never had this issue ... now im struggling every time i try to open one of those projects. ive done clean install, transcoded clips, the OS is perfect with every driver up to date... the 3 titans never reach to work at 100% and suddenly i get the "your gpu memory is full" error, and yes this happens mostly when i hit the NR node, which i repeat was PERFECTLY WORKING in resolve 14

On feb 7 2019 you can buy yourself a 16 GB Radeon7 for only $699.
1 Vega will have around the same or more effective speed than 3 titan blacks.

VRAM is not pooled, so you are being limited to the 3GB of the K4000. I would remove that card.

Or specify the K4000 for the GUI only ?

Alexandre Westphal wrote:

VRAM is not pooled, so you are being limited to the 3GB of the K4000. I would remove that card.

Or specify the K4000 for the GUI only ?

Or do that.

6 GB is on the low side for 4k.

Here are the specs of the Titan Black https://videocardz.com/nvidia/geforce-700/geforce-gtx-titan-black

I would just remove the k4000 and the cubix with the titans and put 1 (or 2 when you have the money) radeon7 in it.
The declink takes care of the 10 bits color, so also no worries about that.

hello, sorry i ignored you guys responses but i've been super busy!

-yes the k4000 is being used for GUI only, and it was everything fully configured in resolve to do so.
-And i already solved the problem... HOW?

After a lot of pain, mails, and investigation... somehow resolve 15 decided to use the 18gigs (i made a mistake, it was 6gb each titan) for GPU rendering BUT it was still thinking the k4000 was the only Vram available. So i had to get inside the Nvidia configuration and under the Cuda option exclude the k4000 from cuda there, now everything is back to normal. the thing is that in resolve 14 this wasn't necesary.

And yes i know 1 new card would do the job today, we are actually looking to move to a new custom machine with new horsepower but i had to make this one work asap with no money on my pocket.

I don't have this issue anymore in 15.3. Sigh. I have others.

I know I am hopping in pretty late into this thread and I too had this issue with my TITAN X Maxwell card with 12GB throwing up Memory Full errors when i was on DR 14 Studio.

But once I forced Resolve to choose the card I didn't have that issue any more.

Now though I am using a Sapphire Radeon RX 580 Nitro+ with just 8GB, I have never faced that issue ever after and I still work on UHD files.

I have the same issue but it seems to be related to only the footage from my blackmagic raw footage. I did the same level of noise reduction on the Sony A7SII footage no issue. I have the same issue on Davici 15 & 16 beta.