3dtours
15fb4422dc
The dust brush filled its hole with a blur of the hole's own rim — the light beside it, carried in. Right for a speck on a wall, and visibly thin over anything with structure: a stroke across a shirt came back as the average of a shirt. The fill is now a learned one. engine/inpaint.ts runs MI-GAN (andraniksargsyan/migan, the same `migan_pipeline_v2.onnx` inpaint-web ships) through onnxruntime-web on the visitor's own machine: 27MB of weights in public/models, WebGPU where the graph fits the provider, the processor otherwise, one warm-up pass so the first repair is not the one that pays for the kernels. It is handed the masked crop and nothing else — the model's mask polarity is 255 KEEP / 0 HOLE, the opposite of the obvious guess, and the other way round repaints the frame and leaves the hole (measured). Step 6e of the renderer cuts the crop at the resolution the model will actually run at (512 on its longest side — the graph is fully convolutional and would take a whole frame, and ten seconds over one), builds the mask from the brush's own circles, and draws the answer into the fill surface at its own place in the box. The composite, the feathered mask and the untouched frame around it are unchanged, so nothing outside the mask moves — and when the model cannot be had the blurred fill is still built first and still stands. The preview gets this for free: renderPhoto was already async and the preview was already debounced. Node probe: the model + polarity + read/write path run; heal-check.mjs keeps measuring the fallback and now asserts the wiring and the polarity. Browser: engine/inpaint.ts in a real Chromium returns a patch (hole moves, kept pixels within 0.02 of a level), and the built app renders a 42-spot stroke in 4.7s on single-threaded wasm with no fallback warning — 1.15s and the warning when the model is taken away.
RecipesCam
RecipesCam is a camera and photo-editing app built around recipes — reusable
looks that carry a film simulation plus a full set of adjustments. You shoot or
open a photo, dial in a look, and keep it as a recipe you can apply again, share
as a .recipe file, or save to your account.
It ships twice from one repository: a React Native (Expo) app for iOS and
Android, and a self-contained web build under docker/ that runs the same
render pipeline in the browser.
What it does
- Shoot with a recipe applied. Live viewfinder, GPS-tagged captures, and the recipe baked into the saved file.
- Film simulations. Built-in looks — PROVIPES, VELVIPES, CLASSIC CHRIPES, CLASSIC NEGIPES, ASTIPES, ETERNIPES, ACRIPES, B&W HIGH CONTRAST and the LC STREETLIFE pair — each with its own grain and tone curve.
- The full adjustment set. Exposure, contrast, highlights and shadows, saturation, colour temperature, clarity, grain, and an HSL mixer with a colour picker that samples straight off the photo.
- Geometry. Crop to a fixed ratio or free-form, quarter turns, and a straighten ruler, plus printed frames (classic border, retro instant, wall frame portrait/landscape).
- Finishing. Watermark and GPS stamp, EXIF carried through the export, JPEG written with a proper 300 DPI JFIF header.
- On-device upscaling. A Real-ESRGAN pass runs locally when an export asks for more pixels than the source has — no server sees the photo.
- Recipes. Save, favourite, export and import
.recipefiles; the web build keeps them in your account, the phone build also keeps them on device.
The two builds
| Build | Where | Stack |
|---|---|---|
| iOS / Android | repo root | Expo + React Native, @shopify/react-native-skia for the render pipeline, NativeWind for styling |
| Web | docker/ |
Vite + React, CanvasKit (canvaskit-wasm) for the same pipeline, Fastify + SQLite API for accounts and recipes |
The render engine is shared by design: the web build compiles the app's own
src/utils/* and type definitions unchanged, with @shopify/react-native-skia
aliased to a CanvasKit shim (docker/frontend/src/engine/skiaShim.ts). A look
looks the same on both because it is the same code.
Running the web build
cd docker
cp .env.example .env
docker compose up -d --build
# → http://localhost:8090
Photos never leave the browser: grading, framing, watermarking and JPEG
encoding all run in the visitor's tab; the API only stores accounts and recipe
JSON. See docker/README.md for the layout and the proxy setup.
Running the app
npm install
npx expo start # Expo Go / dev client
npx expo run:android # or run:ios for a native build
Repository layout
App.tsx, src/ the Expo app: screens, tool rail, viewfinder, shaders
docker/ the web build (frontend + API + compose file)
frontend/shared/ vendored copies of the app's types and utils
frontend/src/engine/ CanvasKit shim, export engine, super-resolution
docs/ privacy policy
THIRD_PARTY_NOTICES.md licences of the bundled fonts, models and libraries
Licence
See LICENSE and THIRD_PARTY_NOTICES.md.