I wonder which algorithm you're using? From very quick testing, it looks like you're picking characters to represent various grayscale values, but I'm not sure that you're taking the shape of the characters into account like other converters do.
I used a combination of Tab Atkins' and the MooTools ASCII art (https://github.com/khrome/MooAsciiArt.js) algorithms. The four ASCII options came from those two libraries, as well (I played around with the values on various pictures until I found ones that I thought worked the best).
OK, and it seems that those algorithms only take the grayscale into account.
Compare http://paste.fulltxt.net/:gh (your output) with http://paste.fulltxt.net/h-,:wiS (aalib's output). This probably isn't the best choice of image, but you can still see how aalib approximates the edges of the drawing with all sort of characters.
Uploaded my favorite photo of our 12 week old daughter in the hopes that I could stuff it into the repo of some new project. When attempting to adjust the line width, Chrome went "Aw, Snap!"
Would love to see this again when all the kinks are worked out.
Sometimes, as a web developer, you have no consistent way to diagnose these issues. We found an issue using drag and drop uploads on one of our sites where if you uploaded the same image in chrome, one after another, it would crash. So I wouldn't give all the flak to the developer, as it might be chrome.
Nope. I suspect the site is fundamentally broken in my browser[1], given that I see two video elements, and the textbox is overlaid on top of several other elements, and there are some control elements floating seemingly randomly on the page.
Here's a screenshot of what I see: http://imgur.com/cET4F. Might be the nightly build's fault, of course!
I don't consider auto generated ASCII figures (from aalib or libcaca or similar) to be art. To me, art implies there is an artist behind the work of art or the technique used to generate it.
In that case the developer of the converter (library) is the artist. I'm sure there's a lot of creative input involved in auto-converting a raster image into an ASCII figure.
Why the #eee on #fff color scheme? It took me a long time to realize that the white blur in the scroll area was changing, and that if I highlighted it it looked like an image.
27 comments
[ 2.7 ms ] story [ 52.3 ms ] threadAlso, here's a link to the Github repo: https://github.com/zachwill/asciifi
You can also take a look at the Asciify and AsciiCharacter classes in the CoffeeScript file (https://github.com/zachwill/asciifi/blob/master/static/js/ap...).
Compare http://paste.fulltxt.net/:gh (your output) with http://paste.fulltxt.net/h-,:wiS (aalib's output). This probably isn't the best choice of image, but you can still see how aalib approximates the edges of the drawing with all sort of characters.
Wonder if that makes any sense for video, though?
There are two copies of the video: http://dl.dropbox.com/u/1237941/Screen%20Shot%202011-11-28%2...
Would love to see this again when all the kinks are worked out.
Here's a screenshot of what I see: http://imgur.com/cET4F. Might be the nightly build's fault, of course!
1. FF nightly build, 11.0a1 (2011-11-28)
For anyone interested it is called "fetts vette"
Real artists do their ASCII art 7 bits at a time.
http://sixteencolors.net/
http://artscene.textfiles.com/acid/
http://artscene.textfiles.com/ice/
Turn up the contrast so we can see it!