Ahhh The Magic Mask....

[Alien On Vacation]

I guess I need more spell points. And a faster graphics card.
I tried making a magic mask 20 times. Got it to work fine, love the feature! Takes an hour for a 2 minute clip but I can wait...
Added an alpha channel node so I could remove the background. Works great.
But when I jog through the video on the timeline or color page, I get random single frames showing as offline. When I seek them out frame by frame they are fine. They vanish, or go somewhere else in the clip.
If I remove the other track I am using as a new background, the clip works fine. No random offline frames.
The real issue is when I go to render the video together. When it encounters a "offline" frame, it stops rendering and says there is no codec. When you check manually the frame is fine and visible. Getting very frustrating. Tried numerous framerates, mov, mp4, apple pro rez... changed everything. It will render fine without the background I needed.

Anyone have any ideas? I've erased the cache files, re-rendered the original video before making a new mask...

 

[DR]

I'm not yet well versed enough in DR to answer your question, but here's what ChatGPT has to say about your post:




Alright, let’s slow this down and untangle what’s actually happening here, because this isn’t magic mask “being buggy” in the usual sense and it’s not a codec issue either, despite what the error message says.

I’ll break this into what’s really going on, why it only happens with the background track, and what to suggest as fixes in a forum reply.

---

What’s really happening (plain English)​

Those “random offline frames” are not actually missing frames.

They’re GPU processing failures during playback and render, caused by VRAM exhaustion or GPU instability once Magic Mask + alpha + background compositing are all in play.

That’s why:

• Scrubbing frame by frame looks fine
• The frames “move around” or disappear
• Removing the background track instantly fixes it
• Rendering stops at those frames with a nonsense “no codec” error

Resolve throws misleading errors when the GPU fails mid-frame. It often blames codecs when the real failure is upstream.

---

Why Magic Mask + alpha + background triggers it​

Magic Mask is:

• One of the most GPU-heavy features in DaVinci Resolve
• Even heavier when:
  
  • It’s tracked
  • Turned into an alpha channel
  • Then composited over another clip

When you add the background:

• Resolve must process both clips
• Apply the mask
• Calculate transparency
• Composite
• Cache or render all of that in real time

If the GPU runs out of VRAM for even a single frame, Resolve flags that frame as “offline” internally. Playback might survive. Rendering usually won’t.

That’s why:

• Timeline playback can look mostly fine
• Render dies at the exact same “phantom” frames every time

---

Why changing codecs and frame rates didn’t help​

Because the codec isn’t the problem.

You can switch between:

• ProRes
• MP4
• MOV
• Different frame rates

…and nothing changes, because the failure happens before encoding ever starts.

That “no codec” message is basically Resolve saying:

“I couldn’t get a valid frame from the GPU, so I can’t encode it.”

---

What actually fixes it (practical solutions)​

Here are real fixes you can suggest in the forum.

1. Render the Magic Mask clip​

This is the big one.

Steps:

• Disable the background track
• Render the masked clip with alpha (ProRes 4444 or DNxHR 444)
• Re-import that rendered clip
• Use it over the background instead of the live Magic Mask

This turns a live GPU effect into a static, precomputed clip.

2. Force Resolve to use cached frames​

• Right-click the Magic Mask clip
• Enable Render Cache Color Output
• Set render cache to User
• Let it fully cache before rendering

This sometimes works, sometimes not, depending on GPU headroom.

3. Reduce GPU memory pressure​

Suggest trying:

• Lower timeline resolution (even temporarily)
• Disable unused nodes
• Avoid additional effects on the masked clip
• Close other GPU-heavy apps

4. If on Windows: check GPU driver stability​

Without blaming the user:

• Studio drivers are usually more stable than Game Ready
• Outdated or unstable drivers can exaggerate this issue

---

What I’d say in a calm, helpful forum reply​

You can post something along these lines (feel free to tweak tone):

This usually isn’t an actual offline frame or codec issue. What’s happening is the GPU failing on individual frames once Magic Mask + alpha + background compositing all hit at once. Resolve then flags those frames as offline internally and the render stops.

That’s why scrubbing frame by frame looks fine, but rendering fails in the same spots every time.

The most reliable fix is to render the Magic Mask clip by itself first (with alpha), then re-import that render and use it over the background instead of keeping the mask live. That takes a huge load off the GPU.

Render Cache Color Output can sometimes help too, but pre-rendering the masked clip is the safest route, especially on longer clips.

---

Bottom line​

• This is normal behavior under GPU pressure
• Magic Mask is not broken
• Resolve’s error message is misleading
• Pre-rendering masked clips is standard practice, even on powerful systems

If you want, I can also:

• Rewrite this as a sticky help post for your DR forum
• Add a “Magic Mask gotchas” FAQ entry
• Or tailor the reply depending on whether the user is on Studio vs Free, Windows vs macOS, or what GPU they’re using