Hi!
jtaber wrote:
Bob Jamison wrote:
The fix is in the patch tracker, and here is the corrected example: http://inkscape.org/win32/siox/howto.svg
Oh this is pretty awesome. Not sure if you've written up anything for the tutorials on this but here are some questions that could go into it.
- how does the svg file size compare ?
I would say that since you will be tracing a smaller sample of the image, the svg size should be smaller. However, as I've always said, tracing has never been intended to create a finished product. Its purpose is to generate curves for the user to further manipulate.
- does it change much if potracing from png, gif, jpg ?
Not at all. It starts with the same pixbuf in memory that normal tracing uses, then feeds a resulting pixbuf to the other filters for processing.
- relative time to convert ?
It has been adding about 5 to 15 seconds to trace times. Yes, it's slow, but it's a very CPU-intensive operation. Hey, this is high-tech image recognition stuff here. :-) But yes, we will definitely work on reducing the times, same as we (especially Mr. Selinger, to whom we owe so much for Potrace in the first place) reduced that of normal tracing.
- once you have the svg image (ie the horse) is there a way to better
blend the color groups (it's a little "blocky") - maybe like specifying the line as thicker and a gradient color ?
Just try tweaking the other filter settings to get what you want. Notice that the example used only 8 colors. But again, I state the #1 item. The trace is not intended to be a final product. Besides, trying to create a photo-perfect image trace would be a silly waste of time. Tracing is supposed to be an exercise in information reduction.
This was only completed at the last minute here, so use it, try to break it, etc. I hope that people find it useful.
bob