Resolve 8: Reduce number of concurrent correctors

[Dwaine Maggart]

Do you have a GUI card in addition to the 285, or do you have your GUI display connected to the 285 card?

I’ve never seen an error message like that. Can you give us the exact error message, and where you see it, i.e. at application launch before logging in, or after you’ve logged in and are doing something with a project?

What version of OSX are you running?

Dwaine Maggart
Blackmagic Design DaVinci Support

[Christopher Adams]

I get it anytime i start the program. then if i do any scrubbing and or corrections. This maybe related to the issues i talked about above too. see the 9600M gt ticket for the error message. Not sure if this is the same one or not though.
CJ

[Andreas Wideroe]

I’m running 10.6.7.

I only have one 285 card in the machine serving both as a GPU and GUI.

Resolve starts up fine, but at the user login screen I get a warning saying The display GPU is being used for image processing. Depending on your system configuration, thes may result in sub-optimal performance. For maximum performance we recommend that your systen uses a specifiction from the configuration guide. OK

So I know things may happen… 🙂

I open up a project and browse for a file. Right now a Prores 4444 file in HD. (same for iphone movs and 10bit sd mov). The picture of the file looks good. I press play in the browse screen and the video plays back fine. Also works in conform. I click Color, it plays back (slow 9fps without any corrections).

I pull Custom Luminance a tiny bit, the system “hangs” for a second or two and then I get this message:

Error running GPU algorithms. GPU memory might be exhausted. Try reducing number of concurrent correctors.

The video is now garbage (lots of colours and hardly anything recognizable).

Looks like it’s the same problem as the other poster above.

And yes, I know my system isn’t supported. 🙂 I will get another 285 card later this summer I hope.

Would be cool if I could get Resolve running version 8 on the current system though. If not I’ll revert back to 7.

Cheers,
Andreas

—
Norsk Smalfilm AS
https://www.smalfilm.no

Filmshooting | Com
https://www.filmshooting.com

[Dwaine Maggart]

You don’t need to add another 285 card. Just adding a cheap GT120 card, or the ATI 5770 card would make a big difference.

The error message is new for version 8. In version 7, I think you just would have seen a beach ball hang in that scenario. Now we catch the error and warn you. I’m sort of surprised it would be worse in V8 than it was in V7. But things have changed, so maybe. You say Custom Luminance is causing the problem. Do any other controls work any better? If you make an RGB Gain change, or change the Sat level, will that also cause the message? Or just Custom Luminance?

Dwaine Maggart
Blackmagic Design DaVinci Support

[Christopher Adams]

Here are the times i get it:
+ sign for new project. after naming it i get the error:
Browse tab clicking on a clip when the video preview comes up. error
adding a clip to media pool is fine.
creating a new master session is fine
tab over to color page is fine
Then almost any adjustment i make will trigger the error:
Curves
soft clip controls don’t trigger it but the master rub curve adj. do
NEW X vs. y curves seem to NOT trigger it
HSL qualification clicking triggers it!
HSL adjustment sliders do NOT
+ and – and +S -s Do not
Power widows do not seem to cause it
switching to blur tab DOES once its dismissed hitting ok. blur mist etc sliders don’t cause it again
Key tab sliders seem to NOT cause it
Main color page:
Offset color controls DO cause the error
This however is NOT consistent. Once you dismiss an error controls that DID cause it won’t’ the next time.

Just a few things i noted.
Also no update on any of the video its all scrambled.
No matter what controls i adjust no effect on video even if i desat or totally crush it. doesn’t matter.
window shows some video though it then mostly corruption.

Version 7 worked fine on this same machine. config
I also didn’t see much beach balling at all

[Andreas Wideroe]

I could tweak saturation and the others (tilt, hue, rotate, pan and so on), but as soon as I press play the system hangs for a second and boom … the message. 🙂

Btw, I just bought a GT120 card from eBay. Hopefully my problems will be gone in a week or so when the card arrives.

—
Norsk Smalfilm AS
https://www.smalfilm.no

Filmshooting | Com
https://www.filmshooting.com

[Christopher Adams]

I guess i have a more fundamental question.. 7 did work fine on mac book pro 15 inch as long as you had HD screen res etc. is the macbook pro 15 with the 9400, GT not at all supported?
even with the limits of SD / HD etc

[Dwaine Maggart]

Hi Andreas,

I’ve just done a test here. I have a system with a GT120 and GTX285. I made a project with a ProRes444 HD file, and did 5 nodes of various types of corrections. It works fine. I pulled the GT120 card. I do get the warning message now about the display GPU being used for processing. I load my ProRes444 project, and it works fine. Just to be sure, I made a new project with the GT120 card removed, and did primary, secondary, windowing and blur, and it all worked fine. The blur (5th node) did drop me out of real time playback, but that would be expected with a single card. But no noise artifacts as you describe and no other error messages.

I am running OSX 10.6.8 with the newer Nvidia 256.02.25 and CUDA 4.0.19 drivers. That might make a difference, but I doubt it. This system is also a 4,1 2009 Mac Pro. What type of Mac Pro do you have? If it’s a 2008 3,1 system, that might be an issue.

If you could send your Mac System Profile file in XML to davincihelp@blackmagic-design.com, we could take a look and see if anything looks odd.

Dwaine Maggart
Blackmagic Design DaVinci Support

[Pablo Nóbrega]

I have the same issue running with one GTX 285, this message and crashs… I had to back to version 7 to finish the work… did you find a solution? Maybe the CUDA or Nvidia newest drivers?

[Christopher Adams]

I added these to debug for my macbook pro 2.93 works fine so far. no more error.
even on Lion 10.7 For Resolve 8.0.3

LsManager.3.NumGPUs = 1
LsManager.3.GPUMapping = 0
LsManager.3.GPUMappingEnable = 1

NOTE: You will have to Save and restart Resolve for these settings to take effect.