sigma-fp-lab
Extra recording modes, an on-camera menu to switch them, and a way to run your own code on the SIGMA fp (firmware Ver.5.02).
- Add-on
- Alpha
- Low brick risk
- Reversible
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
SIGMA fp, firmware Ver.5.02 only. Not the fp L.
fp-fc-scale-card.zip contains AutoRun.txt and a README.txt. No VSHL.BIN and no USB shell: the code is carried in the AutoRun and lives in RAM. Nothing is flashed.
Setup
- Menu → Custom → button settings → assign False Color to a button.
- Copy
AutoRun.txtto the SD card root (only oneAutoRun.txton the card). - Battery out for 10 s, battery in, power on with the card. Boot takes ~30 s longer than stock.
Use
On the button assigned to False Color:
| press | result |
|---|---|
| 1 | False Color / EL Zone on, and it stays on |
| 2 | the EL Zone scale across the bottom of live view |
| 3 | both off |
EL Zone or False Color follows your own False Color Style setting.
What it is
- Scale geometry and colours are the firmware's own:
FalseColorBarDrawerband table0xC0D1B74C(15 bands, half-stop bands 70 px, others 68), palette0xC0D1B34C(A,Y,U,V, converted with the firmware's matrix), label glyphs from theElZoneScalescene. - Drawn on the 16-bit main OSD layer inside the display submit (
0xC02E8A08), once per frame; a press paints the front buffer directly. - Press and release of the assigned button are the two
CameraIFmethods0xC03722E8/0xC0372330, replaced so the mode latches. - Emulator verification:
tools/verify_fcscale.py, 21 cases; render inbuilds/fcscale/scale.png.
Known
- The order of the three colour nibbles in the main layer's 16-bit pixel is not established from the firmware; the build uses A-R-G-B. If the -4/-3 bands show orange instead of blue on your camera, report it.
- Not tested: HDMI output, playback/menu/record transitions while latched.
Changing builds, reverting
A soft power cycle does not clear RAM on this camera. Pull the battery for ~10 s whenever you change to a different AutoRun.txt, and to revert: remove AutoRun.txt, battery out, cold boot.
RAM-only and reversible, but a RAM change can still spoil a take. Do not use it on a paid job.
Before you start
- How hard is it?
- EasyCopy a file or use a web page. No extra software.
- What you need
- Comfort with the command line
- An SD card or USB stick
- Can it break my device?
- Very unlikely to break anything.
- Can I undo it?
- Yes. You can go back to the official software.
Did it work for you?
Did sigma-fp-lab v0.6.0-test work on your Sigma fp?
No reports yet for v0.6.0-test.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: Sigma fp.
No compatibility information yet.
Getting started
From the project's README ("Try it"):
The easy way, no computer needed after the copy: grab a file from cards/, rename it to AutoRun.txt on the SD card root, and cold boot. Instructions and what each one does are in cards/README.md.
Latest dev builds: the newest cards, including work that has not been on a camera yet, are published as releases and as zips in cards/. A dev card is a real experiment: read its notes before booting it, and expect to pull the battery.
Build the full menu card yourself (needs your own firmware copy, see below):
.venv/bin/python tools/buildcombinedcard.py
That writes AutoRun.txt and VSHL.BIN into builds/combined-menu/. Copy both to the root of the SD card with a card reader, then cold boot with USB unplugged. The screen reads fpLAB MENU when it has loaded.
Live experiments over USB need a debug card and the fpSup USB shell running:
.venv/bin/python tools/histdeploy.py place # the histogram overlay payload .venv/bin/python tools/histdeploy.py start # its resident thread .venv/bin/python tools/histdeploy.py stop
Risk and recovery
- Brick risk
- Low
- Reversible
- Yes
- Requires opening the device
- No
From the project's README ("Safety"):
- fp Ver.5.02 only. Not the fp L, not other versions.
- Back up whatever is on the card first, and keep only one AutoRun.txt on it. Do not paste two projects' AutoRuns together.
- Cold boot with the battery out for a few seconds, card in, USB unplugged.
- Change options only while stopped, with the card finished writing. After changing one, switch the recording preset away and back before you roll.
- Anything over roughly 400 MB/s wants the SSD, attached before power-on.
- Back to stock: remove the files, battery out and in. RAM only is still not a guarantee against a lost take, so do not shoot anything you cannot reshoot.
- No firmware flashing path is involved, proven or implied.
Releases
| Version | Name | Released |
|---|---|---|
| v0.6.0-test | v0.6.0 — False Color / EL Zone toggle with the EL Zone scale (test release)Pre-release | 20 September 2026 |
| v0.5.0-test | v0.5.0 — test releasePre-release | 14 September 2026 |
| v0.4.2-test | v0.4.2 — test releasePre-release | 14 September 2026 |
| v0.4.1-test | v0.4.1 — panel stays down after the camera's menu (test release)Pre-release | 14 September 2026 |
| v0.4.0-test | v0.4.0 — the camera's menu is the camera's again (test release)Pre-release | 14 September 2026 |
| v0.3.1-test | v0.3.1 — fixes the double-click crash (test release)Pre-release | 14 September 2026 |
| v0.3.0-test | v0.3.0 — the panel gets a thread, and toggles now stick (test release)Pre-release | 14 September 2026 |
| v0.2.0-test | v0.2.0 — the menu is drawn by us now (test release)Pre-release | 14 September 2026 |
| v0.1.0-test | v0.1.0 — on-camera menu + false colour latch (test release)Pre-release | 14 September 2026 |