OpenOSV 0.6.4

OpenOSV 0.6.4: VEGAS extension compatibility, Avata 360 stabilisation, Source Settings live sync and 8K exports

Fixes for all four open reports across VEGAS Pro, DaVinci Resolve and Premiere Pro (#7, #8, #9, #10).

What's fixed

• Third-party VEGAS Pro extensions such as Vegasaur no longer fail with E_NOINTERFACE (IVegasCOM / IDockWindow) when OpenOSV is installed (#10). WinForms' default WindowsFormsSynchronizationContext.AutoInstall replaces the UI thread's SynchronizationContext.Current on Control construction and reverts it to a plain System.Threading.SynchronizationContext when a modal dialog loop exits, stranding STA COM marshaling for other extensions in the process. OpenOSV now pins the UI SynchronizationContext with AutoInstall = false across initialization, command callbacks and modal dialogs.
• Changing a control in the OpenOSV Source Settings effect updates the live clip and exports immediately, including when returning a control to its default (#9). All value controls in OpenOSVSourceSettings.aex are now supervised and publish the translated PrefsBlob synchronously to the importer's live instances and direct-GPU engine via OsvEngine_PublishSourceSettings before Premiere re-instantiates the effect or opens a second importer instance for export.
• 8K 50 fps exports and seam analysis no longer exhaust NVDEC's VRAM cache slots and fall back to software decoding (#8, #9). Automatic VRAM budgets now reserve at least four dual-lens cache slots when free device memory allows, and ImporterInstance::anchorPairLocked releases older cached analysis frame leases before retrying when all slots are pinned by multi-bucket lookahead.
• OpenOSV Source in DaVinci Resolve now uses the NVDEC + CUDA own-GPU pipeline by default (#7, #8, #9). Resolve's OpenFX generator host hands CPU output buffers even on CUDA timelines; enabling the own-GPU path for HostProfile::Resolve keeps decoding, stitching and reframing on the GPU and downloads only the finished output window (11.8x faster at 1080p and 4.6x faster at 4K on RTX 5090).
• Stabilisation now works on DJI Avata 360 clips (#7). The Avata 360's IMU records the attitude of the aircraft frame while its lens extrinsics sit in the camera body frame (productMount(Avata360)^T); AttitudeTrack::build now post-multiplies the stored rig-axes quaternion by productMount(schema)^T, attitudeReadingVerified(Avata360) is enabled, stabilizationBodyFromWorld applies the mount across all five stabilisation modes, and CalibrationSelector::choose counts native_refine_far as a native calibration set.

Good to know

• .LRF is not supported — only .OSV. The camera's low-resolution .LRF files are not a supported workflow. Always work from the .OSV.
• Drone / airborne Osmo 360 & Avata 360 settings (#8): For an Osmo 360 hanging under a drone or an Avata 360 in flight, use Stabilisation: Smooth + Horizon Lock (or Horizon Lock to keep the aircraft's yaw while levelling pitch and roll; high-frequency prop/motor vibration above 12 Hz is automatically filtered out of the gyro track), Parallax Grid: Steady (or Auto), and Hide Mount: Auto (or Off if the drone body sits near the seam and you want full lens overlap).

How to update

Close your editor, unzip the zip for it and double-click Install.cmd. Premiere users: launch it once holding Shift.

Downloads

• OpenOSV-0.6.4-premiere-windows-x64.zip: Premiere Pro
• OpenOSV-0.6.4-resolve-windows-x64.zip: DaVinci Resolve (preview)
• OpenOSV-0.6.4-vegas-windows-x64.zip: VEGAS Pro 17.0 (experimental)

ffmpeg-9.0.1-source.tar.gz and ffmpeg-9.0.1-vcpkg-port.zip are the source of the FFmpeg build the zips ship (LGPL-2.1).

SHA-256

d7def9561dfef9292f5b522422880c4308b9830b0dc14c87c5733416b626a46c *OpenOSV-0.6.4-premiere-windows-x64.zip
815b4a6784d66f5e1dc063660d52b81ca220ea097a12007c24873b5b3505502a *OpenOSV-0.6.4-resolve-windows-x64.zip
2a2bf98c6acd8af05a065102b70b48c4bacd3808bee807064c40f568d521f88f *OpenOSV-0.6.4-vegas-windows-x64.zip