A deterministic repeat-pattern engine for textile printing. Give it artwork and a few numbers and it returns a tile a fabric bureau can run, measured in millimetres rather than pixels.
That band is a single 600 × 225 mm image, repeated by your browser on a plain rectangular grid. Nothing on this page repairs a seam, because there is no seam to repair: a motif that crosses the edge of the tile comes back on the opposite side, in the right place, before anything is written to disk.
A repeat that looks right on screen can still come back wrong from the printer. Three things decide whether it does.
A 120 mm repeat and a 400 mm repeat are different designs, not different zoom levels. Geometry is stored in millimetres and converted to pixels once, in the export layer, at whatever resolution the bureau asked for.
Wrapping a tile at its own edges is correct for a block repeat and silently wrong for a half-drop. Patternated wraps on the lattice itself, so half-drop, brick and diagonal are the same code path as block rather than a special case bolted on afterwards.
Scatter is pseudo-random and pinned to an explicit seed. The same document rendered on another machine, another platform or a later version produces byte-identical output, and the test suite asserts that rather than hoping for it.
These three are the same document. Same motifs, same palette, same seed, same 300 × 225 mm repeat. The only difference between them is one field.
row_offset: 0, col_offset: 0row_offset: 0.5col_offset: 0.5That is the whole of the difference, and the third one is where a tiling engine usually goes wrong. A half-drop cannot be produced by wrapping a rectangle at its own edges, and the failure is invisible until fabric comes back.
A pattern is not only what sits on top of it. Tartans, ginghams, stripes and ornamental grounds are generated from the same palette as the motifs, as slot indices rather than literal colours, so the ground and the artwork cannot drift out of colour with one another and a colourway is a parameter rather than a redraw.
Motifs arrive as PNG or SVG. The engine mattes them, trims them to their real extent and samples a palette, then places them at a size given in millimetres on the cloth rather than in pixels on the file.
The artwork on this page is generated test material, drawn to a written style brief so that separately generated images read as one illustrator. It exists to push real files through the ingest pipeline. It demonstrates the engine and is not a catalogue of prints.
Rust, no network access, no account, nothing to configure. The example below ships in the repository, so this produces the picture beneath it on your machine and not a near enough one.
# a seamless 3x3 field from artwork in the repository
git clone https://github.com/leon-mallett/patternated
cd patternated
cargo run -p pattern-cli -- render examples/drawings/pears.json --out pears.png --cols 3Patternated is AGPL-3.0 and is also used inside Captivated Ltd's own closed products. That works only because Captivated owns the copyright outright: a copyright holder is not a licensee of its own work. One merged contribution would put part of that copyright in somebody else's hands and the arrangement would quietly stop holding, so pull requests are closed on sight. It is not a comment on the patch.
What is wanted instead is a file that broke it, what it got wrong on fabric, or a feature and the constraint a printer imposed on you. All three are issues, and issues are read. If you would rather carry a change yourself, fork it: that is what the AGPL is for.
The desktop application exists and runs, and there are no tagged releases. An unsigned installer meets Gatekeeper on macOS and SmartScreen on Windows, and both tell the person who was about to try it that it is not safe, which is worse than offering nothing. Signed builds come first; the download appears here when they do. Until then the repository builds from source.