Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Resolve on Acid

D Fuller

Well-known member
Joined
Oct 13, 2008
Messages
2,040
Reaction score
0
Points
36
Location
Portland, Maine
Does anybody have any idea what the source of this render failure might be in Resolve?
LSDResolve.png


I get it when rendering a 1080p timeline from R3D sources (4K & 5K) with a mix of other sources. When it happens, the system starts to flicker between two or three bits of video as well. It starts about 2 mints into the timeline, and if I stop the render and start at point just ahead of the problem, it renders the material fine for another minute or two, then does it again.

This is on a nMP, D700s 64G RAM.

Any ideas?
 

Attachments

  • LSDResolve.jpg
    LSDResolve.jpg
    22 KB · Views: 0
There is a thread about this over at Lift, Gamma Gain, and another on the Black Magic forum. I'm really surprised this issue hasn't shown up here yet. It seems Red footage is usually involved when it happens. Also Open CL. Nobosy I know has reported it with CUDA.
 
I had this under 10.9.3 and resolve 11 on your hardware. It signaled then end of all GPU ability until 10.9.5. I saw it on all kinds of material, 1080p timelines. Definitely a GPU software bug. I have not upgraded to 10.10 yet.
 
So did it go away completely under 10.9.5?

If that's the case, it might be that a downgrade would be good until this gets sorted.
 
It's a Mac/Opencl error. Manifests more with large formats and heavy processing such as NR/OFX.
Install windows and resolve on your NMP and the issue will not happen there.
Hopefully a fix coming to Yosemite soon.
I've had to resort to booting into windows to render 4k deliverables.
Sucks.
 
Yup I've been seeing this too in Resolve Lite (latest version), nMPro D700 Yosemite, when grading Red footage + OFX Noise reduction (Neat video). I think all we can do right now is hope Apple/Blackmagic come up with a fix soon. Or use Windows ^^
 
Does this still occur if you do not use the GPU for debayer and just let the CPU do it? Possibly the GPUs are being too taxed with the debayer and the node trees you have built.
 
Definitely OFX NR (neat in my case) "GPU full" error, and if u have "smart render" cache going, corrupt cache will hold those acid trips.
Only way to push the blitzed frames out of the buffer (thumbnails are blitzed too) is to switch off the OFX node and the smart render (on that particular clip), then "update thumbnail", then save, quit, re-load resolve, go that clip first, switch everything back on (including "smart render")
 
well how do you create the problem if you want it, that is the real question? I just need yosemite on my rMBP? that shit looks cool as hell bro!
 
Does this still occur if you do not use the GPU for debayer and just let the CPU do it? Possibly the GPUs are being too taxed with the debayer and the node trees you have built.
Yes I tried turning GPU debayer off in Resolve, and also switched the NR in the Neat Video plugin to CPU only, and I'm still having the same issues...

I think if it was a GPU issue, we should be seeing these issues when transcoding in RCX (with GPU debayer) too, but I've never had the slightest issue when transcoding footage in RCX...
 
I don't know how to resolve the glitch, but that image is awesome!

I thought the same thing, but didn't want to detract from the discussion at hand. Finally, an appropriate use for this emoticon... :emote_rainshower:
 
I don't know how to resolve the glitch, but that image is awesome!
You could sorta/kinda get there with YSFX and keys, but it'd take some time. Random, unpredictable acid effects are generally cooler than prearranged, "designed" acid effects.
 
Back
Top