The player runs the camera's own firmware file, which this site does not hold: choose it above or drop it anywhere on this page. It is read in this browser and never uploaded.
OM System's firmware page
lists the releases but offers no .BIN: its update tools fetch the file from OM System's update service.
That service and its download server send no CORS headers (checked 2026-10-29), so this page cannot fetch the file
for you, and it goes through no relay. In a terminal (macOS or Linux), this command asks the same service and saves
the file in the current directory:
The service hands out each camera's latest release only: if OM System has published a newer one than
the release this player runs, the player refuses it and names the file it needs. The download is subject to OM
Digital Solutions' software licence, which the service's reply carries. With the repository cloned,
node emu/bin/fetch-fw.mjs does the same and also unpacks the blocks for the node tools.
The camera's sensor, image pipeline, AF and release are not modelled. This stand-in renders a synthetic scene (layers at three distances, a thin lens on a Four Thirds sensor, the exposure triangle) into the live-view bank, and the firmware's own through-image API shows it on the IMG1 plane (it needs A15). S1 focuses on the layer under the AF point S2 records a capture with the exposure in use and REC starts and ends a clip: all three are the stand-in's, not the firmware's. The firmware's camera application answers S1 and S2 itself (the date prompt, the shooting information, the focus confirmation, the capture display for the shutter time in use, the rec view), with the modules' notifications of a release stood in (S-RELSEQ). REC records with the mode dial at Movie (position 7) after the LLPSW firmware key (Firmware keys, 1.1.4 0x121c) is released; with LLPSW pressed, as the lab's idle image has it, the application refuses the key's function.
Subject detection: the scene's subjects are its patterns' (the moving scene's rider and the race scene's two motorcycles stand for motorsport subjects, the motorcycles' helmets for their parts); the scene takes no subjects of its own at run time. The camera's own setting chooses the kind (id 1682, 1 motorsports to 5 animals: its menu, or the debug API's token SET:1682=1), and while it names the kind of a subject the live view shows, DISP_FRAME draws the frames natively from MDET's own frame table: on the OM-1, CPU 3's MDET runs natively on the scene's subjects as the engine's records and reports a subject from its seventh frame (elsewhere S-SUBJECT writes the table where MDET would).
reading the session…
Take out and Put in are the card inputs (S-MEDIA: the card switch changes as a body's does, UI_IN decodes it and the firmware unmounts and mounts the card; E143). The list is the card's sectors read between the lab's steps with the independent FAT and exFAT readers (refs/fat.mjs, refs/exfat.mjs: refs/volume.mjs picks one by the card's boot sector), not through the firmware: a file being written can show as it was before, and the card out of the slot is the settled view. Pictures are decoded with the independent JPEG decoder (refs/jpeg.mjs).