3dtours
0ac9f2ddfa
The Fujifilm RAF this was reported on opened with magenta through every white in the frame. The develop itself was the cast, not the tone curve fitted over it: run flat — white balance, matrix, knee, encode, no curve at all — the frame's bright neutral blocks came back 232,196,201 against the 223,232,236 the camera's own preview has there. The matrix is not it either; every row of `rgb_cam` sums to one, so a neutral triple opens neutral. What was wrong is the balance it was given. Neither balance LibRaw hands over is the one the frame was rendered with. `pre_mul` on that frame is R/G 2.296, B/G 1.307; `cam_mul` is 1.795, 1.626; the balance the preview's own bright neutral blocks imply is 1.588, 1.266 — and that one is readable: average the sensor triple behind each block the camera left bright and near neutral, and the ratio that equalises those blocks is the frame's white. So the develop reads it there, before the first draw, from the same preview map the tone curve is fitted on, and keeps LibRaw's tags only as the fallback a frame with nothing neutral and bright to read (a clipped or dark frame) falls back to. `cam_mul` is tried before `pre_mul` on that path: as-shot before daylight, measured 6.73 -> 5.27 on this frame where the reverse gave 6.66. Measured end to end through the real develop (LibRaw worker + CanvasKit, 64x64 block grid against the file's own preview), mean dE00 / mean dRGB: HAGIANG-20170202-FUJIFILM-418.RAF 6.73 -> 4.89 +5.8,+0.9,+0.5 -> 0.7,-0.5,-0.7 _DSF3087.RAF 7.52 -> 6.78 +1.6,+0.1, 0.0 -> 0.5,-0.2,-0.7 DSCF1701.RAF 6.86 -> 6.54 ~0 -> -1.5,-1.7,-0.9 _DSF7273.RAF 5.13 -> 4.66 +2.4,+1.0,+1.5 -> 1.8,+0.9,+1.5 _3279791.ORF 5.81 -> 5.93 ~0 -> -0.4,-0.2,-0.5 P1010256.RW2 9.60 -> 9.56 +2.5,+0.6,+0.7 -> 1.6,+0.4,-0.1 The four Fujifilm frames lose the cast; the Olympus and Lumix frames hold. The two that open as their preview (Nikon NEF, DNG) still do. The bright neutral fifth of both Fujifilm frames now differs from the preview by the same figure on all three channels — a difference in brightness, not in colour, which is the tone curve's business and not this one's. The read is on the frame, not on the brand or its tags, so the bodies with no sample here (Sony, Canon, Ricoh, Leica) take the same path. scripts/raw-develop-check.mjs had gone stale against the module and is back in step with it — the highlight gate's threshold, the gain's divisor, the preview-WB read and the tag order are pinned, and previewWhiteBalance now carries a case that hands it a plane and a map and reads the balance back.
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.