Here is some Example:
apparently dxf does not support curves. That’s fine i guess, but why does svg and ai alter the path?
svg also breakes one of the paths completely and turns it into a giant loop after exporting.
ai doesn’t do that at least:
Imma adding the files, so you can verify:
Lightburn project: clock_bug.lbrn2
SVG export: clock_export
These are all different file type associated to, generally an application.
DXF, SVG, AI and other formats have a wide latitude on what is ‘standard’ what they store and how it’s stored.
When you change file types, like everything else, there are tradeoffs in what is kept and what isn’t. If it’s a closed ‘line’ a short vector or even a curve…
The only real why to keep all the parts properly is to use the ‘native’ file type of the application. Once you leave that, you start giving up other things. Generally it’s better than creating the whole thing over again.
There may be adjustments on the export facility or how you import it into Lightburn that can cause things to behave differently.
This is one of the drawbacks of designs in on other platforms.
Good luck
I am fully aware that changing the file type is not always lossless and also differs from type to type or version of the program used. So we could be surprised at any time if Adobe changes the AI structure and breaks things.
But we’re talking about an svg file here, which is specifically designed to store this kind of information in a lossless way, and is pretty well standardized as well as non-proprietary and pretty much THE file type for paths. Also, I export from Lightburn and import back into Lightburn, and any change to the paths should be considered a bug, since you shouldn’t have a different “standard” for export than you do for import.
I opened the resulting svg in Inkscape. The small loop seen in the first image is also missing in Inkscape, which could be an indication that it will be omitted during export.
The large loop (2nd image) did not show up in inkscape and looked fine there. I then saved the file from inkscape and opened it again in lightburn to see if inkscape “fixed” the path, but the large loop is still there, which could be an indication that the import is behaving incorrectly.
The large loop also seems to start exactly where the small loop was omitted, so both issues might relate with each other.
I hope someone can confirm this behavior on another machine and a developer can take a look, as problems with importing could cause annoyance, especially with files/orders from clients.
That’s always possible. It’s possible that Lightburn people haven’t tackled some part of importing svg files.
If you search on svg then you’ll find lots of discussions on this forum. Maybe it will help you locate either an issue or a work around until then.
I’ve had few problems with svg files, but most are not very complex.
Maybe @LightBurn could make a suggestion or see what is going on and help out.
Good luck
All of the above do still happen in 1.2.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
