the Stack Scans option does not affect colors at all. However, the colors in a trace with the Stack option on are completely identical to the ones in a trace with the Stack option off – ie. … Well, the colors aren’t the exact same as in the raster version, if that’s what you mean (though I wouldn’t say they are quite as different as your picture shows… only a little dimmer than the original, which is a typical side effect of quantization). Selecting the node tool to reveal and manipulate the nodes and all the best but remember to keep it simple.Ungrouping or breaking apart objects and shapes and moving them around.Hovering over the options and reading the tooltips.I haven’t used the trace tools in eons but these observations can be easily made by: Those shapes don’t have to be object-based. As there are less nodes and paths, the overlapping of shape boundaries occur. Each scan is like another layer to the painting (“stacking” as Inkscape calls it watch an episode of Bob Ross’ The Joy of Painting ). In contrast, when “Stack scans” is on, the algorithm takes the approach of a painter. Unfortunately, path edges don’t line up perfectly (hence introducing transparency) but the colors tend to be more accurate due to the segmentation. The reason that there is transparency when “Stack scans” is off is that the algorithm’s focus is to preserve shapes (“tiling” as Inkscape calls it think of a tiled floor or stained-glass window). I don’t think it is a bug per se but how the paths and nodes are drawn. I never noticed any color difference with or without stack scans – that sounds like a bug. Did you check the opacity of the paths generated with Stack Scans on? I never noticed any color difference with or without stack scans – that sounds like a bug.If this parameter is greater than 4/3, then all corners are suppressed and the output is completely smooth.” If this parameter is 0, then no smoothing will be performed and the output is a polygon. The man page says “The smaller this value, the more sharp corners will be produced. Judging from your complaints, you might be happier with a lower threshold (eg. You can think of this as how willing the trace will be to abstract away details of your shapes. The main parameter to adjust is the ‘Smooth corners’ threshold.Never found this good to use, personally, it rounds corners off too much. ‘Smooth’ checkbox = gaussian blurring.Your ‘stack both versions’ solution is even more scary in these terms Lots of traces = slow (both to trace and to render) and big filesize.You can do an end-run around this by indexizing it in advance (eg in GIMP) to N colors, and verifying the colors are satisfactory. The ‘Colors’ and ‘Grays’ choices both indexize the image to N colors.Autotrace is pretty much uniformly worse quality than PoTrace (the algorithm built into inkscape).Always creates transparency and there is no easy good looking fix. Don’t bother turning off stack scans, generally. I’ve investigated this subject quite a lot personally.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |