Magic Masks won't output at render

On previous versions of Resolve, when I went to the Deliver page and rendered a media file, I could see the viewer that showed my magic masks being rendered for output. Now that I'm on version 19, when I go to the Deliver Page and render a file, all magic masks become undone.


I'm trying to render an 86 minute movie, at Ultra HD MP4. That works fine. When I play the finished MP4, each shot with magic mask will display one rendered frame (the one I drew lines on), while the rest of the frames on each shot is just the dark layer. I have two layers, one light and one dark.


I have about 200 of these kind of color corrected shots, where the mask brightens up the subject, or darkens the background:

TomDark.jpg (87.03 KiB) Viewed 1471 times

TomLight.jpg (85.22 KiB) Viewed 1471 times

After a render attempt, all my magic masks on my timeline become undone (except the one marked frame in each shot) and have to be regenerated. I did find the one step regenerate command for all clips, but even that takes hours to restore.

If I attempt to output render my timeline again, they disappear, again. I tried rendering smaller files (just a couple of scenes), but the masks still would not render.

Maybe I'm missing something in settings, so any words of wisdom would be appreciated. I'm using Windows 10. As I said, version 18 was working. Here are my output settings:

RenderSettings.jpg (74.14 KiB) Viewed 1471 times

You can't output Magic Mask at render unless you create alpha output connection, connect to it and render at appropriate codec the mask itself.

So probably what you mean is rendering the adjustment, like exposure changes, limited by magic mask you have created.

What you describe in your post seems to be related to caching. You have essentially lost cache in one way or the other and that is why Magic Mask selection and tracking needs to be re-rendered to re-created the cache.

I don't know at which point cache was deleted or why, but there are several things you can do. Assuming the cache is lost, you can re-render the magic mask strokes which takes time and is no fun, but as long as the reference strokes of the magic mask are not deleted, they should be recreated and cache build up again. People have been having issues with magic masks and caching for a while now, either because they used wrong workflow and didn't know how to manage it or sometimes related to bugs etc.

In the future the safest way to save cache is to output masks or mats themselves as rendered masks. That way you have them rendered and as long as you don't delete them manually they can be reused on the same project, preventing any accidental deletion of cache or problems with bugs.

I use this format typically to render the masks from deliver page. Or if I use fusion for magic mask I do it via saver node.

sshot-474.jpg (29.24 KiB) Viewed 1135 times

I wonder what is invalidating the masks, though, in the OP's case? To the OP - can you provide a DRP of the project where this is happening? Upload it to a file sharing site and provide a link here. Someone may be able to see a flaw in the way you are using the magic mask (either a helpful forum member of someone from BMD).

Thanks for your response. I have alpha outputs inserted. I'm using the color page, btw. I'm also using many other masks, with traditional tracking. No problem with those.

What you describe in your post seems to be related to caching. You have essentially lost cache in one way or the other and that is why Magic Mask selection and tracking needs to be re-rendered to re-created the cache.

I don't know at which point cache was deleted or why, but there are several things you can do. Assuming the cache is lost, you can re-render the magic mask strokes which takes time and is no fun, but as long as the reference strokes of the magic mask are not deleted, they should be recreated and cache build up again. People have been having issues with magic masks and caching for a while now, either because they used wrong workflow and didn't know how to manage it or sometimes related to bugs etc.

I've been editing this project off and on for a couple of years. It has screened in different theaters, in early and late 2022, and has had multiple screener versions. So, it has been rendered out successfully, multiple times. Each time, I update it and render it out as a 4K MP4, then I render a 2K DCP from that. The masks used to render out. Something happened with OS 19. I'm agreeing with you that it is cache related.

When I get home, tonight, I'll check it out some more. Thanks!

I could swear I've seen something similar when testing 19.0.1 but I didn't look too closely - I was doing something a bit non-standard with the way I was linking the magic mask node to other nodes - I can't recall the details but I will definitely keep an eye on this as I continue using Resolve. Cheers.

I too had many issues with MM (and other tools) and caching (since DR 18 or so). After many tests, workarounds and reading forum posts I gave up finding the cause of the issue. My conclusion was: At some point Resolve looses the cached data and does not notice it.
My solutions:
1) stop using MM and go back to traditional ways of doing it (has other benefits too).
2) render in place

Update: I've made several renders with success,.....after a lot of failures. The short of it is when I changed my render settings to KrunoSmithy's codec suggestion, I think it was EXR. I did a short render, and I think it jogged Resolve.

I did not like that codec, so I changed it back to MP4 (like I was using), and it worked, even without Render Cache and Alpha settings. I did a few short renders with success. Of course, for the 4K, 86 minute version, I went to MP4 Advanced settings and selected Render Cache.

You can't output Magic Mask at render unless you create alpha output connection, connect to it and render at appropriate codec the mask itself.

Yes, and no. I've output Magic Mask at render both ways. But you really did help me...

I use this format typically to render the masks from deliver page. Or if I use fusion for magic mask I do it via saver node.

The attachment sshot-474.jpg is no longer available

I give you full credit for steering me in the right direction. Thanks, again!

So, I honestly believe something is afoot with Resolve. I change timeline resolution and the masks disappear. I render and the masks disappear. It takes me about 3 hours to regenerate them. I wouldn't know where I would be without this wonderful feature:

RegenerateMask.jpg (94.13 KiB) Viewed 169 times

render in place

Also, a very good suggestion! I will be doing so, moving forward. Thanks!

Also, a very good suggestion! I will be doing so, moving forward. Thanks!

Cool.

Few more notes: Keep in mind that magic mask renders what it gets from edit page. So its ok to do things downstream from magic mask node, but not upstream. If you change something about its source, like transform functions in the edit page, or timeline resolution etc, you are changing input data for magic mask, so it has to re-render. If you want change something in the color page or edit page, it has to happen downstream from magic mask node.

For example if you want to change size of the mask, you can add transform node after the magic mask and change it, no problem. You can even drop a transform effect on edit page, go to effects tab and change size there. But just keep in mind that downstream is ok, upstream is not. As you work with a bit of foresight and planing it should not be a problem.

I encountered an issue where magic masks don't work if you save an existing project as a new project. The project thinks the masks are cached but can't find them, it also won't let you Regenerate them. In this case the solution was "Delete Object Mask > All Clips" and then "Regenerate Object Mask > All Clips".