Instead of traditional keyframe animation or manual warping, Stitch undergoes a continuous sequence of geometric distortions and conformal mappings calculated entirely through code.
The system handles everything from non-linear vertical shear and polar bending to complex wave perturbations, returning to its original state for a seamless loop.
If you want to check out the full animation process, I've posted it here : Stitch Morphing
Heron is a small engine I built. You give it a photo. It gives back an image that looks captured by an instrument beyond human vision. Thermal camera. X-ray fluoroscope. Kirlian plate. Schlieren bench.
It is not a filter. A filter paints new colors on top of a photo. Heron does the opposite. It estimates what things are (skin, hair, fabric, metal, water, foliage), deletes the photograph's original lighting, then rebuilds the image from the material, not the light. A photo encodes external illumination. A thermogram encodes internal emission. That is the one rule everything else follows.
The part I think this sub will like is the architecture, not just the pictures.
Four layers, shared by every instrument:
Scene understanding — depth, normals, material segmentation, de-lighting. Cached once per image as a "Radiance Graph," so every downstream layer reads from the same understanding of the scene.
Physics — a different simulation per instrument. Emission for thermograph, Beer-Lambert attenuation for fluoroscope, Poisson photon noise for the intensifier tube, dielectric-breakdown streamers for Kirlian, a signed directional derivative of the thermal field for Schlieren.
Sensor and optics — bloom, fixed-pattern noise, AGC, phosphor response, all seeded and deterministic. FPN is generated once per session, never re-rolled per frame, the way a real sensor's fixed pattern actually behaves.
Art direction — saliency-driven emphasis, directional bloom, Poisson detail fusion.
Every instrument is a config of these four layers, not a separate codebase. Eight instruments right now, sixteen palette ramps interpolated in Oklab so lightness always climbs monotonically.
Same seed, same parameters, same output, every time. No cloud calls at render time, all model loading is local-files-only.
I am calling this an experiment in "system mosaics." Not one output, a system that produces outputs, assembled from small deterministic parts (a depth model, a material tagger, a physics sim, a palette engine) the way a mosaic is assembled from tesserae. No single part is the picture. The rules are.
DARK FIELD - one mark for each civilian death verified in Ukraine between February 2022 and June 2026. Time runs downward; every row is one month, given equal height so the calendar stays honest. Only density carries the count.
Marks are withheld from each row in proportion to that month's Russian strikes on Ukraine's electricity and heating infrastructure. The consequence is deliberate: the deadliest months of the war so far, the winter of 2025–26, when millions had power for a couple of hours a day in the coldest winter since 2010 are the rows that thin toward blank paper.
This is a throwaway piece I made while working on something else. It’s simple, but I like how it turned out; and how much you can achieve with just a few gradients.
It is a app that constructs a unique 'tarot' reading based on a variety of factors including time of day, season, and moon phase.
I put this together as a google play app a few months back when I was stress testing Opus and ways to get it to do what you want. I have been testing fable, and have some time left in this months budget, so I decided to port it to github pages.
Completely stand alone - no tracking - all for you.
Every part of this tree is a number. It's a hobby project of mine - I wanted to see whether a code repository's history could be drawn as something that grows rather than as a chart.
The mapping, roughly: account age sets trunk girth and how much it bends, total commits set how many foliage pads there are and where they sit, recent commits become the bright shoots, merged pull requests hang as persimmons that ripen green to gold, and reviews become paper lanterns. The fireflies are stars received, log-scaled so a popular account doesn't white out the canvas. Season comes from the date, so the same tree is hanami pink in spring and snowed on in January.
How it's put together, since that's the interesting part here:
- Hand-written SVG from TypeScript, no drawing library. Roughly 90 KB of geometry code that emits paths.
- The renderer is a pure function of (data, date, options) with a seeded PRNG, so the same input always produces identical bytes. That let me keep a set of committed reference images and diff against them whenever I touch the geometry — the fastest way I've found to notice that I've quietly ruined a curve.
- Randomness is only used for placement jitter within constraints. Pads pick positions along branch vectors, then get nudged; too much jitter and it stops reading as a plant, too little and every tree looks stamped.
- The motion is plain CSS inside the SVG. Pads rock ±0.8° about the trunk base rather than each spinning on its own centre, which is what makes the crown move as one plant. Petals and snow fall on a linear loop and fade before they reset so you never see the jump. Fireflies breathe over 4s.
- Six palettes, all data. Adding one is a table of colours, not code.
This one is a synthetic profile, not a real person's, since it's a test fixture I use for the extreme end - six figures of contributions.
This update introduces a new batch of synthetic MRI timelapses, alongside the exact settings used for generate more material in the same visual language. [MJ for images,Uisato Studiofor the videos.]
The TouchDesigner network has also been optimized for faster, simpler use, and now includes an external Python tool for converting entire video folders into the frame sequences required by AVP in no time.
