Maciek S
Active member
So besides getting a 1080ti (I'm waiting to see what the Red+Nvidia performance increase will be with the recent debayering updates) I'm wondering how you guys are working when you hit a "GPU Memory Full" wall.
I have an overclocked 6900k, GTX 1070, SSD scratch drive and Raid I work on currently. My footage is mostly 6k Dragon or 4k Mavic Pro.
I have my Red Camera raw settings in Resolve at "1/4 good" and playback settings at a quarter and all is well. Playback is smooth and all that everything works great.
When I start denoiseing/adding luts and effects to 4k Mavic Footage or Red footage at 4k that is when I run into GPU Memory Full issues. What are my options at that point? Will Resolve still render this or fail?
Is there a way to force computation to the CPU for rendering?
Since 4k/6k red footage has been around for a while, how did people denoise and work with multiple effects before the 1080ti's were available is what I'm curious about.
I'm new to Resolve and learning so forgive me if this is simple answer. I just see people beefing their systems up, but i'm wondering what some options were before.
I have an overclocked 6900k, GTX 1070, SSD scratch drive and Raid I work on currently. My footage is mostly 6k Dragon or 4k Mavic Pro.
I have my Red Camera raw settings in Resolve at "1/4 good" and playback settings at a quarter and all is well. Playback is smooth and all that everything works great.
When I start denoiseing/adding luts and effects to 4k Mavic Footage or Red footage at 4k that is when I run into GPU Memory Full issues. What are my options at that point? Will Resolve still render this or fail?
Is there a way to force computation to the CPU for rendering?
Since 4k/6k red footage has been around for a while, how did people denoise and work with multiple effects before the 1080ti's were available is what I'm curious about.
I'm new to Resolve and learning so forgive me if this is simple answer. I just see people beefing their systems up, but i'm wondering what some options were before.