Foveon Lab
Try Sigma Photo Pro (SPP) presets on your Sigma SD1 / SD15 X3F files, side by side, in the browser —
without importing, clicking and waiting in SPP for every preset.

- Scans your folders for
.X3F files and reads the full-size JPEG embedded in each X3F
(SD1 Merrill: 4704×3136, SD15: 2640×1760). No Foveon raw decoding needed.
- Presets from three places: your own preset folder, a built-in pack of ~290 SD1/SD15
presets (base, negative/slide/portrait film looks, cine, B&W, white balance, scene), and the
presets you saved in SPP itself (Windows). Comma or dot decimals; identical duplicates folded.
Filter by camera,
[GROUP] tag, file or name. The film-look names describe the look only and
are not affiliated with any film maker.
- Grid view: one photo through every preset at once. Click a tile for a large view with sliders;
←/→ steps through presets, hold O for the camera original.
- Save as preset writes an SPP-importable XML (
FoveonLab_SD1.xml / FoveonLab_SD15.xml in the
presets folder; saving the same name replaces it instead of duplicating).
- Export next to the photo, in a
foveon-lab/ folder:
- JPEG — full resolution, preset applied;
- TIFF 16-bit — full resolution, preset applied, no 8-bit rounding (Deflate-compressed RGB, no
alpha) for further editing in Photoshop, Affinity, GIMP…;
- DNG (raw) — the X3F's raw data as a DNG 1.4 with colour matrices, for Lightroom / Capture
One / darktable (any Foveon body; it's raw, so presets are not applied).
- Calibration tools measure what SPP actually does, to replace guesses with measured curves (below).
Single Go binary, no runtime dependencies, runs locally on 127.0.0.1 only.
Download
Grab the file for your system from the latest release,
nothing else needed:
| System |
File |
| macOS (Apple Silicon and Intel) |
Foveon-Lab-….dmg → open it, drag Foveon Lab to Applications |
| Windows |
foveon-lab-…-windows-x64.zip → unpack, double-click foveon-lab.exe |
| Linux |
foveon-lab-…-linux-x64.tar.gz → unpack, run ./foveon-lab |
It opens in your browser; Folders… picks where your photos and presets are, Quit stops it.
Starting it again while it runs just reopens the browser tab. The Windows build is
Authenticode-signed; the Mac app is signed with a Developer ID, notarized and stapled by Apple.
The macos-*.tar.gz archives hold the plain command-line binaries.
Updates: from v0.3.0 on, Foveon Lab checks GitHub for a newer release (twice a day) and shows
Update & restart in the top bar. It downloads only files listed in a manifest signed with the
project's Ed25519 key, checks their SHA-256, swaps them in place and restarts on the same address.
Nothing is installed without your click; set FOVEON_NO_UPDATE=1 to turn the check off. On macOS
the app has to be in Applications (not run from the disk image) to update itself.
Releases are cut locally with go run ./tools/release -version vX.Y.Z -publish (signing keys never
leave the maintainer's machine; it refuses to publish unsigned binaries).
Build from source
go install github.com/biopoetic/foveon-lab@latest
or clone and go build -o foveon-lab.exe . (Go 1.25+).
Usage
foveon-lab # scans your Desktop, presets from "Desktop/foveon pack", opens the browser
foveon-lab -photos "D:\Photos;E:\Sigma" -presets "D:\SPP presets" -port 8777 -no-open
Photos are found up to 4 levels below each -photos folder.
Open in Sigma Photo Pro (Windows, SPP 6)
Open in SPP ↗ in the editor hands the current preset straight to SPP: it adds it to SPP's preset
list, makes it SPP's current adjustment and launches SPP on the photo — no XML import step.
How it works: SPP keeps no per-photo edits. Its preset list is
%LOCALAPPDATA%\SIGMA\SIGMA_PhotoPro6\X3F_Setting.xml and its current adjustment is the X3F_* keys in
SPhotoPro.xml there. Foveon Lab edits both only while SPP is closed (SPP rewrites them on exit),
backs them up first to foveon-lab-backups\ next to them (last 10 kept), and prefixes everything it
writes with [FL] so your own SPP presets are never overwritten. Your X3F files are never modified.
Black & white presets (the packs mark them with Saturation −1, or tick Monochrome in the editor)
are handed over with Saturation −2: in SPP −1 is only muted colour, −2 is fully grey. (SPP's separate
Monochrome mode can't be used — SPP always opens photos in Color mode, whatever its saved
X3F_FilterMode says.)
If SPP is already open, Foveon Lab offers to close it the normal way (a window close, never a forced
kill — SPP can still ask about unsaved work) and reopen it with the preset.
AI agent: pick and tune a preset for you
Click ✦ AI pick (grid) or ✦ AI (editor). A vision model looks at the photo, shortlists presets
by rendering them on it, compares the renders (each comes with objective stats: clipping, crushed
shadows, brightness, saturation, warmth), fine-tunes the best one, and explains its choice. You watch
every step live, then Open in editor to save it as an SPP preset or export it. You can give it a
direction, e.g. "warm film look", "moody", "natural skin".
Connect a provider in the app: open the AI panel, pick DeepSeek, OpenAI, Google
Gemini, OpenRouter or any other OpenAI-compatible API (it must accept images and tool calls),
paste your API key and click Test & save. Foveon Lab checks the key with one tiny request before
saving it. The key stays in Foveon Lab's settings file on your computer and is sent only to the
provider you chose; Remove key deletes it. You pay the provider directly.
Alternatively set an environment variable (used when nothing is saved in the app):
set DEEPSEEK_API_KEY=sk-... # Windows (export ... on macOS/Linux)
foveon-lab -ai-base https://api.openai.com/v1 -ai-model <vision model> -ai-key-env OPENAI_API_KEY
- Downscaled renders of the photo (≤ 768 px) are sent to the model provider.
- A run is typically 4–8 model calls, ~60–100k input tokens — about 1–2 US cents on DeepSeek
(September 2026 pricing).
- The agent judges the emulated preview, so its choices inherit the emulation's limits (see below).
Limitations — read this
- The preview is an emulation, not SPP. Sigma's algorithms (X3 Fill Light, colour modes, highlight
handling) are not public. The emulation (
render/) gets the direction and relative strength of each
preset right, not the exact pixels. Use it to choose and compare presets; develop final images in SPP.
- The source is the camera's own JPEG, which already has the in-camera colour mode applied (often
Vivid). "Compensate camera JPEG" undoes that approximately, from the X3F metadata
(
CM_DESC, SATU_DESC, CONT_DESC), so presets start from a more neutral base.
- ColorMode codes: 4 = Standard, 6 = Portrait, 7 = Landscape were inferred from preset packs; other
codes are unknown (the calibration pack probes them).
- White Balance / ColorTemp are kept and written back but not emulated.
- Cameras: tested on files from the SD9, SD10, SD14, SD15, SD1 Merrill, DP1, DP1 Merrill,
dp2 Quattro, DP0 Quattro, sd Quattro and sd Quattro H. Merrill bodies get the SD1 presets,
SD14/DP1/DP2 the SD15 presets (same sensor generations).
- SD9 / SD10 carry no full-size preview. Foveon Lab decodes their raw data at full resolution
with the bundled
x3f_extract from x3fuse-core
(Apache-2.0, with a small fix for these older files — see third_party/x3fuse-core). The first
view of such a photo takes a few seconds, then it is cached. Without x3f_extract it falls back to
the camera's 567×378 preview. A raw decode has no in-camera look, so it starts more neutral than
the JPEG-based previews of the other bodies.
Calibration: measuring SPP instead of guessing
foveon-lab calibrate # creates Desktop/foveon-calibration: preset pack + INSTRUCTIONS.txt + exports/
foveon-lab analyze # measures the exports → report.txt + calibration.json
Each [CAL] preset moves exactly one SPP control to a known value (e.g. Contrast +0.5); everything
else matches the neutral preset A00. You apply each preset in SPP to the same photo and save it as
<photo>_<code>.tif. analyze then compares every export with SPP's own neutral A00 export and
reports, per control:
- the tone curve (output vs input brightness),
- the saturation gain,
- a 3×3 linear colour matrix (for colour modes and colour adjust) and its fit error,
- whether it acts locally (Fill Light) — brightness shift by pixel vs. surrounding brightness,
- how far this project's emulation is from SPP for the same setting.
calibrate also suggests good calibration photos from your library (wide tonal range, colour,
little clipping). This is black-box measurement of SPP's output; nothing is decompiled.
Project layout
| Path |
What |
x3f/ |
X3F container: section directory, embedded JPEGs, PROP metadata |
preset/ |
SPP preset XML reading/writing |
render/ |
linear-light float pipeline emulating the SPP sliders |
calib/ |
calibration preset pack, export analysis, source-photo suggestions |
agent/ |
vision-model agent loop (tools: render_presets, render, finish) |
spp/ |
hand-off to an installed Sigma Photo Pro 6 (preset list + current setting) |
web/index.html |
the UI (embedded into the binary) |
go test ./...
Tests that use real X3F files or preset folders skip themselves when those are not on the machine.
Contributing
Issues and pull requests are welcome — especially calibration results (report.txt) from SPP, and
X3F samples from other Foveon cameras.
Third-party software
Release archives include x3f_extract from x3fuse-core © 2026 Sang Lee, Apache License 2.0,
itself derived from the Kalpanika x3f tools (BSD-style). Its license, notice and Foveon Lab's
modification are in third_party/x3fuse-core/.
Legal
MIT licensed — see LICENSE.
Sigma, Foveon, X3F and Sigma Photo Pro are trademarks of SIGMA Corporation. This is an independent
project, not affiliated with or endorsed by SIGMA Corporation. It reads the documented-by-the-community
X3F container format and never modifies your original files.