Download

Capture Studio for Windows

One recommended build at a time. Every package is immutable, published with its SHA-256, and kept in the version history so an earlier build can always be retrieved.

Reading the release feed…

Setup checklist

  1. 64-bit Windows 10/11 with the existing, working Envi camera installation. Keep the slit lamp on the bench, no patient.
  2. Close the original camera application and the MVS client so they release the camera.
  3. Verify the download: Get-FileHash .\Envi-Capture-Studio-<version>-win-x64.zip in PowerShell must match the SHA-256 above.
  4. Extract the ZIP to a new folder and run Envi.Acquisition.exe. No administrator rights and no separate .NET install are needed.
  5. If Windows SmartScreen warns, this is expected for an unsigned engineering build. Have IT review the checksum; do not disable protections.
  6. Find cameras → choose the Envi by model/serial → Connect. If the x64 MVS runtime is not found, see the runtime guide.
  7. Capture an OD/OS bench frame, then Export diagnostics and send a report from Device tools → Report a problem.

Readiness, honestly

Prototype readiness means the build starts, renders, saves synthetic frames and passes its regression checks on a Windows test machine. It does not mean the camera works.

Physical camera validation is a separate hardware test on the Envi bench: discovery, live frames, still capture, exposure/gain and shutter-controller input. The badge on the current build reflects only what has been recorded.

Known issues

Loading…

Version history

Release notes come from the published feed, not from this page.
Loading…
How releases are published and verified

Each release is a ZIP under /releases/<version>/ that is never overwritten. The publisher uploads the payload first, computes and records its SHA-256 and size, and only then updates /feed/versions.json and the small pointer /feed/app.json that the app and this page read. The pointer is served with Cache-Control: no-cache. After publishing, the published bytes are downloaded back through this hostname and re-hashed before the release is declared complete.

A hash proves the file you have is the file that was published; it does not prove who published it. Until a code-signing identity is established, treat this as an engineering build distributed inside the partnership.