I’m getting issues with Luban apparently “missing” (for want of a better term) parts of images.
Attached is an image of a set of logos I am trying to engrave. This is an image produced fromCorelDraw and exported in SVG format. When I run it through Luban as a vector engraving and look at the output the mountain logo is missing: only the text is there.
Much more oddly as a matching problem is when do the same thing with a JPG exported from CorelDraw, the image again looks proper in the editor but when I preview it in Luban the mountain logo is there but the text is missing!!!
I think I begin to see something… I hadn’t noticed it with the ‘vector’ option, but same as B/W there is a threshold that can be adjusted. When I push the threshold up very high the image comes back into view - but it’s like an overblown photo, it’s very ugly. No good.
I don’t understand graphics well enough: I thought a SVG drawing was basically a bunch of curves so there wouldn’t be a ‘threshold’ to be concerned about. But I must be misunderstandign something and there clearly is something there. The image was intially a jpeg that I transformed into an svg to get rid of the color, then added text using CorelDraw. Outputting the subsequent SVG, there are some important “levels” that are different I guess.
I suppose it simply means that I will have to learn more.
Nit all SVGs are created equal. Some programs output “Their” SVG format, which differs slightly to others. I would suggest loading the SVG into Inkscape and saving as a Plain SVG.
Adding to that, I had success in Inkscape by selecting problematic objects and choose the option “Convert to Path”. SVGs after that worked without problems in Luban.
I tried the ‘object’ → ‘object to path’ - option in Inkscape and saved the image to a new name… However I can’t see that there is any difference when used in Luban. I can make the image appear completely but it requires turning up the Threshold to a really high value and the image looks poor. Mind you I have not tried printing that: perhaps it is better in real than in the image in the program.
In my experience, if you can’t see it in Luban, it probably won’t happen in the process. While Luban’s visualization is not always what you see is what you get, I have found that it does need to be somewhat visible.
