Saphere/Docs

Realtime

Stream a video source you already hold, and read the pulse waveform and the vitals as they are computed.

Realtime Measure is the continuous counterpart of Saphere Scan. Where the widget owns a container, walks a person through a thirty-second capture and hands you a result at the end, this one takes a video stream you already hold and measures it as it arrives — a pulse-waveform point per measured frame, and the vitals once a second, for as long as you keep the session open.

The realtime measurement chainA video stream you own is pushed by your client into one session; the analysis server cuts it into frames, finds the face, reads the pulse, and three streams come back — the pulse waveform, the breathing baseline and the vitals.YOURSVideo streamcamera, media server, fileYOUR CLIENTOne session, one streamopens a WebTransport sessiondeclares content and formatpushes the container as it comesreads what comes backSAPHEREAnalysis servercuts the frames, 30 a second at mostfinds the face, reads the pulsecomputes the vitalshr — pulse waveformone point per measured framebr — breathing waveformin bursts, once the window allowsvariables — vitalsonce a second, when the window allowsThree return streams on one session —each says its kind once, at its start.
One session carries the whole measurement: your client pushes the container, the server cuts it into frames, finds the face and reads the pulse, and three streams come back — each saying its kind once, at its start.

What this section documents

The wire protocol, and how to push a video stream into it. That is what a media server, a mobile capture pipeline or a recorded file replayed for validation needs — anything that holds the video and cannot run a browser module we provide.

You open one WebTransport session, declare in your address what the session will send, push your container as it comes, and read the three streams the server opens back. The wire protocol page carries the byte layout and a complete client; access tokens is how your server mints the credential the handshake consumes.

Alpha

Realtime Measure is alpha. It is stable enough to build against, and we will tell you before anything moves — but expect it to move, and talk to us before you build: a server-to-server integration is not something you switch on alone.

Which one to use

Saphere ScanRealtime Measure
What you geta widget with its own screensa measurement service you stream to
The videothe widget asks for the camerayou already hold it
The capturethirty seconds, then a resultcontinuous, for as long as you keep the session
The resultonce, at the enda waveform point per measured frame, the vitals every second
Consent and guidanceincluded, and customisableyours to write
The integrationone script taga WebTransport client, written against the wire protocol

The deciding question is rarely the measurement: it is whether you already own the video. A teleconsultation that is already carrying a face has a stream, and a journey around it — Realtime Measure joins that. A form on a website has neither, and Saphere Scan brings both.

Access tokens

One session, one token, minted by your server and consumed by the handshake.

Wire protocol

For integrations that stream from a server rather than a browser: the transport, the streams, and the byte layout.