I was doing a simple 5 box gradient patch. Drew it in Inkscape, then exported as PNG, attached.
It configured it with two copies of the attached file (and have not tried scaling it down to many fewer pixels), one at a medium speed and one at a very low speed. The low speed one seems to push it over the edge into failure. Will test again in a moment.
The GF front end fails to prepare this file. Times out.
The attached file seems to have two SVGs. Without seeing the PNG, my guess is that you rasterized and exported at a very large size/DPI. What’s the file size and the pixel dimensions for your PNG?
I don’t think so. Processing a single copy of the PNG file at about 5" wide took ~9 minutes at a speed of 500. At a speed of 100, that should “only” take 45 minutes, right?
Those error messages are not from the original vector file. They are from the raster file. You have at least 13 squares piled on top of each other ( at least thats what I counted).
By strictly math: Assuming a ~3 hour buffer and the physical size of the print being 5.4"w x ~1"h, you’d have to set the LPI down to ~133lpi in order to get the print to run at 100 speed.
I don’t get it. Never had an “old unit” UI so I have no idea what the old unit to new unit conversion means.
What are the units of the “speed” parameter, then? Arbitrary? And seemingly non-linear?
I.e. if I have an engrave that is, say, 100mm long by 10 rows (i.e. 1m total, minus corners) then what would be the time to traverse at the different speeds?
You just have to calculate it backwards… spreadsheet only calcs one way as it is. “Old units” were Inches per Minute. Plug in an inches per minute value (old unit) and you’ll see what the corresponding “new arbitrary value” is.
In the strict mathematical sense it is linear function of speed but it has an arbitrary offset as well as a scale. To convert back to inches per minute use these formulae.
I’m not saying this is the case here, but the PNG file format does allow layers and they can end up stacked. Adobe Fireworks was my go-to editor for years and uses layered PNGs as it’s default file type to this day.
But nothing else (that I know of) will really modify those layered PNGs. It was basically Fireworks injecting some code into the PNG file, that it could then read back and interpret as layers.