Working on a cat to eat the goat. No, cats don’t eat goats, but that’s what it says in the song.
Category: work-in-progress
One Little Goat
R-G-B, C-M-Y, H-O-R-S-E
All The Pretty Horses
I ran an inversion on yesterday’s horse Traveling Salesman Problem animation:
Again I had to take out a few stray lines manually. Here’s the same white on black:
Yesterday’s negative image and today’s positive image together:
The positive image has only 2,000 points, so it was faster to process. It’s still denser than the negative image (background) which has just under 4,000 points but covers a lot more area.
Here are both with contrast on grey:
and in yellow and blue on magenta:
Embroidermation Test 2
Sequel to Embroidermation Test 1.
Theo Gray and I bought a 10-needle embroidery machine to pursue a dream of embroidered animation. Existing embroidery software sucks too badly to do the automated shape-to-stitch conversions necessary, so Theo found a way to use Mathematica instead. This is his first full test, created in Mathematica, exported directly via an Embroidermodder file conversion program as DST files, stitched on canvas (which made the edges kind of jaggy) and photographed. No loose threads were clipped in the making of this video.
Embroidermation: test 1
You may have heard I’m working on this movie, and I am, but my contract prohibits me from blogging about work-in-progress. All the more reason to blog about my super-exciting other project that no one is paying me for and is motivated purely by madness and my crazy Muse: I want to make an animated quilt. Or rather quilted animation. Or embroidered animation, because the most common quilt plotters are actually embroidery machines.
I’ve already ranted about the shameful state of embroidery machine software. Having just bought a fancy new Brother machine that came with Brother’s “top-of-the-line” software, PE Design NEXT, I can now say the situation is worse than I thought. Not only is the software crazy expensive, it’s also woefully inadequate for automated line drawing conversion. More on that in a future post; for now I want to describe the steps required to make a single frame (scroll down to see it).
I began with an animated cycle I made almost two years ago: the Ziz. Automated digitization of one frame of that design, in color, for embroidery, is well beyond what PE Design NEXT can handle, so I started by just asking it to do the outline, monochrome, in a simple running stitch. That was also way more than it could handle, so I went back into Flash and simplified the design:
Then I imported a frame into Adobe Illustrator and “merged” everything to eliminate background shapes.
I gave it no fills, only a 1pt stroke. PEDNEXT read it as several hundred separate shapes, with thread cuts between each; it wanted to start and stop every few stitches to cut threads, even with all the outlines abutting each other.
Clearly we had to convert the design into one continuous line, which PEDNEXT can’t do (it can sort of do it with bitmaps it traces itself, but it’s terrible at auto-tracing. One should be able to trace in a better program and get it to work with those vectors, but it’s biased against vectors for some reason). It’s an old math problem called the Chinese Postman, a variation on the more famous Traveling Salesman. The Traveling Salesman visits every vertex in the most efficient path; the Chinese Postman travels every path.
Fortunately my Significant Other and co-lunatic in automated embroidery machine experiments, Theo Gray, was a founding developer of Mathematica software. Just one morning of his fiddling with the files yielded exceptional results.
Then PEDNEXT refused to read the resulting single-line file, even after it was converted to .wmf (windows metafile – the ONLY vector file PEDNEXT accepts. It doesn’t accept .svg, .eps, .dxf, .ai, or any other vector file. Just .wmf. Which is what you’d expect from $2,000 embroidery software, right?) Thinking the line was too long, we broke it into smaller segments and imported them as separate files. Through a tedious process of elimination we discovered there was just one teeny segment PEDNEXT refused to read. We pinpointed it to two points (perfectly normal points! the files are fine, we have no idea why PEDNEXT doesn’t like them), deleted them from the master line, imported to Illustrator, exported to .wmf, imported to PEDNEXT, saved as .pes (Brother’s proprietary format) on a flash drive, and got it into the machine. And finally:
This represents a huge step towards my dream of embroidermation. It took us a long time and much obsession to get to this single frame. Further tests with PEDNEXT will determine whether the whole 24-frame sequence can be automated, or if there are bugs in every new frame import. Meanwhile I’m even more committed to supporting EmbroiderModder2, a young FLOSS alternative to existing inadequate overpriced embroidery software (crowdfunding campaign coming soon!). I hope Brother supports it too – their machines are great, with better software who knows what people could do with them.
Update: see the Mathematica code and an animated gif of the stitching here!