Sorry if this has been addressed. The Apply Mask to image does not seam to work in Millmage. It crops out the image, but still carves the “cropped out” areas.
Taking a wild guess here but it might be because you cropped with a square instead of with a circle. Everything inside the crop outline should remain part of the operation, right?
No, If you look close at the 1st image, you will see the red circle close against the coin. This is the same file I used to make this brass coin in lightburn. If I had used a square ro crop the image, you would still see the square in the 1st image. Cuz the gray scale image itself is square. But you can see, I did get the mask to work in the design window. Just not in the carve.
No, If you look close at the 1st image, you will see the red circle close against the coin. This is the same file I used to make this brass coin in lightburn. If I had used a square ro crop the image, you would still see the square in the 1st image. Cuz the gray scale image itself is square. But you can see, I did get the mask to work in the design window. Just not in the carve.I am failing to see the issue. The left part of the second image (Post #1) shows a bounding box around the coin. The right side of the image shows the cut Preview, which makes sense [1] according to the left image, and [2] your having a single operation “3D Relief Finishing” listed.
I seem to be missing something. What were you expecting to happen?
Masking is not intended to apply to engraving. Don’t mask the image, just include the vectors you used for the mask in the operation itself to use them as a boundary.
Masking requires storing a copy of the image with full color and transparency, meaning an 8 or 16 bit depth map becomes a 16 or 64 bit depth map (per pixel), quadrupling the memory requirements.
Since so many people are used to masking from LightBurn, we’re likely going to get this confusion a lot, and will ultimately be required to support it as a workflow as a result, but your processor memory will thank you if you don’t use it. ![]()
Ok, Thank you for the answer. That is a feature I use in other software, and was hoping it worked here too.
It will when I have a chance to finish it, but it’ll always take dramatically more memory to work that way, and will require us to trace the transparency layer every time it runs.
If you just provide a boundary instead, less memory, no tracing.
I mean as long as I can trace it, I would remove Apply Mask from Millmage all together.That way it is less work on you, and less work on all the smaller computers out there doing this work. I am going to do a video now. My channel does not get a lot of views, but if it helps someone, it is worth it.
Thank you for all the work yall have put into it. I am stoked about vcarve and 3D.
There are folks internally who’ll fight me on that, and a number of other packages support it too, so I think I’ll lose that battle eventually. You can absolutely trace the transparency layer in the image trace function.
I just subscibed so keep pumping out those how to videos!


