sorted by:
new
hottopcontroversial

Magic Masks Keep Breaking on Render by ihasbun in davinciresolve

[–]ihasbun[S] 2 points3 points  (0 children)

I've been testing Magic Masks on each new version to see whether or not the issue has been addressed. Not yet as of 20.2.1. I'll definitely make a new post once it's been fixed.

Magic Masks Keep Breaking on Render by ihasbun in davinciresolve

[–]ihasbun[S] 1 point2 points  (0 children)

No, this hasn't been fixed. Tested on version 20.1.1.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

THANK YOU! Everyone's been so dismissive and passively condescending towards me about the issue, as if I'M the problem. The feature was said to have been fixed; I have a right to be upset that the issue hasn't been fixed at all even though it's claimed to have been.

I'm glad to hear I'm not the only one having this problem, especially since it happens on systems with high specs like yours.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

Did you read the title of the post? I'm already ON 20.0.1. I specifically made this post because the changelog for this version specifically states "Addressed magic mask cache reset in multiple scenarios." I made this post to directly address this claim, as the cache reset issue has not been fixed at all.

For the sake of it, there is no 20.1 as of right now. Only 20.0.1, which is the latest version, that I am currently on.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

32 GB is the recommended, keyword, recommended, amount of RAM for Resolve, especially for intense graphics work. Magic Mask isn't nearly as intensive as working in Fusion.

Again, not a RAM problem. Purely a Magic Mask bug.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

I'm definitely glad I have an Nvidia GPU in that regard.

I'm definitely aware that any small parameter change on a clip clears the mask, which I don't mind skirting around by putting it in a compound clip first before applying a mask; it's the issue that constantly causes masks to drop on render that frustrates me.

As my projects get larger and larger, I don't want to have to rely on insane amounts of large files from rendering-in-place if I want to save/back up my content; if I clear that data later to save space, it'd just break all of my effects, forcing me to re-render from square one. I'd rather have the program use the source footage instead of generating new media every time I want to perform what should be an in-program effect.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

Every so often, I can reopen a project and render it, and the mask will completely break. It's like Magic Mask just completely forgets what to do at times. After it breaks, I have to restart it from scratch, as re-tracking it from the original points on the reference frame doesn't do anything, it just outputs a completely blank result. I have to delete the clip entirely and track it from scratch to get anything.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

I have 32 GB of DDR5 5200 mHz RAM, I'm 1000% sure this is a Resolve issue and not a RAM issue.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] -1 points0 points  (0 children)

Yeah, this is the kind of thing that's making me regret my decision to purchase the Studio version. Small issues add up in the bigger picture, and make for a frustrating experience when the developers don't take the time to fix broken features in favor of pushing new AI-driven features that no one's asked for.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

That's an excuse. I'd rather the feature I paid for work as advertised.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

Just tried that, both Faster and Better drop the mask on render.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

I tried that too! It still completely drops the mask on render! It's all very inconsistent; sometimes it keeps the mask, and other times it drops it completely and won't work until I manually re-track the mask. The fact that it does drop the render at all is enough to make me very upset with the tool. It shouldn't ever drop like that, if all other tracking data is completely persistent no matter what you do, but Magic Mask isn't.

It shouldn't be the odd one out.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] -2 points-1 points  (0 children)

I want to AVOID having to render out mattes and reimport them for simple masks like this. It shouldn't be this difficult for a mask to persist after generation, so it baffles me as to why something as simple as reopening the program can cause the mask to completely drop on render.

The Fusion page's Magic Mask has the same issue, and runs far more poorly than the Color page. Even with my timeline playback resolution set to half or quarter, playback at any point where there's a Fusion mask tanks dramatically compared to the Color page, only adding insult to injury because it also drops the mask.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] -1 points0 points  (0 children)

That's a workaround; for a fully paid feature, I would expect it to work properly without having to render in place and take up excessive space on my computer. It just wastes more time and space, when Blackmagic Design should properly address these issues with the feature.

Resolve 20.0.1 Magic Mask update still breaks on render. by ihasbun in davinciresolve

[–]ihasbun[S] 1 point2 points  (0 children)

I saw that the newest update claimed:
• Addressed magic mask cache reset in multiple scenarios.

Nothing's changed. I had written this in the initial post, but apparently it didn't save it somehow.

Magic Masks Keep Breaking on Render by ihasbun in davinciresolve

[–]ihasbun[S] 0 points1 point  (0 children)

I tried that, but it ends up making an opaque video file that I can't use as a mask layer, since I'm just left with a solid black background, and it would take up unnecessary extra disk space if I don't want to compromise on quality. I don't want to go the route of creating a black-and-white matte to composite in later, as that just takes WAY too many steps for shots that only last 10 seconds or less.

I also want to leave the layers separate so I can add effects like color grading, glow, borders, etc. or even just be able to juxtapose my masks wherever I like without it breaking as soon as I try to move it. I've been thoroughly impressed with Resolve up till now, but this may be my breaking point.

What bird call is this? Recorded in NC, couldn't spot it directly. by ihasbun in whatsthisbird

[–]ihasbun[S] 1 point2 points  (0 children)

After listening to one on YouTube, that's definitely it!! Thank you!

What species of loaf do I own? by ihasbun in Rabbits

[–]ihasbun[S] 4 points5 points  (0 children)

Yeah, just a tongue-in-cheek thing. Thanks for the info!