Skip to content

RigFX - Changelog

This documentation describes RigFX firmware 1.13.0, released 2026-11-06.

Firmware files for each release are named rigfx-firmware-vX.Y.Z-<edition>.hex. See Firmware update to install one.

November 2026

  • 1.13.0, 6 Nov — OptiTrack with Motive 3.5, the Slider + FR7 preset, the external encoders on any lens ring, and the whole OpenTrackIO transform list.

Sources

  • OptiTrack works with Motive 3.5 — With Motive 3.5, RigFX connected to Motive but never received the rigid body: the OptiTrack card stayed on "No rigid body with ID 1 in stream" while another application (eZtrack, for example) tracked it on the same Motive. Motive 3.5 announces NatNet 4.5 but, unless an application asks for a version, sends the older NatNet 4.0 data format, which RigFX misread. RigFX now reads every NatNet 4.x format, whichever Motive sends, also when another application on the same Motive asks it for a different version. RigFX never asks for a version itself, so it does not change what the other applications receive. (1.13.0)
  • Supported OptiTrack versions — Motive 3.0 to 3.5 (NatNet 4.0 to 4.5), tested with Motive 3.5.1 (NatNet 4.5). Motive 2.x (NatNet 3.0 / 3.1) sends the same data format as NatNet 4.0 but has not been tested. Not supported: Motive 1.x (NatNet 2.x), and Multicast streaming (set Motive's Transmission Type to Unicast). Other applications can receive the same Motive at the same time. (1.13.0)
  • The whole OpenTrackIO transform list — An OpenTrackIO stream that gives the camera pose as a list of transforms (a tripod, then a head, then the camera) is now combined in order into the camera pose, as the protocol defines it. RigFX used only the transform named "camera" (or the only one), so a list, such as the Chain transforms output of another RigFX, gave no pose. Each transform is also offered on its own when binding a rig field (OpenTrackIO · 1, 2 …, with the name the sender gives it), so a node can follow one stage of the sender's rig, and the OpenTrackIO card lists the transforms received with the camera pose they combine into. (1.13.0)

Lens

  • External encoders on any lens ring — In Encoder mode of the Lens FIZ source, encoder 1 (Zoom connector) and encoder 2 (Focus connector) can each drive focus, iris or zoom, or nothing: a prime lens with focus on one encoder and iris on the other works. The default stays zoom on encoder 1 and focus on encoder 2; iris is no longer reported in Encoder mode unless an encoder drives it. (1.13.0)
  • Prime lens files without zoom — A lens file that does not depend on zoom (a prime) now runs on focus alone, without a lens warning when no zoom is mapped: with the sync card's encoders, or with Kuper or Filmotechnic encoders. (1.13.0)

Camera Rig

  • Slider + FR7 preset — A Sony FR7 on a slider whose rail runs between two tripods (2 m by default), the carriage position read from the X of FreeD 1, counted from the second tripod. Offered on every firmware, with a "what to measure" figure. The rail can run in any direction, along X or Y, either way: the 3D view's clamps and carriage follow it, and the rail node's Pan set to the rail's direction makes the carriage move along it. (1.13.0)
  • Cameras pointing straight up or down — A tracked body or a rig node pointing nearly straight up or down no longer gets a wrong orientation (up to 40° off with an OptiTrack body, 4.6° and 8 cm through a rig node), and its pan and roll stay continuous through vertical. (1.13.0)
  • e-Jibo — Cartoni's e-Jibo is spelled as Cartoni writes it, in the preset names, the 3D view and the measure figures. (1.13.0)

Web app

  • Restoring a large configuration — Restoring a saved configuration larger than 4 KB on the System card no longer fails. (1.13.0)

October 2026

  • 1.12.0, 30 Oct — Bind one axis of a tracking input to any rig field, and set the FreeD lens range on the Settings card.
  • 1.11.1, 30 Oct — The base firmware edition is now called "standard".
  • 1.11.0, 28 Oct — Two new tracking inputs, Filmotechnic and Kuper, each with its own firmware edition, and steadier tracking output timing.
  • 1.10.3, 16 Oct — Maintenance release, no change visible to users.
  • 1.10.2, 16 Oct — The e-Jibo and e-Sensor equipment in the 3D view and the matching rig presets follow Cartoni's drawing, and the browser tab shows the unit's name.
  • 1.10.1, 14 Oct — The phase offset is easier to find and set, and the e-Jibo and e-Sensor rig presets are revised.
  • 1.10.0, 9 Oct — The unit now tells you when the sync card is missing or silent, starts with a ready-made rig, and its serial console is quiet and readable.
  • 1.9.3, 8 Oct — OpenTrackIO timecode now follows Sony's conventions, so a 50 or 59.94 Hz camera can be the timecode source.
  • 1.9.2, 8 Oct — Fixes and additions from validating the OpenTrackIO output against a Sony FR7 stream, plus a phase offset guard.
  • 1.9.1, 5 Oct — The rig live in 3D with ready-made presets, the phase view, DHCP, and tighter sync timing.

Camera Rig

  • One axis of a tracking input on any field — Each axis of a FreeD, OptiTrack, OpenTrackIO or Canon CV input (X, Y, Z, pan, tilt, roll) can now be bound on its own to any field of a rig node, like an encoder channel: take only the FreeD tilt, for example. Positions are in metres and angles in degrees. (1.12.0)
  • Easier source picker — The list of sources for a field is grouped by input with short names ("FreeD 1 · Tilt"), opens wide enough to read, and gets a search box when the list is long. (1.12.0)
  • e-Jibo + FR7 preset removed — The FR7 mounts under the e-Jibo, so the e-Jibo + FR7 underslung preset is the one to use. A rig already saved on a unit is not changed. (1.11.1)
  • e-Jibo and e-Sensor presets sized from Cartoni's drawing — The e-Jibo presets (e-Jibo + e-Sensor, e-Jibo + FR7, e-Jibo + FR7 underslung) now use the drawing's dimensions: the jib pivot sits 0.244 m above the tripod (it was 0.26 m), the arm is 0.928 m, its shortest setting (it was 1 m), and the head plate is at its shortest setting. The e-Sensor tilt axis, on the two e-Sensor presets (e-Jibo + e-Sensor, Tripod + e-Sensor), is 0.132 m above the head's base (it was 0.13 m). Rigs already saved on a unit are not changed: load the preset again to get the new values. (1.10.2)
  • Sensor offset ends at the sensor plane — The FR7 presets now put the sensor offset at the FR7's sensor plane, 0.048 m behind the tilt axis (it was 0.03 m, the lens mount). The e-Sensor presets raise it to 0.17 m above the tilt axis (it was 0.151 m) so the camera body sits on the head's plate. These values are starting points: measure the offset on your own rig. (1.10.2)
  • Revised e-Jibo and e-Sensor presets — e-Jibo + e-Sensor, e-Jibo + FR7, e-Jibo + FR7 underslung and Tripod + e-Sensor now use a 1 m tripod (it was 1.09 m on the e-Jibo presets and 1.38 m on Tripod + e-Sensor) and a 1 m e-Jibo arm (it was 2.2 m). The jib head's pan and tilt, and the e-Sensor head's pan, now turn the other way. Rigs already saved on a unit are not changed: load the preset again to get the new values. (1.10.1)
  • Ready-made rig — A unit with no SD card or no saved rig starts with a tripod (1.00 m), a fluid head (0.25 m above it) and a camera sensor offset (0.12 m), instead of three unnamed nodes. Units that already have a saved rig are not changed. (1.10.0)
  • Rig presets — Load a ready-made chain (tripod, e-Jibo with its head plate, FR7 ceiling and more) in one click instead of building it node by node. (1.9.1)
  • Move rig nodes — Each node card has up / down buttons to reorder the chain. (1.9.1)
  • Reset offsets — The studio and sensor offset cards have a reset-to-zero button, and offset and node values show whether they are saved. (1.9.1)
  • Rig node binding — Rebinding a rig field to another source no longer carries over the previous source's "negate" setting. (1.9.1)

Sources

  • FreeD lens range on the Settings card — Each FreeD input has a Lens auto range switch and the min / max of zoom, focus and iris. With auto range on, zoom and focus show the range learned from the sender (Reset learns it again); with it off, the range you enter is saved and shows as Cal Min / Max on the Lens page. Iris always uses the range entered. (1.12.0)
  • FreeD lens end stop at 0 — Auto range now learns a zoom or focus end stop whose raw value is 0, so the lens reaches that end of its travel. (1.12.0)
  • Cartoni glitch tolerance — A single bad reading on an encoder channel no longer zeroes pan or tilt for a frame: the last good value is held for up to 3 frames before the channel is reported lost. Disabled or unplugged channels no longer delay the output. (1.9.1)

Firmware editions

  • Lens edition renamed standard — The base edition, with the lens, FreeD, OpenTrackIO and Canon CV inputs, is now called "standard": its firmware file is rigfx-firmware-v1.11.1-standard.hex and it shows as "standard" in the Flasher and on the firmware update page. Only the name changes: a unit on the lens edition takes the standard firmware like any other update and keeps its settings. (1.11.1)
  • Two new editions — "filmotechnic" and "kuper" each add one input to the lens edition. The edition shows in the Flasher and on the firmware update page. (1.11.0)
  • Each edition carries only its own equipment — The 3D equipment models in a firmware are now only those of its inputs (every edition keeps the tripod, fluid head, camera and FR7), so the lens firmware is about a quarter smaller. The rig presets and the node Type selector offer only what the unit can use. (1.11.0)

Filmotechnic input

  • Technoscope crane, Flight Head and encoder inputs — Receives the Filmotechnic box's data over the network (port 9000 by default, off until enabled): the head's pan, tilt and roll, the crane's pan, tilt and reach, and seven encoder inputs, each with its own enable, scale, offset and Set 0. A Settings card and a dashboard row show the live values. (1.11.0)
  • Lens from the encoder inputs — The Settings card picks which encoder inputs drive focus, iris and zoom, and the Lens page can use them as its FIZ source. (1.11.0)
  • Technoscope F27 and F17 + Colibri presets — Two rig presets with 3D models drawn from Filmotechnic's drawings. Loading one also sets the crane's reach for that model (F27 1.40 m, F17 1.32 m retracted). (1.11.0)

Kuper input

  • Kuper motion control and Ravensclaw Talon / Nano heads — Receives the axis stream over the network (port 9100 by default, off until enabled), up to 16 axes, each with its own enable, scale, offset and Set 0. Talon, Nano and Raw counts presets set the scales in one click, and the zoom and focus axes can drive the lens. (1.11.0)
  • Tripod + Nano head preset — A rig preset with a 3D model of the Nano head drawn from Ravensclaw's datasheet. Loading it also sets the Nano scales on the Kuper input. (1.11.0)

Sync & Timing

  • Steadier tracking output — With Output at Pulse on, a web page left open on the unit could delay a FreeD or OpenTrackIO packet by up to 6 ms. The unit now keeps the network free around each send: in the same test, late packets went from 47 to 2 and the worst delay from 3.4 to 2.0 ms. (1.11.0)
  • New inputs in the phase view — Kuper and Filmotechnic each get a lane showing when their data arrives against the sync pulse. (1.11.0)
  • Phase marker in free run — Without a sync card the phase offset is not applied; the marker is now greyed out to say so. (1.11.0)
  • Phase offset slider — The Phase Offset setting has a slider next to its number box, so the delay can be dragged as well as typed. (1.10.1)
  • A phase marker you can see and grab — In the Phase View, the PHASE marker is now a grip tab that grows under the pointer, with a larger grab area on a phone or tablet. A line above the chart says to drag it, and double-clicking it jumps to the number box to type a value. (1.10.1)
  • Sync card status in the web app — When the sync card is not connected, stops answering, answers but sends no sync pulses, or is waiting for its external reference, the Sync & Timing card says so and what to check, instead of leaving a frozen timecode on screen. The timecode shows zeros in red, the timecode in the top bar and sidebar turns amber, and the dashboard Sync tile reads No card, Lost, No pulse or No ref. Nothing is shown while OpenTrackIO is the timecode in use. (1.10.0)
  • Recovery after a firmware update — A sync card that stayed silent after the unit was flashed (timecode frozen until the sync settings were edited) is now handled: the unit keeps asking the card for its settings until it answers, and if a card set to freerun answers but sends no sync pulses, its own settings are sent back to it. The saved sync settings are now always applied at start-up; they were sometimes missed. (1.10.0)
  • Sync settings you never chose are no longer applied — Saving an unrelated change used to store a 24 fps freerun setting as if you had chosen it, and the next restart pushed it to the sync card. Only sync settings you set are saved now. A saved configuration that already holds that default still applies it: set the rate again if needed. (1.10.0)
  • Steady clock without the sync card — With no sync card the unit keeps running at the saved sync rate, or at 25 fps when none was saved (it used to run at 60 fps), and the FreeD and OpenTrackIO outputs report that rate instead of a fixed 24 fps. (1.10.0)
  • OpenTrackIO timecode source at 50, 59.94 and 60 Hz — A camera's 25 or 30 fps timecode with sub-frames now matches the unit running at twice that rate (it always fell back to the hardware timecode before). Sony's non-drop 29.97 and 23.98 modes match as well. At 29.97 and 59.94 Hz the drop-frame mode must also agree. (1.9.3)
  • Timecode as the camera shows it — Above 30 fps the dashboard, sidebar and top bar show the camera's frame (0–24 at 50 Hz) instead of the raw 0–49 count. Hovering shows the raw count. (1.9.3)
  • Sub-frame marker — The Sync card shows which sub-frame the sample is, with a pair of dots after the frames and a line saying how the timecode is built. (1.9.3)
  • Timecode source status — A short status beside the Hardware / OpenTrackIO selector tells you what is in use (in use, no signal, no timecode, rate mismatch, external timecode, or auto-generated when no external timecode is detected). The controls below no longer jump, and the TC light turns on when OpenTrackIO provides the timecode. (1.9.3)
  • Timecode source — The Sync & Timing card can take the output timecode from the incoming OpenTrackIO stream (for example the camera's own clock) instead of the sync card. Whenever the stream is absent, has no timecode or runs at a different frame rate, the sync card's timecode is used and the reason is shown. (1.9.2)
  • No jump at minute changes — The sync card's timecode no longer steps back by almost a minute for a few frames when the seconds wrap from 59 to 00, on the dashboard and on the outputs. (1.9.2)
  • Phase offset follows the frame rate — Changing the frame rate reduces a phase offset that no longer fits the new frame to 90% of its period (35 ms set at 25 Hz becomes 30 ms at 30 Hz), and a configuration saved earlier is corrected at start-up. Before, the unit slipped against the sync pulses and the source timing drifted across the frame. The phase view's drag limit now follows the frame rate as well. (1.9.2)
  • Phase view — A new timing view shows when each source (sync card, Lens FIZ, Cartoni, network inputs) arrives within the frame, and the measured output latency, to set the phase offset by eye. (1.9.1)
  • Output at Pulse — With Output at Pulse on, tracking packets leave on the sync pulse instead of after the phase offset, and the output latency is measured and shown. A case where it sent nothing at all is fixed. (1.9.1)
  • Tighter sync timing — The unit reacts to each sync pulse at once and times the phase offset precisely, removing up to 0.1 ms of jitter from every frame. (1.9.1)
  • Keeps running without sync — If the sync pulses stop for two frames, the unit keeps running at the set frame rate and locks again when they return. (1.9.1)

Tracking outputs

  • Clearer OpenTrackIO options — An "options" link under Protocol opens them, grouped by the receiver they are for, each with a line saying when to enable it: CalibFX Lineup (Chain transforms) and Aximmetry (Invert Cx, and Legacy distortion order for Aximmetry 2025.3.0 or earlier). (1.11.0)
  • OpenTrackIO timecode written like Sony's — The timecode frame rate is now the timecode's own counting rate (24, 25 or 30 fps; 30000/1001 in drop frame) instead of the sample rate. Above 30 fps (50, 59.94, 60 Hz) the timecode counts at half that rate and a sub-frame number tells the two samples inside each frame apart. Sample rate and capture frame rate keep the real rate. (1.9.3)
  • OpenTrackIO frame rates in Sony's form — Rates are written the way Sony writes them, 25 fps as 25000/1000, so a capture lines up field for field with a Sony camera's. The values are unchanged. (1.9.3)
  • OpenTrackIO matches the Sony reference — The output reports the OpenTrackIO version it follows, sends frame rates as exact fractions (29.97 Hz goes out as 30000/1001 instead of 29/1), and numbers its packets once per frame, so a receiver no longer counts every other packet as lost when two outputs are enabled with different options. (1.9.2)
  • Camera and lens metadata passed through — Camera label, serial number, firmware version, ISO and shutter angle, and the lens serial number, firmware version, nominal focal length and raw encoder counts received from the source are shown on the Lens page, can be overridden, and are sent on in OpenTrackIO. This unit's own serial number and firmware version are reported as the tracker's. (1.9.2)
  • OpenTrackIO packets stay valid — Aperture, pinhole focal length and focus distance are left out until they have a real value instead of being sent as 0, which strict receivers rejected (for example with a FreeD FIZ source that has no iris). (1.9.2)
  • OpenTrackIO drop-frame flag — The timecode's drop-frame state is now reported at 29.97 and 59.94 Hz when it is known. (1.9.2)
  • OpenTrackIO rate and timecode with another lens source — With another lens source the output advertised 24 fps and a zero timecode while the unit was locked at 25 fps; it now follows the unit. A timecode outside the valid range is sent as 00:00:00:00. (1.9.2)
  • Small values keep their precision — Distortion coefficients, projection offset, entrance pupil and the encoders were rounded to six decimals (a k1 of -3.0912345e-4 went out as -0.000309). They keep their full precision in the output, in the saved lens overrides and on the lens readout, so an override reloaded after a reboot is what you typed. (1.9.2)
  • Output monitor — The output card shows each output's live send rate, and flags failures only while they are happening. (1.9.1)

Lens

  • Lens source mode kept — Turning the Lens FIZ Source off and on again no longer resets its mode to Canon. (1.11.0)

3D view

  • e-Jibo counterweights — The counterweight discs now sit between the two lock nuts on the counterweight shaft. (1.11.0)
  • Equipment redrawn from the real parts — The jib pivot, arm, end bracket, levelling plates and e-Sensor head follow Cartoni's drawing and photos of the plates, with a separate plate for the e-Sensor (bowl) and for the FR7 (disc). The tripod legs end in cast foot blocks, the camera has a 16:9 matte box and no rods, and the camera model starts at the sensor plane, which it marks with a circle crossed by a line. (1.10.2)
  • View cone starts at the entrance pupil — The camera's view cone now starts at the lens's entrance pupil instead of the sensor, so it matches how the field of view is measured. (1.10.2)
  • 3D rig view — The Camera Rig page and the dashboard show the rig live in 3D: every node moves with the real pan, tilt, roll and offsets, and the camera's view cone follows the lens. Two looks are available: a wireframe view and a graphite "Maquette" view with lighting and shadows. Each node's Type selector can show it as an equipment model (tripod, jib, heads, FR7 ceiling rig and more). (1.9.1)

Web app

  • Unit name in the browser tab — The tab shows the unit's name before RigFX (its serial number when it has no name), so several units can be told apart in the tab strip. It follows a rename made in System Info. (1.10.2)
  • Dashboard status at a glance — The dashboard shows the quality of the connection to the unit; pose, FIZ and lens readouts dim when their data is stale; Network and Link are merged into one indicator; a heartbeat under the logo (and in the phone top bar) shows the page is live. (1.9.1)
  • Clearer errors and confirmations — Failed changes are reported instead of silently ignored, actions that delete lens data or the configuration ask for confirmation, and deleting the configuration offers Undo. (1.9.1)
  • Consistent naming — Rig and pose names are the same on the Dashboard, Camera Rig and Settings pages. OptiTrack's Mode, Multiplier and Subframe settings are tucked behind an Advanced section. (1.9.1)
  • Phone portrait layout — Settings pages, lens readouts and phase charts fit a phone held upright, and an outdated page reloads itself. (1.9.1)
  • Same dropdowns on every browser — Dropdowns look the same on every browser, warning icon included. (1.9.1)
  • Smoother live display — The timecode, FIZ gauges and rig cards update without flicker or lag, and the 3D view redraws only when something moves. A typed value is sent once you stop typing, a switch holds your choice until the unit confirms it, and going back to a page is instant. (1.9.1)
  • One update per frame — The web app receives exactly one update per frame (24–60 Hz), so the timecode counts smoothly and no frame is repeated or skipped. (1.9.1)
  • Faster reconnection — Switching tabs no longer disconnects the page from the unit, and a lost connection comes back within a fraction of a second. (1.9.1)
  • "In use on another device" page — When another device holds the live data, or takes it over, the page is replaced by a full-screen notice with a single "Take control" button, so two devices can no longer bounce it between them. The device that loses control is told so instead of reconnecting by itself, and a browser that stopped responding no longer blocks a new one. (1.9.1)
  • Full-precision lens readouts — Lens readouts in the web app keep their full precision. (1.9.1)

Serial console

  • Startup banner — Shows the RigFX version, the edition, the exact build with its date, and the unit serial number. (1.10.0)
  • Plain, quiet messages — The console now only reports what matters (network, sync card, SD card, settings, web page connections, firmware and lens file operations) in plain words. The periodic status report is gone, and a busy start-up no longer loses lines silently: the console says how many were dropped. (1.10.0)
  • Warnings that mean something — Memory warnings are in plain words, a missing lens file selection is no longer reported as a failed load on every start, and starting up without the sync card yet no longer raises a sync warning. (1.10.0)

Network

  • DHCP — The device can take its address from a DHCP server, with the static address used as a fallback if no lease arrives within 10 seconds. Selectable in the web app and in the Discovery tools. (1.9.1)
  • <name>.local address — The device advertises itself on the network by name; the address is shown on the network settings page. (1.9.1)
  • Network save no longer freezes the device — Saving network settings used to be able to hang the device; it now applies cleanly and the web app follows the device to its new address. (1.9.1)

Reliability

  • No more periodic hiccup — The tracking output no longer pauses briefly every 200 ms, and a network input (OptiTrack, FreeD, OpenTrackIO, Canon CV) can no longer give a pose mixed from two packets. (1.9.1)
  • Settings survive a power cut during a save — The previous settings stay on the SD card until the new ones are written, and come back if the power fails in between. (1.9.1)

September 2026

  • 1.9.0, 22 Sep — The web app works on phones and tablets.
  • 1.8.0, 22 Sep — Fixes a freeze in long sessions, and the web app can no longer hold up the tracking output.
  • 1.7.0, 22 Sep — Lens files can drive the aperture, with smoother focus distance and aperture curves.
  • 1.6.1, 7 Sep — A second Aximmetry switch on OpenTrackIO outputs, for the sign of the centre shift.
  • 1.6.0, 7 Sep — Frame delay on the FreeD and OpenTrackIO inputs.
  • 1.5.0, 1 Sep — A simpler Tracking Outputs page, and OpenTrackIO chain output fixed for larger rigs.

Web app

  • Phone and tablet support — The web app adapts to the screen: on a phone the navigation becomes a slide-in menu behind a top bar and every dashboard card, the 3D view and the settings forms stack vertically; on a tablet held upright the sidebar collapses to icons. Typing in a field no longer zooms the page on an iPhone, and the page height follows the mobile browser's toolbar. (1.9.0)
  • Reliable page loading over Wi-Fi — A phone or tablet on Wi-Fi could get a blank page when its connection paused for a moment; pages now load reliably. Reloading the page no longer downloads the web app again unless the firmware has changed. (1.9.0)
  • Live data at full rate on phones — On an iPhone the web app showed only about 2 of the updates it received each second, so every page refreshed roughly once a second. It now shows them all (about 21 a second in our test on an iPhone 13 Pro). (1.9.0)
  • Steadier connection on Wi-Fi — On a phone or tablet the page rides through Wi-Fi's short gaps instead of reconnecting, and it lets go of the unit while in the background (phone locked, app switched) so another device can connect. The 3D view pauses while hidden and uses less detail on phones to save battery. (1.9.0)
  • Known issue: the timecode still does not look perfectly smooth on a phone — The live data arrives at full rate and the display is correct, but the frames counter does not read as fluidly as on a computer. A phone on Wi-Fi gets its updates less regularly, so the counter visibly skips values. This is cosmetic and affects no tracking output. (1.9.0)
  • Faster Settings and Lens page loading — The Settings and Lens pages open faster and no longer load only partly, and the lens file list is ready at once. (1.8.0)

Reliability

  • No more freeze in long sessions — During long sessions the device could run out of working memory and halt silently, with the front-panel LED frozen and the internal LED blinking two short pulses every two seconds. Working memory is now about five times larger, and running out degrades gracefully (a dropped packet or a refused web request) instead of stopping the device. (1.8.0)
  • Tracking output can no longer be held up by the web app — Saving the configuration, uploading or loading a lens file and other web actions no longer pause the tracking output, and a slow network no longer delays it. (1.8.0)
  • Loading a lens file no longer disconnects the web app — The web app stays connected while a lens file loads. (1.8.0)

Tracking outputs

  • OpenTrackIO chain output supports the full 16-node rig — With chain transforms on, rigs of up to 16 nodes are sent (the limit was about 10 nodes), and a lasting output problem no longer floods the console with warnings. (1.8.0)
  • New "Axi cx" switch on OpenTrackIO outputs — Each OpenTrackIO output's advanced panel has a second Aximmetry switch that flips the sign of the horizontal centre shift (cx). It works independently of the distortion-order switch; both can be on together. Called Invert Cx since 1.11.0. (1.6.1)
  • "Axi" renamed "Axi disto" — The Aximmetry distortion-order switch is now labelled "Axi disto", so the two Aximmetry switches read clearly side by side. Called Legacy distortion order since 1.11.0. (1.6.1)
  • Simpler Tracking Outputs page — The protocol dropdown is now just OpenTrackIO or FreeD. Protocol settings (FreeD camera ID, OpenTrackIO Aximmetry mode, OpenTrackIO chain transforms) are behind each row's "advanced" panel, so the main row only shows what applies to the selected protocol. (1.5.0)
  • Aximmetry and chain transforms can be combined — OpenTrackIO's Aximmetry distortion order and chain transforms are separate switches: enable either, both, or neither on the same output. (1.5.0)
  • Fixed OpenTrackIO chain output on larger rigs — With chain transforms on, an OpenTrackIO output stopped sending when the rig had more than about two nodes. It now sends the studio offset, the sensor offset and about 12 nodes (16 since 1.8.0). (1.5.0)
  • Same node list in every chain packet — The output always lists the studio offset, every rig node, then the sensor offset; a missing or invalid node is sent as a zero pose, so the receiver always sees the same list. (1.5.0)
  • Older settings load safely — An output saved with one of the removed protocols ("OpenTrackIO Aximmetry", "OpenTrackIO dev") is switched off at start-up with a warning instead of sending wrong packets. Choose OpenTrackIO again and set its Aximmetry or chain options. (1.5.0)

Status LEDs

  • Halt LED patterns documented — The LED reference now explains the 1-, 2- and 3-pulse halt patterns on the internal LED. (1.8.0)

Lens

  • Smoother focus distance and aperture curves — Lens files can carry PCHIP curves for focus distance and aperture, which follow the lens much more closely than straight-line interpolation, without the overshoot of a polynomial fit. Existing lens files are unaffected. (1.7.0)
  • Aperture from the lens file — The aperture data in .mrxlens files was ignored: the f-stop could only come from a lens source (OpenTrackIO, Canon CV) or be typed in. It now follows the iris from the lens file. Lens files without aperture data behave as before. (1.7.0)
  • Fixed f-stop not updating when the iris encoder is overridden — Setting the raw iris value by hand in Advanced Settings moved the encoder but left the f-stop at its previous value. (1.7.0)
  • Empty lens file curves no longer give a false value — An empty curve in a lens file (seen on some older aperture calibrations) gave a reading of 0 that looked valid. It is now ignored and the value shows as missing. (1.7.0)

Sources

  • Frame delay on FreeD and OpenTrackIO inputs — Both inputs' Settings cards have a "Buffer (frames delay)" setting, like Cartoni's: 0 adds no delay, and 1–10 holds back the pose, FIZ and lens data by that many frames, to line tracking up with a delayed video path. The delay counts sync frames, whatever the sender's packet rate. Saved with the unit's settings. (1.6.0)

May 2026

  • 1.4.0, 29 May — Firmware update from the web app, three firmware editions, and clearer OptiTrack status.
  • 1.3.0, 22 May — Override any lens value, name and identify units on the network, and clearer status LEDs.
  • 1.2.0, 18 May — The Flasher and Discovery tools, and a Cartoni firmware edition.

Firmware update

  • Firmware update over the network — Update RigFX from the web app: drop a .hex file in Settings, the unit checks it, shows a full-page update screen with the RigFX logo, installs the update, and the page reloads by itself when the unit is back. No more USB cable for routine updates. (1.4.0)
  • File check before installing — The unit checks that a .hex file is a valid RigFX firmware before installing it, and refuses any other file. (1.4.0)

Firmware editions

  • Three firmware editions — Releases now ship three firmware files: lens (base), optitrack (lens + OptiTrack) and cartoni (lens + Cartoni), named rigfx-firmware-vX.Y.Z-{lens,optitrack,cartoni}.hex. The edition shows in System info, and in the Flasher before flashing. (1.4.0)
  • Two firmware editions — Releases now ship two firmware files: rigfx-firmware-vX.Y.Z.hex (regular) and rigfx-firmware-vX.Y.Z-cartoni.hex (with the Cartoni encoder input). The Flasher shows the edition before flashing, so you can confirm you're loading the right one. (1.2.0)

Sources

  • Blackhelix input removed — The Blackhelix input is no longer available. (1.4.0)
  • OptiTrack rigid body warnings — When the rigid body is missing from the Motive stream, or present but not tracked (occluded, inactive), the unit stops passing on an old pose, raises a warning and says why on the Settings card ("No rigid body with ID N in stream" or "Rigid body N not tracked"). A single dropped frame does not trigger it. (1.4.0)
  • OptiTrack reconnects by itself — If Motive is not reachable at start-up or drops off the network for a moment, the unit tries again every second until Motive answers, instead of giving up after the first try. (1.4.0)
  • Less OptiTrack network traffic — The unit asks Motive for the chosen rigid body only, without markersets, skeletons or other rigid bodies, which helps most on busy capture volumes. (1.4.0)
  • FreeD camera ID filter — Each FreeD input channel can now ignore packets coming from a different camera ID, so multiple cameras can share the same network port without crosstalk. (1.3.0)
  • Canon CV distortion warning — Warns when a Canon CV source is used with the OpenCV distortion model, and recommends switching to OpenLensIO for accurate results. (1.2.0)

Web app

  • Source status LED in card headers — Each source card shows a status LED in its header, so the source's health is visible even when the card is folded. (1.4.0)
  • Redesigned system info panel — Cleaner, more compact layout for system, network and version information. (1.3.0)
  • Miraxyz branding — Sidebar logo and browser tab icon refreshed. (1.3.0)
  • 3D dashboard fix — Fixed a rendering glitch in the dashboard's 3D view. (1.3.0)
  • Timecode display refinements — FPS and lock state moved into the timecode area, and drop-frame is now a switch. (1.2.0)
  • Timing at low frame rates — Timing values in the web app no longer wrap around at 30 Hz and below. (1.2.0)

Tools

  • Per-tool version numbers — The Flasher and Discovery tools now carry their own version, independent of the firmware. This release ships with Flasher 1.0.0 and Discovery 1.1.0; each tool's version is in its filename and shown in the tool's window. (1.4.0)
  • Unit names and Identify — Each unit can be given a name, shown on the network. The Discovery tool has an Identify button that flashes the unit's LED, to find it in a rack of several. (1.3.0)
  • Tools show their version — The Flasher and Discovery tools now display their version number, making support and bug reports easier. (1.3.0)
  • RigFX Flasher (GUI + CLI) — Standalone Windows tool to update the firmware over USB. Drag-and-drop .hex, checks that the file is a RigFX firmware before flashing, and puts the unit in update mode automatically. (1.2.0)
  • RigFX Discovery (GUI + CLI) — Windows tool to scan the local network for RigFX devices and remotely set their network configuration. Scans all interfaces. (1.2.0)

Lens

  • Cleaner lens page — Every lens field (focal length, focus distance, entrance pupil, distortion, sensor size, etc.) can now be individually overridden on top of any source or lens file. Missing values show a dash instead of a misleading zero, so you always know whether a number is real, overridden, or unavailable. (1.3.0)
  • More reliable lens file upload — Lens files load correctly at start-up, a file too large is refused before it is uploaded, and uploading a lens file no longer freezes incoming tracking data. (1.3.0)

Status LEDs

  • Updated LED signals — The unit's LED patterns are reworked for clearer status at a glance (start-up, heartbeat, alarms, identify). (1.3.0)

Tracking outputs

  • OpenTrackIO with the whole rig chain — An OpenTrackIO output can send every node of the rig chain, not only the final camera pose. (1.2.0)

April 2026

  • 1.1.1, 1 Apr — Maintenance release, no change visible to users.
  • 1.1.0, 1 Apr — Maintenance release, no change visible to users.

March 2026

  • 1.0.0, 31 Mar — FreeD, Canon CV and OpenTrackIO inputs, warnings on the rig and the lens, and a new web app layout.

Sources

  • FreeD input — Receive FreeD D1 packets on up to 3 configurable channels. (1.0.0)
  • Blackhelix input — Receive Blackhelix tracking data over the network. (1.0.0)
  • Canon CV input — Receive Canon CV metadata with lens data (FIZ + distortion). (1.0.0)
  • OpenTrackIO input — Receive OpenTrackIO packets (binary or JSON) with pose and lens data. (1.0.0)
  • OptiTrack subframe selection — Pick one subframe when Motive runs faster than the frame rate. (1.0.0)
  • Cartoni channel enable/disable — Switch each channel on or off, with its status shown live. (1.0.0)

Tracking outputs

  • OpenTrackIO Aximmetry mode — Distortion coefficients in the order Aximmetry expects. (1.0.0)

Lens

  • Lens file resilience — Lens files load even when the unit's memory is low. (1.0.0)
  • Lens delay — The lens data can be delayed by a set number of frames. (1.0.0)
  • Lens warnings — A warning when the lens's source is missing or invalid. (1.0.0)
  • FIZ source with a lens file — Fixed problems when using a FIZ source together with a lens file. (1.0.0)

Camera Rig

  • Per-node warnings — Each rig node shows its own warning in the web app. (1.0.0)

Web app

  • Sidebar navigation — Redesigned layout, with a sidebar instead of the top bar. (1.0.0)
  • Dashboard source cards — Status cards that open the source's settings. (1.0.0)
  • 3D view — Shows the camera's view cone and highlights the selected rig node. (1.0.0)
  • Frame rate precision — The frame rate shows more decimals. (1.0.0)
  • Taking control from another browser — Detects when another browser holds the live data and lets you take it over. (1.0.0)

Network

  • Network settings set remotely are kept — Network settings changed from a discovery tool are now saved on the SD card. (1.0.0)

Sync & Timing

  • Sync and timecode settings kept — They now survive a restart. (1.0.0)
  • Phase offset saved — The phase offset is now saved with the settings. (1.0.0)

February 2025

  • 0.9.0, 25 Feb — First versioned release.

Sources

  • Cartoni encoders — Pan and tilt from up to 4 Cartoni encoder channels, read on every frame. (0.9.0)
  • OptiTrack — Tracks a Motive rigid body over unicast, with a subframe multiplier setting. (0.9.0)
  • Sync card lens input — FIZ data from the sync card, with external sync and timecode. (0.9.0)

Tracking outputs

  • OpenTrackIO — Full camera tracking metadata: pose, lens, timecode, distortion (Brown-Conrady). (0.9.0)
  • FreeD D1 — Multi-channel output with raw encoder passthrough. (0.9.0)

Lens

  • Lens files — Upload .mrxlens calibration files (8 slots); the lens file gives the focal length, focus distance, entrance pupil, projection offset and distortion from the lens encoders. (0.9.0)
  • Manual lens mode — Type the lens values in the web app. (0.9.0)

Camera Rig

  • Camera rig chain — Build the rig as a chain of nodes; each position or angle follows an input channel or a typed value. (0.9.0)

Web app

  • Web app — Camera rig editor, lens settings, tracking output settings, lens file manager, live pose, lens and timecode display. (0.9.0)
  • Live data — The web app shows live data and reconnects by itself when the connection degrades. (0.9.0)

System

  • Saved settings — Settings are saved on the SD card, and the configuration can be downloaded, uploaded or deleted. (0.9.0)