The only pixels that have data are within the workspace.
The image has a huge square around it (though empty) and the software is viewing that as burnable area (it’s not)
It continues throwing these errors, and is asking that I keep shrinking and shrinking the image down.
I cannot get it to burn and have no way to remove the rectangular extends.
This seems like a HUGE bug to me…
I have mentioned this topic before only for them to be ignored and finally auto-closed.
People respond suggesting to “remove the overlap outside the work area”…there IS NO overlap..that area is EMPTY.
It is a software issue that is causing me no end of nightmare for a product I have at this point paid hundreds of dollars for.
Please state you have no plans to address the bug if that’s what is going on.
Without an attached LBRN2 file, it’s a guessing game.
First step would be to explode/ungroup the existing image. You should see bounding boxes in “blank” zones and be able to delete them, reducing the overall project footprint.
If you have separate layers, you can select any given layer with shift-click on the layer number in the cuts palette and find other locations of concern.
They perform a data check for any pixels or not…which lightburn seems to not care about doing.
All they need to do is check to see if there is DATA to be burnt (or not) outside the workspace…if there isn’t, it should just burn everything inside the workspace. The frame is completely arbitrary and pointless. It contains no data outside the rectangular extends of the image…which may, or may not, contain data to be burnt.
It seems the mask tool would work, but it also just creates a large rectangle outside the dang thing. The rubberband tool works better even..but sadly, will not remove the rectangular extents. I would be able to apply a crop in this instance, reducing the rectangular footprint of the image and truncating the “spill over” outside the workspace…however, it is a hack, and does not always work. It only will work in this case due to the image being perfectly horizontal…this is not always the case. Sometimes the image is rotated 45 degrees or whathave you, and a tiny edge of the frame goes outside the “workspace".”
Only way I can think of around this issue would be to FAKE the workspace and use a locked rectangular shape to force myself to remember where the true bed workarea is…this again, is a very bad hack.
The issue is that transparent data on an image is being treated as data. That is the problem.
The rectangular extents of an image should have absolutely ZERO impact on what is able to be burnt on the workspace. Everything outside that range should be ignored.
Please open my files and see what I mean. I understand that it appears as white due to the fact the web browser defaults to a white background and even if this chat thing was capable of displaying transparent images, which I am unsure if it can, it would display the exact same regardless
“You are correct. Lightburn is using the entire size of the graphic. Make a new, smaller rectangle around the image and use it to crop.”
Appreciate your reply.
I get that, however that is not always possible due to some projects needing the entire workspace to be burnt with an image, and some of the images extents (data or no) being otuside the work area…this really is a bigger problem I believe than people are dismissing it as. I had addressed this “solution” in my 3rd or so reply. This will only work for this instance because of the perfect 0/90° angle of the image being perfectly in the center of my bed…it normally isn’t like this.
