Luckily, I have the 3D models of the objects and, in Flitter, a bespoke rendering pipeline that already includes all of the machinery necessary to do this. So I can synthesise tens of thousands of labelled images in minutes.

When I created Flitter I wanted it to be a very domain specific language. What is surprising me is that I am discovering that there are more things in this domain than I originally thought. 3/3

#FlitterLang

Oh yeah, and a few filters thrown in: a feedback mixer, lens flare and bloom on the bodies layer, and then a filmic tone map on the composited output.

This process of layering shit up is largely how I designed Flitter to work. It is, I guess, the answer to the question "What if TouchDesigner was a functional language?"

#FlitterLang #CreativeCoding

The end result here is bodies spinning in one layer and the head spinning in another, with the first layer texture-mapped onto the head. The two layers are then multiply-composited together. A couple of different directional coloured lights completes the effect.

All of the various parameters that control the animated elements are driven by beat-aligned pseudo-random streams, randomly glitching the rotations, the camera, the direction and colour of the lights, etc.

#FlitterLang #CreativeCoding

Actually, I want to follow this up as I see amazing visuals on here all the time and my first thought is always, "Fuck! That's incredible, how did they do that?". Usually immediately followed by, "God I wish I was that creative."

This is 40 lines of code (plus an external OBJ model and a stripes texture image). The process I followed was largely one of fucking-around-and-finding-out, beginning with the spinning body and then just layering shit on top.

#FlitterLang #CreativeCoding

Further experiments: more, smaller snowflakes and many more, more colourful spotlights

#FlitterLang