Blackmagic Forum

Hi,
I have a problem with Davinci Resolve 11.3.1 when using neat video v4. When the ofx plugin is applied on a few clips (it doesn´t matter if it is render cached or not) an error message pops up saying: "GPU out of memory"
hope that Blackmagic Design is aware of this problem while preparing v12.
this is indeed a problem which is annoying cause it prevents me from using the tool.

please help, perhaps there is an easy work around?

thank you very much
greets. p

What GPU(s) are you using and how much VRAM do they have?

What is your timeline resolution?

ah. ok. sorry.
my gpu is a nvidia gtx 680 with 4gb ram and the timline resolution is: 2k dci scope 2.39 2048x858 (this will also be my final resolution).
i have no problems when not using neat video


thx

What settings are you using in neat video? I'm no programmer but I do know that noise reduction uses a lot of vram so maybe it is analyzing too many frames/doing too much noise reduction and your GPU can't hold all the info. Also considering it is a plugin you may want to check in with their forum/site/support. They might have a better idea how the plugin works with what types if GPUs

Neat Video can use GPU memory but not necessarily so. That can be disabled completely.

Please disable any use of GPU by Neat Video in its Preferences (Performance tab) for a test. If that helps to avoid those Resolve errors then the problem may indeed be caused by both Resolve and Neat Video using the shared GPU memory resources concurrently.

Please try that and let us know.

Thank you,
Vlad

Hello!

I wonder if i am the only one who has such problems. but thank you for the tip, i will try to disable gpu for testing purpose.

thank you. Peter

We received several other reports of similar problems when Resolve produced such an error message ("GPU out of memory"). That happens with and without Neat Video and seems to depend on the additional load placed on Resolve render engine by effects, filters, plug-ins used in a project. Resolve seems to be using more GPU memory in such circumstances and eventually runs out of it.

Using Render Cache may also contribute to that problem. Using the same GPU for both Resolve processing and display may be a factor too.

I hope Resolve developers will offer some additional insight and guidelines on how to deal with this problem.

Vlad

Thank you for the insight. Will test some different settings.

Exact same problem here. Just bought Neat yesterday and immediately got the GPU MEMORY is full error. Been troubleshooting with Vlad via email. My issue is specific to Neat video plugin. I use other OFX plugs in Resolve and Haven't seen this error before. I'm on a PC windows 8 with 2 GTX980's. My footage was shot 4k on the FS7 so XAVC MXF's.. We thought it might have to do with the node heavy session I was working in so I tried launching a fresh session applied Neat to a single clip in the timeline. Same error.

That may be a bit different.

AFAIR, Resolve officially requires 6GB of video memory or more to work in 4k resolution.

Do those GTX 980 have 4 GB each?

Vlad

yes I believe so..4GB per card

I have re-checked the available documentation (which seems to be somewhat outdated - about 1 year old) and it looks like while the Mac version requires at least 6GB (for 4k), the Windows version only lists "4GB or more". So formally speaking, Resolve for Windows should be able to work without those glitches you observed (random noise in preview, error messages about GPU memory). Therefore this seems to be yet another case for BM support.

Dear Blackmagic people, please take a look at this problem. According to the official specs, 4GB of GPU memory should allow Resolve to work with 4k timeline without problems yet glitches and error messages are observed.

Please advise how to resolve this problem.

Thank you,
Vlad

after testing i really have to say that this problem is really annoying. also with only cpu enabled in neatvideo, the error appears.
so please both blackmagic and neat, try to fix this. the error also happens when only !!! one !!! clip is in the timeline.

greets pete

Hello all,

Sorry for my english i'm french.

I use Neat video V4 with avisynth/virtualdub and resolve V11. (I use Neat video from V1 because I love this filter)

I created profiles and presets under avisynth (neat V4) with a temporal radius of 2 images (default). When I want to use the same profiles, these presets in Resolve does not work, even after the render (SMART or USER):

1) I have to put a temporal radius 1
2) I can not use the Dust and Scratches (works well under avisynth / VirtualDub) but never with RESOLVE.
3) I also use BCC OFX 9.03 continuum and once done made the smart or user RENDER, I have a perfectly smooth playback but even when rendering is done with NEAT, reading is never fluid.

Where is the mistake?

We have just uploaded updated builds of the Neat Video v4 OFX plug-ins that include several minor modifications intended to reduce load on Resolve.

Please update your copy of Neat Video and try to use the new build to see if it helps to avoid those problems with Resolve. Preliminary reports suggest that it does help, at least in some cases.

Please note that we have been implementing these changes from our side alone, without any help from Resolve developers. They have not yet responded to these forum posts nor to our direct e-mails and requests for assistance. So unfortunately it is only us so far and our capabilities regarding making Resolve stable are very limited. Therefore we would still very much like to hear from the developers of Resolve because both users of Resolve and developers of plug-ins for Resolve need some guidelines on how to deal with these problems.

Thank you,
Vlad

Hello Vlad,

Thank you ! i just download this new version and test it.

I come back after test and i hope good news for us, i wish with my gtx 980 TI.

Best regards.

Jean Claude,

I was mostly replying to other users who reported GPU memory problems above.

Regarding your questions:

- I recommend to build new profiles in Resolve because the noise may be different in Resolve as compared with avisynth/virtualdub;

- "Resolve does not work" - what do you mean exactly?

- "Dust and Scratches" doesn't work (1) in preview of Neat Video itself, (2) in preview or Resolve, or (3) in the final render results of Resolve?
(2) and (3) should work. (1) should not, because of the current functional limitations of Resolve itself who does not provide all required frames to Neat Video (as described in our webpage);

- if playback is not fluid in Resolve, please kindly report this to the developers of Resolve.

Thank you,
Vlad

Hi,

Sorry for the delay but I wanted to do and redo all tests.

I recomme a new project with new clip 1080p 25 fps: Call Neat Video 4.05

The clip comes from Sorenson Squeeze v10 in DNXHR 10 BITS, cache frame to resolve (general options) => DNXHR HQX

- From a new DEVICE NOISE PROFILE "AUTO" and NOISE FILTER SETTING preset "Reduce noise and sharpen" (default temporal 2): ​​render smart or user => results OK preview and delivery

- Even DEVICE NOISE PROFILE "AUTO" and NOISE FILTER SETTING preset "Reduce noise and sharpen" + custom improvement (default temporal 2): ​​render smart or user => results OK preview and delivery

- Even DEVICE NOISE PROFILE "AUTO" and NOISE FILTER SETTING just custom improvement (temporal 3): render smart user => results OK preview and delivery

dust and scratches :

even DEVICE NOISE PROFILE "AUTO". Loading C: \ Users \ Jean-Claude \ Documents \ Neat Video v4 OpenFX \ Presets \ Advanced \ Dust and scratches \ conservatively Reduce dust and scratches => PREVIEW is OK but the KO result during read and delivery...



even DEVICE NOISE PROFILE "AUTO". Loading C: \ Users \ Jean-Claude \ Documents \ Neat Video v4 OpenFX \ Presets \ Advanced \ Dust and scratches \ agressively Reduce dust and scratches => KO in preview in NEAT SCREEN + the result is KO + DELIVERY IS KO.



And the dust and scratches
Then GIF attachments is not to clean but you can see the default (jerkly).

Can all Resolve ant Neat can help us ?

Best regards.

1. Does that original clip have any actual dust and/or scratches (that typically come from scanned film)?

2. As you can see in the bottom of the Neat Video window, Resolve does not provide those adjacent frames to Neat Video, so some of the functions (including the Dust and Scratches filter) cannot work correctly within that window, simply because there is not enough input data yet. Those functions may work in final render, but not in preview inside Neat Video window. That is why there may be some difference (if you use temporal features like Dust and Scratches) between preview inside Neat Video window and final render results of Resolve. (Please note that this is a problem of Resolve only. Other OFX hosts work properly in this respect. You may want to ask the developers of Resolve to improve Resolve to make it at least as capable as other OFX hosts such as Nuke, Scratch, etc.

3. If you want to demonstrate any specific filtration problem and get some help or advice about the filter itself from the developers of Neat Video, please prepare a small test project (allowing to reproduce the problem) with a short clip and send the project and clip to support [at] neatvideo.com. Please include a short description of steps required to reproduce the problem using the test project as well as any additional comments that may be needed. Neat Video support staff will reproduce the problem on their machines and will then advise on how to deal with it.

In this particular thread, the main topic is the "GPU out of memory" error shown by Resolve in situations of high load, including situations when Neat Video is used. I suggest to discuss that problem here. The goal of that is to collect practical examples of the problem, circumstances where it shows up, and to help the developers of Resolve to address this issue in a more systematic way.

Thank you,
Vlad

Hi Vlad Hi, Thanks for your reply,

(Sorry, i use google translation, my English is far from perfect...)

I'll answer point by point:

1) Yes, it is a clip from a telecine transfer EUMIG super-8 => 1080p via a NIKON camera lens. I do this type of transfer for over 20 years and that is not the issue. Like all telecine super-8 transfers (and this is its charm) there always has dirt and scratches but the goal is to reduce a little.

2) I have seen that in the OFX version Neatvideo 4, unlike other HOST (ie VirtualDub or Adobe) there is not in the preview at the bottom of the window with adjacent images around the current one that allow scroll hotizontal. I understood in First, it affected only the preview, not the final rendering in theory. But in fact, the delivery is also affected by my results.

It remains unless it without the dust and scratches option, the temporal operation works well, so I deduced that the absence of adjacent images in the PREVIEW affect rendering.

You say: Please, note that this is a problem Resolve only. Other OFX hosts to work properly this. You may want to ask the developers improve Resolve and Resolve to make at least as capable as other OFX hosts such as Nuke, Scratch, etc.

So if the TEAM DAVINCI RESOLVE wanted to solve this problem quickly, it would be nice to be positioned RESOLVE at a level equivalent to other OFX hosts such as Nuke, Scratch, etc. And I thank them in advance.

But I ask this while I use the lite version ?

3) Thanks for the offer : I use Neat video since version 1 and again I have no trouble using it. I do not have problem getting a more than 85% profile. I recall that I also have version 4 virtualdub, version 3 media composer and recently version 4 of resolve. After Resolve have like other OFX hosts adjacent images around the current one, and if i can't have a good delivery, i go to your support.

For now if you want, il can provide for everyone my clip extract + project + my profile neat => no problem. Thank you to confirm and links for upload.

Regarding my comments in this particular thread to the main topic is the "GPU memory" according to you, for me it is globally "Davinci 11.3.1 Lite Problem with Neat Video V4 OFX" but if you wish, I can open another topic.

Thank you again for your help and this good filter.

Jean Claude,

Thank you for your reply. I suggest to continue the discussion related to the filter itself by e-mail.

Please kindly send an e-mail to support [at] neatvideo.com and if possible include a small test project with a short clip allowing to reproduce the problem (lack of reduction of dust&scratches in final render). We will run the project, render out and check the results. Normally, the results should show proper reduction of dust and scratches (provided of course that the filter settings of "Dust and Scratches" are set correctly).

I believe our posts here have already made it clear to the developers of Resolve that providing adjacent frames to Neat Video window is as important as providing those frames to the filter during final render (which Resolve does provide).

Again, I suggest to continue discussing the Dust and Scratches filter by e-mail. I see no need to continue that here or in another topic.

Thank you,
Vlad

Dear Blackmagic/Resolve people,

Please confirm how much GPU memory is officially required by Resolve 11 (Windows) to work with 4k timelines without Resolve running into that "GPU out of memory" error.

Please take into account a situation where:
- Resolve runs a project that uses Neat Video with its temporal filter radius set to 5
(which means Neat Video can request Resolve to provide up to 5+1+5 input frames to produce one output frame);
- Neat Video is set to NOT use the GPU (to make sure Neat Video doesn't consume the GPU memory, only Resolve does).

What amount of GPU memory would be then be required by Resolve? Is it 4GB or 6GB? Or is there no definite threshold amount that would guarantee the absence of the "GPU out of memory" errors coming from Resolve?

Thank you,
Vlad

Hi,

I just make a test with a clip was i downloaded from Blackmagic : Night Shot Store where is the first time 4K shoot is available( thank's) in a new project : 4K UHD.




So... i put it on a new projet..new timeline...new call from Neat Video...new profile

just make a new preset 5 temporal frames and start from resolve => neat => preference => test... and optimizing performance Setting :



But after this : resolve freeze after accept best combinaition :

(Pas de réponse = freeze)

May be is a problem from memory is locked or leak. I can accept the : with my configaration that my PC freeze. Sorry !

My CPU : Type de processeur QuadCore Intel Core i7-3770K, 4400 MHz (44 x 100)
My GPU : NVIDIA GeForce GTX 980 Ti (6 Go)

Best regards.
Jean Claude

Does Resolve freeze after you click the "Apply" button in Neat Video plug-in?
Or does it freeze right after you click the "Accept Best Combination" button?

Does that happen if you do not run Optimize Settings at all but instead just manually set the Performance settings to use CPU (4 cores) and GPU and then click OK to save these settings?

How much GPU memory is reported by Neat Video in the Performance tab?
How much of the available GPU memory is allowed to Neat Video?
Please try to set it to something like 30% and check if this helps Resolve.

Thank you,
Vlad

Sorry for the delay but I wanted to make and remake my tests (long time.....) :
(I made screenshots at all stages and due to provisions if you want)

1) full uninstall of the NVIDIA drivers included with my GTX980 TI : V3.06
2) Cleaning the installation with Guru3D: DDU (startup SAFE mode and clean drivers
3) Restart in normal mode and installing the latest NVIDIA version 3.30
4) resolve Uninstaller + restart PC
5) reinstall it + restart PC + LAUNCH RESOLVE
6) creating a 4K UHD + clip loading project (from blackmagic: Night Shot Tram.mov (3820x2160)
8) creating a timeline UHD + put the clip
7) ON EDIT tab => smooth playback
8) TAB COLOR => PLAYBAK => RENDER CACHE => USER
9) placing the filter on the clip (neat V 4.05) (default temporal 2)
10) directly into preference => optimzing performance (2 frames) + 5 result cores + GPU = 3.36 fps : OK. After automatic profil + preset 'filter and sharpen'
11) Click on NODE => NODE CACHE => on
== >> Rendering starts but stops after 20 seconds and after nothing. On task manager = not to totaly freeze but stay at 1.1
12) TAB COLOR => PLAYBAK => RENDER CACHE + NONE
13) TAB COLOR => PLAYBAK => RENDER CACHE DELETE ALL
14) resolve OUTPUT
15) Uninstall NEAT + 4.05 REBOOT THE PC
16) Installation of OFX NEAT 3.06
17) reboot the PC + LAUNCH RESOLVE
18 Creating a 4K UHD project + clip loading (from blackmagic: Night Shot Tram.mov (3820x2160)
19) creation of a UHD timeline
20) EDIT TAB : smooth playback
21) TAB COLOR => PLAYBAK => RENDER USER CACHE => USER
22) placing the filter on the clip (neat V 3.6) (TEMPORAL 2)
23) directly to OPTIMIZING PERFORMANCE SETTING => 3 cores + GTX 980 TI: 4 FPS (better version 4.05)
24) Auto Profile + filter setting: same: FILTER AND SHARPEN
25) Click on NODE => CACHE NODE => on
== >> Rendering starts but stops after 20 seconds and after nothing.
26) QUIT RESOLVE


Launching media composer
1) creation of a UHD + project creating a time line
2) AMA LINK same clip
3) CALL FILTER neat video + 3.6 temporal filter 2 but there: 16-bit?
4) Optimizing Performance: GPU + 3 cores : 5.35 fps (more better)
5) render the effect very quicly
6) very good result.

Thank you for your help.

I had planned to migrate slowly towards media composer 8.4 to RESOLVE V12 and buy the full version but now I am reviewing my intentions. And customers are not ping-pong balls: thank you to listen to your customers.

Thank you for your help.

Best regards.

Thank you very much for describing the steps in details.

We will try to reproduce this on our test machines with Resolve. Steps 11 and 25 certainly look abnormal.

Thank you,
Vlad

Hi,

Just found one temporary solution for use Neatvideo 4 and temporal 5 and now the render
the rendering is complete (same clip : Nigth shoot tram.mov) 4K UHD
1) tab EDIT => menu playback => Render Cache = USER
2) TAB color => windows 'NODE' change clip to timeline.
3) Use Neatvideo filter => profil auto + temporal 5
4) come back to tab EDIT
5) tab EDIT => The render start and finish

Load in GPU memory is 3435 Mb when CPU + GPU .

See attachment : Resolve + GPU-Z + control panel W8.1. AFter end, the plackback is not smooth but may be my hard drive...(not in raid HDD). Is a Plan B..





Load in GPU memory is 5808 Mb when GPU ONLY.




Best regards,

We have not yet been able to reproduce that specific freeze of Resolve (as described in the steps 11 and 25 above). Usually, Resolve just complains about the GPU memory shortage, but doesn't freeze in our tests.

Still, it is very good that you have found a workaround for your situation. We are going to try your new steps too. Thank you for your sharing!

Vlad

P.S. Developers and support of Resolve: please also try to help your users.

Hi,

For step 11 & 25, not freeze totaly but just 1.1% CPU used...

Does the stafs Blackmagic and NeatVideo have a solution for my problem?
Otherwise, lack of time, I'll stay on a real NLE: media composer / Symphony 8.4

Best regards,
Jean Claude

The problem seems to be in Resolve. Other OFX hosts as well as other applications like Media Composer, FCP, AE, Premiere do not show the same issues.

Dear Blackmagic people, please help your users. We are ready to provide you with any required assistance from our side.

Thank you,
Vlad

It does not work! have the same problems.GPU FULL:
I tried different video cards ati 7990 6gb, r 290x 8GB, 980 ti 6gb .
i use 1 videcard only for gui and 4 gpu for Color.
At all resolutions not working .. and Davinci freeze.
For now remain on Neat 3.6, this also works with all resolution , and Raw files 6k RED without problem.
Vlad, what cards you are using to avoid problems?

foto is apple prores hq 1920x1080 25p. with error GPU FULL.

Please clarify, what is the resolution of the input clips and what is the timeline resolution?

Does that happen if you completely disable use of GPU in Neat Video v4 itself (to leave the GPU to Resolve)?

Thank you,
Vlad

Hi,

Beautifull


I come back to this discussion and clearly blackmagic's team and Neat video made a big effort to optimize the rendering between DaVinci and resolve Neat video.

I think there is a good balance between CPU usage and GPU.

The screen is made during the render clip => color page => playback => render cache : user => right clic node => on

Davinci resolve (lite) 12
GPU: GTX 980 TI.
i3700k/4400Ghz
16 Go RAM,
Video HDD = SSD
Render HDD = SSD

The clip is a UHD (3840x2160) from Blackmagic,
Neat Video 4.08, temporal is set to 5,
+ Tweaks on the same node,
i use on a SSD caching and rendering clip is very good and fast (and delivery)

Congratulations to the teams to leverage the performance of the hardware and compensates investment.

But I get a better reading good and normal 24 fps) of the clip made after leaving resolve and restart the software (should update the cache?) But in all cases it is much better.

Best regards.

Hi Jean Claude.

I'm wondering how your render looks like. I and other users can"t render OFX plugins with DR12 (my sapphire & Filmconvert are full of glitches). Is neat video rendering without issues?

For now i downgrade to DR11 and all is fine again.

Jean Claude wrote:Neat Video 4.08, temporal is set to 5

I also recommend to update to 4.0.9, it was uploaded recently and may be useful with your config.

Thank you,
Vlad