{"id":455,"date":"2008-05-05T11:10:59","date_gmt":"2008-05-05T10:10:59","guid":{"rendered":"http:\/\/ospublish.constantvzw.org\/?p=455"},"modified":"2009-01-21T11:25:39","modified_gmt":"2009-01-21T10:25:39","slug":"potrace-alphamax-1334-or-the-limit-between-artificial-and-natural","status":"publish","type":"post","link":"http:\/\/ospublish.constantvzw.org\/blog\/tools\/potrace-alphamax-1334-or-the-limit-between-artificial-and-natural","title":{"rendered":"Potrace –alphamax 1.334 (or the limit between artificial and natural)"},"content":{"rendered":"

Since the first time I’ve used an autotrace program -Adobe Streamline 1.0 in the early nineties- I’ve been disappointed by the unavoidable angles in curves, named kinks or cusps, that pledged the vector output. Lots of designers and developers seem not to care about it, but for me it is simply the difference between artificial shapes that scream “I’m a vector!<\/em>” and natural shapes where every sharp edge is a small curve when you look really close. That kind of ultra detail may seem useless and\/or nerdy, but it can really make the difference in typography. Like in my work where I use bitmaps as sources.<\/p>\n

\"Perfectly<\/a>So for 17 years+, I’ve tried all options and all autotrace softwares I’ve found for that simple but invisible holy grail function : a real smooth aligned anchor for all curves. No way. The only cheat strategy I’ve found was to produce polygons with no curves at all, then to round all them… Sometimes ok, but really not satisfactory.<\/p>\n

A few weeks ago, during my first real hands on Inkscape, I’ve made some tests on the Potrace function. That FLOSS package will be more open to custom settings? I founded the “smooth corners” setting, like in so much other packages. After a few tests, with the maximum and strange value of 1.34, it’s reveal to produce those precious precisely aligned anchors! Ma-gni-fi-que.<\/p>\n

And today, having a bunch of tif pictures to autotrace for a “regular” “proprietary” job, I decided to try potrace more extensively and to try to process them in batch. So I read the potrace documentation, and in a flow of features I read with *real* emotion :
\n“-a n, --alphamax n<\/code>
\nset the corner threshold parameter. The default value is 1. The smaller this value, the more sharp corners will be produced. If this parameter is negative, then no smoothing will be performed and the output is a polygon. The largest useful value is 4\/3 or 1.334, which suppresses all corners and leads to completely smooth output.<\/strong>“<\/em> (from http:\/\/potrace.sourceforge.net\/potrace.1.html<\/a>)<\/p>\n

\"Magic<\/a><\/p>\n

So the cryptic Alphamax setting, with a 4\/3 value define precisely the limit between artificial and natural in the autotrace and vector world!…<\/p>\n

And I immediately use it :<\/p>\n

    \n
  1. \nrename to avoid spaces :
    \nfor file in *; do mv \"$file\" `echo $file | sed -e 's\/ *\/_\/g' -e 's\/_-_\/-\/g'`; done<\/code><\/em><\/li>\n
  2. \nconvert tif files (not supported by potrace) to pbm files and insert “pbm-” at the beginning of the filename :
    \nfor pic in `ls *.tif` ; do echo \"converting $pic\"; convert $pic pbm-$pic.pbm; done<\/code><\/em>
    \n(it take some time : pbm files, as other portable anymap files not compressed, are ~30 x more heavy than tif)<\/li>\n
  3. \ntrace the pbm and produce eps files with “eps-” at the beginning of the filename :
    \nfor pic in `ls *.pbm`; do echo \"potrace $pic\"; potrace --alphamax 1.334 --turdsize 2 --longcurve --turnpolicy black -o eps-$pic.eps $pic; done<\/code><\/em><\/li>\n<\/ol>\n

    Even if it has me place three hours closer of my job’s deadline, in this rude white night in pure designer style, I continue to smile.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Since the first time I’ve used an autotrace program -Adobe Streamline 1.0 in the early nineties- I’ve been disappointed by the unavoidable angles in curves, named kinks or cusps, that pledged the vector output. Lots of designers and developers seem not to care about it, but for me it is simply the difference between artificial […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[38],"tags":[52,6],"_links":{"self":[{"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/posts\/455"}],"collection":[{"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/comments?post=455"}],"version-history":[{"count":3,"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/posts\/455\/revisions"}],"predecessor-version":[{"id":1670,"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/posts\/455\/revisions\/1670"}],"wp:attachment":[{"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/media?parent=455"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/categories?post=455"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/ospublish.constantvzw.org\/blog\/wp-json\/wp\/v2\/tags?post=455"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}