fpsup-v0.1.10

Reads the new Gyro2 camera format. Update to this release before you open CinemaDNG footage recorded with the new Gyro2 sup (40GYR2.BIN); older plugin releases report "unsupported block version 2" for that footage.

What changed

• Gyro2 now writes its motion data to its own MakerNote tag (0x4653) in each DNG frame. The plugin reads that tag first.
• Each frame records the sensor mode. The plugin computes the rolling-shutter readout time and the sensor crop from it, so a different frame rate or resolution gets the correct values.
• Each frame records the lens's calibrated focal length. The plugin uses it when the lens is not zoomed.
• Footage from the earlier Gyro2 sup (20GYR2.BIN) still opens as before.

Validation

The automated suite passed 68 tests. Real footage from the new sup opened with every frame's data intact: 59.94p FHD (2,081 frames, 35 s) and 29.97p (189 frames), with no lost or missing samples. A take from the earlier sup still opens. The 29.97p take was also opened in DaVinci Resolve Studio 21 on macOS. Windows and Linux were not tested.

fpsup-v0.1.9

Fixes a DaVinci Resolve crash on Windows PCs that have both an NVIDIA card and an Intel integrated GPU.

The crash

With Resolve's GPU processing mode set to CUDA, Resolve crashed a few seconds after opening a timeline that used the plugin. Windows crash dumps placed the fault in the Intel Vulkan driver (igvk64.dll). To find the Vulkan GPU that matches the CUDA device, Gyroflow's core created a device on every Vulkan GPU, the Intel one included, and the older Intel driver crashed while doing so.

The fix

The plugin is now built from Gyroflow core with one change (ijigen/gyroflow, branch fpsup-core): only NVIDIA GPUs are checked, because a CUDA device is always an NVIDIA one. Intel and other GPUs are no longer touched on the CUDA path.

If you switched Resolve to OpenCL to avoid the crash, you can switch back to CUDA (Preferences > Memory and GPU > GPU processing mode), where playback is faster.

Validation

macOS behaviour is unchanged, because the changed code is only built for Windows and Linux. The fix has not yet been confirmed on a Windows PC that had the crash.

fpsup-v0.1.8

Gyro2 CinemaDNG footage can now be opened in the stock Gyroflow app directly from the fpSup plugin.

Workflow

1. In the DaVinci Resolve plugin, click Open in Gyroflow.
2. Make your changes in Gyroflow, then use the arrow beside Export and select Save project file.
3. Return to the plugin and click Reload project to apply your changes.

The plugin creates a persistent .gyroflow project containing the parsed motion samples, frame timing and lens data, and switches its Data source to that project. After reloading, the saved project supplies the stabilization data. To use the original camera data again, select a DNG frame with Browse. If you save the project to another path, select that project in the plugin with Browse.

Reload fixes

• Reload refreshes the saved project even when Embed .gyroflow data in plugin is enabled.
• Old cached data is discarded on reload, including while a render still holds the previous data.
• Embedded projects remain usable when their external project file is unavailable.

Validation and known limitation

The complete workflow was tested on macOS with DaVinci Resolve Studio 21 and stock Gyroflow 1.6.3, including saving a changed Smoothness value and reloading it into the plugin with embedded data enabled. The automated suite passed 59 tests, and a real clip round-trip preserved all 54,284 IMU samples, 649 frame timing entries and 649 lens records.

Gyroflow's DNG decoder can include sensor borders outside the active crop, causing a lens dimensions warning. This release transfers the telemetry and saved edits; the RAW dimensions mismatch still needs attention before relying on Gyroflow's rendered video output.

fpsup-v0.1.7

fpSup v0.1.7

fpsup-v0.1.6

fpSup v0.1.6: lens data follows a zoom within the take

The take's lens table is read when recording starts, so it holds the focal
length the take started at. When the frames' FocalLength tags differ within
a take (a zoom lens moved), a frame away from the starting focal length now
takes its own: the mount's focal length and that frame's WarpRectilinear
opcode. Before, a zoom of under a quarter kept the table's focal length and
a larger one kept the starting focal length's distortion.

A take at one focal length (a prime, or a zoom left alone) is unchanged: the
converted output of 11 recorded clips (LUMIX S 40mm F2 and a manual lens)
is byte-identical to v0.1.5.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fpsup-v0.1.5

fpSup v0.1.5: unsigned macOS installer package and Windows install sc…