The supervision browser package is session-first. The public API should make the common path
easy while keeping renderer internals replaceable.
This guide describes the current package boundary. It is intentionally smaller than the implementation.
Today, supervision is the browser package. It is built on a
platform-neutral internal core package, but browser users should continue to
import from supervision:
import { createMediaSession } from "supervision";
Install the current browser release with npm install supervision. See
Application Integration for the supported
consumer workflow.
The web video engine subpaths are included in supervision starting with the 0.2 release series.
The split keeps detections, timelines, styles, retention policies, source composition, and picking contracts reusable without making Pixi, Mediabunny, workers, or browser storage part of those core concepts.
Start here for normal application code:
createMediaSession()MediaSessionMediaSessionOptionsMediaSessionStateMediaSessionStatusMediaSessionActivityMediaFrameClock and optional session.frameClock / renderer.frameClock
for exact indexed timing. The clock is null for unindexed media; its
frameCount, firstTimestamp, endTimestamp, duration, timeAt,
durationAt, and indexAtOrBefore members use presentation time rather
than an assumed frame rate;MediaFrameNavigation and optional session.frameNavigation /
renderer.frameNavigation for exact indexed moves and latest-wins scrubs on
push-presented indexed sources. Use the ordinary time controls when it is
null;session.setDisplay() / renderer.setDisplay() to resize existing
push-presented output without recreating the source or session. Web video
engine sources expose it when configured with a display-box decode strategy;MediaSession: play, pause, seek, frame stepping,
playback rate, and current-presentation refresh;session.captureFrame() when a host needs an encoded JPEG Blob for the
raw media frame currently presented by the renderer. The result includes that
frame's media timestamp and dimensions; it never exposes a renderer canvas
or composited annotations;DetectionFrameDetectionFrame.coordinateSpace when detections were produced against a
differently sized copy of the media; the renderer projects vector geometry
into media space for every detection input, so static frames, caller-owned
sources, composite sources, and appended frames all behave the same. A
composite composes children that were each inferred at a different size, and
every child is projected from its own space before compositionMediaSessionOptions.depth (a DepthMap, or a depth.json
manifest the session fetches and decodes, for a still image or a clip over
video media), and the depth annotation renderer. Depth is its own channel
beside detections, never a DetectionFrame field, and a map is stretched
over the media rectangle rather than projected by coordinateSpace. Which
media draws which depth, and what plays, is in
Depth mapsDetectionDetection.trackerId for identity assigned by a tracking post-processorRectDetectionMaskPolygonGeometryOrientedBoxGeometryPolylineGeometryKeypointGeometryBaseBoxStyleBoxShapeBaseMaskStyleBaseOrientedBoxStyleBasePolygonStyleBasePolylineStyleBaseKeypointStyleBaseLabelStyleBasePercentageBarStylePercentageBarPlacementBaseInteractionStyleBaseFocusStyleannotationRenderersannotationRendererKindsAnnotationRendererAnnotationRendererKindRegionAnnotationRendererdetectionPostProcessorscreateDetectionPostProcessingPipeline()TrackingGeometryDetectionPostProcessingModeprepareMedia()prepareMediaProgressively()probeMedia()MediaErrorKind and MediaSourceError for branching on media failuresThese are the concepts a user should be able to understand without knowing how Pixi, Mediabunny, workers, or prepared mask artifacts are wired internally.
MediaRendererPresentation.renderers is the unified presentation surface for
annotation visualization. An annotation renderer consumes semantic detections
and contributes to the renderer-owned scene. The built-ins retain the
established draw order and backend paths for masks, boxes, vectors, and labels.
MediaRendererPresentation.annotationAntialiasing enables smoothing for all
annotation edges, including focus and interaction, without filtering video
frames. Use true for FXAA at output density or 2 for FXAA captured at twice
that density in each dimension. It smooths label
backgrounds while keeping text sharp. Separated label runs share captures;
overlaps split captures to preserve blending and draw order. It defaults to
false and can change in an existing
session. See
Presentation Styles.
import { annotationRenderers, BaseBoxStyle, BaseLabelStyle } from "supervision";
session.setPresentation({
renderers: [
annotationRenderers.box({
style: new BaseBoxStyle({
stroke: { color: 0x8b5cf6, width: 2 },
}),
}),
annotationRenderers.label({
style: new BaseLabelStyle(),
}),
],
});
The current built-ins are box, box-corners, depth, ellipse, heatmap, marker, mask,
maskHalo, orientedBox, polygon, polyline, keypoints, label, percentageBar, and
the multi-instance region renderer for asset overlays and current-frame media
crops; heatmap and depth also support multiple instances with distinct ids;
annotationRendererKinds enumerates that vocabulary and
AnnotationRendererKind names it in application code. When supplied, the list
is authoritative: omitted built-ins are
disabled, and renderers: [] disables every built-in layer. For a listed
renderer, an explicit style wins; otherwise its matching legacy style field
provides the default. A source-specific override can refine a selected layer,
but cannot re-enable an omitted layer. The existing boxStyle, maskStyle,
and related presentation fields remain supported for compatibility and
source-specific style overrides. New global presentation code should prefer
the renderer list.
region carries its target, source, anchor, transform, and composition
configuration directly because it does not lower into one of the legacy style
fields. Its browser backend supports URL-based assets and crops of the existing
renderer-owned media texture. Media crops may request exact mask coverage,
which reuses the renderer's prepared GPU ID-mask artifact, or polygon coverage
for canonical closed polygons. Asset transforms may use an
explicit media- or screen-space size; screen-space assets stay the same visible
size across differently sized detections and viewport zoom. Multiple region,
heatmap, or depth descriptors may coexist when each has a unique id.
Media sources may also request bounded blur or pixelate effects through
source.effect; those semantic settings stay independent of the browser filter
implementation and operate on the renderer-owned current frame.
Do not pass Pixi display objects or custom drawing callbacks: the public API
describes semantic renderer configuration while the browser backend owns
composition and resource lifetime.
These exports are public because serious integrations need them, but they are not the first thing most users should reach for:
createMediaRenderer() for lower-level renderer ownership;createMediaStreamRendererSource() for adapting a browser MediaStream
without adding a second visible video layer; its bounded snapshot queue is
latest-frame-wins, so a temporarily slow renderer resumes at the live edge
instead of replaying stale frames. Its onPresentedFrame option reports
MediaStreamPresentedFrame metadata — media time plus, where the browser
supplies them, RTP timestamp, dimensions, presentation time, and expected
display time — so a host can correlate transport-side results with what is on
screen without opening a second hidden video. No DOM element or vendor object
crosses that boundary, and every field beyond mediaTime is optional;createWebVideoEngineMediaRendererSource() and openWebVideoEngineMediaSource()
for video presented by the web video engine, which owns the playhead and
hands each selected frame to the host. The renderer atomically composites
annotations from that frame's identity and acknowledges it once displayed.
Its source is a URL or a Blob, because it reads the video twice: once for
the frames it presents, and once for the thumbnails and single-frame grabs
its sample sink answers. A ReadableStream can be read only once, so pass
one to WebVideoEngine directly instead.
Both are also exported from supervision/web-video-engine, alongside the
engine's own types; the subpath and the root give the same two functions. The
source types are among those engine types: UrlVideoSource,
BlobVideoSource, and the SourceKind values that build one are imported
from supervision/web-video-engine, not from the package root. Importing the
subpath does not evaluate the root entry, so an application that wants only
the video engine does not run the renderer graph. The engine is loaded
dynamically at the moment one of these opens a source, so an application that
never opens one pays nothing in its bundle to import supervision. Pass
display to size the decode to the box the frames are painted into; without
it they decode at the source's full resolution however small that box is.
Under this source the renderer also answers getRenderCount() and
getPreparedAnnotationWindow(), which report null for pulled media that
plays. A still image renders on change too, so it answers
getRenderCount();DetectionFrameSource for caller-owned range loading. loadFrames receives
optional DetectionFrameLoadOptions; a source that returns its own frames
unchanged can ignore it, while a source that flattens child frames uses
coordinateSpace to project each child before composing. A
WritableDetectionFrameSource is accepted anywhere a session accepts
detections.source or a detections.sources[].source; the session borrows
that source and never disposes it. Write through the session when it should
refresh the visible result, or call session.refresh() after a direct source
mutation. detections.autoRefresh: false leaves every redraw to the host;LiveMediaSession, the shape createMediaSession() returns. It guarantees
appendLiveDetectionFrame() and finalizeDetectionCoverage(), which stay
optional on MediaSession so controllers and test doubles written against the
previous shape remain assignable;WritableDetectionFrameSource and createWritableDetectionFrameSource() for
streaming inference ingestion. appendLiveFrame() and finalizeCoverage()
are optional members of WritableDetectionFrameSource, so a source written
before they existed still satisfies the interface;
createWritableDetectionFrameSource() returns the narrower
LiveWritableDetectionFrameSource, which requires both, and the session
surfaces them as session.appendLiveDetectionFrame() and
session.finalizeDetectionCoverage();projectDetectionFrame(), projectDetectionFrames(), and
createProjectedDetectionFrameSource() when a host wants the same
coordinate-space projection outside a session;detections.sources, MediaSessionDetectionSourceOptions, and
createCompositeDetectionFrameSource() for composing model predictions,
draft annotations, review overlays, or other app-owned detection streams over
one media item;session.setRenderQuality() for runtime DPR/quality changes without
rebuilding the media session. The renderer synchronizes the canvas,
display-sized masks, and display-box video output when quality or container
dimensions change. Native and capped video strategies, and masks configured
without a display box, keep their own resolution policy;session.setDepth() to swap or remove a depth map or manifest without
reopening the media, renderer.getActiveDepth() for the map on screen, readDepthAt()
for the stored value, disparity, metres, and confidence under a media point,
computeDepthPercentileRange() to lock a frame's automatic colour range,
depthColormapColors() for a legend in the renderer's own colours, and
parseDepthManifest() to validate the depth.json a producer writes;RenderPreparationMode.Auto uses the package's embedded Blob worker when the
browser supports it and falls back to main-thread preparation after a worker
failure. RenderPreparationMode.Worker is strict: worker creation or runtime
failures reject instead of silently changing execution modes.
Hosts whose Content Security Policy blocks Blob workers may supply a
RenderPreparationWorkerFactory and host the self-contained script exported at
supervision/render-preparation-worker. That subpath is a deployment asset,
not a JavaScript API; its message protocol is intentionally internal.
Tracking uses the same deployment pattern. The self-contained script at
supervision/detection-post-processing-worker can be hosted by strict-CSP
applications through a DetectionPostProcessingWorkerFactory; its protocol is
also private.
A producer that streams results into a session has four supported contracts:
session.appendDetectionFrames() writes a batch. Frames that declare
coordinateSpace are normalized into media space before storage; rectangles,
polygons, oriented boxes, polylines, and keypoints scale, while masks keep
their own intrinsic dimensions and are never scaled twice.
session.appendLiveDetectionFrame() writes the newest result for a live
stream. It stays active until the next live frame supersedes it, at which
point the previous frame is closed at the new frame's mediaTime. At most two
frames are written per call, so append cost does not grow with retained
history. Tune the open-ended hold with
detections.appendable.live.holdSeconds (default 60 seconds).
Live writes are serialized inside the source and the newest causal result wins: concurrent appends are applied in call order, and a result older than the newest accepted live frame is dropped rather than reopening coverage the source already closed. A repeat of the current frame's identity is treated as a revision and replaces it. Because the hold is a placeholder for "still current" rather than covered data, retention windows are measured against the producer's real coverage, not against the hold.
session.finalizeDetectionCoverage(endTime?) closes the last frame at the
end of media, defaulting to the renderer's reported duration. It sets that
frame's exclusive end to the requested time, extending a finite frame whose
container declared a duration past the last decoded sample, or shortening a
live frame that is still held open. Without it, reported availability either
leaves a terminal sliver uncovered or claims time past the end of media. It is
idempotent.
session.refresh() still redraws on demand. By default the session also
redraws itself when a write actually changed the frame selected for the
displayed time. Live writes, batch writes, and coverage finalization all use
the same rule: a result the source dropped as stale changes nothing, and a
frame whose interval does not contain the displayed time cannot change what
is on screen. A frame written without an
endTime stays selected until a later frame supersedes it, so one appended
behind the displayed time still redraws, and rewriting the most recent one
with a real end redraws for the time it stops covering. Requests arriving during a redraw
collapse into a single follow-up. Set detections.autoRefresh: false to own
every redraw.
Retention windows evict in place when the cold store implements pruneFrames
(the built-in memory store does), so a long-running stream does not reload and
rewrite everything it keeps on every append. pruneFrames rejects a retention
floor that is not finite and non-negative rather than silently emptying a
dataset. Stores without that hook keep working through a reload-and-replace
fallback.
Media failures carry a stable MediaErrorKind instead of asking applications to
match decoder, demuxer, or container message text:
import { MediaErrorKind, getMediaErrorKind } from "supervision";
const state = session.getState();
if (state.renderer?.source.errorKind === MediaErrorKind.UnsupportedFormat) {
// Application-owned, localized copy.
}
MediaSourceError preserves the originating failure on cause. Public media
sources — finite video, MediaStream, and image sources — wrap what they throw,
and getMediaErrorKind() classifies any caught value, including one that never
passed through a source boundary. Unrecognized failures stay representable as
MediaErrorKind.Unknown, and new kinds may be added over time, so treat unknown
values like Unknown. MediaSourceState.errorKind is optional, so state
fixtures written before it existed keep type-checking; read it as
state.renderer?.source.errorKind ?? null.
Finite video sources present a zero-based timeline. Media trimmed through an
edit list carries decodable samples ahead of presentation time zero; those are
not presented, and the session reports firstTimestamp as the presentation
start rather than the negative decode start.
When a detection source uses MediaStart conversion, renderer time is
detectionTime + firstTimestamp; source coverage remains in detection-timeline
coordinates.
Annotation editing is a supported advanced API at the dedicated subpath:
import {
createAnnotationEditingEngine,
createEditableAnnotationFrameSession,
createMaskBrushEditor,
} from "supervision/editing";
The host creates and owns the editing engine, commits semantic detections to
its own source or persistence layer, and owns undo/redo. Pass the engine through
createMediaSession({ renderer: { editingEngine } }) so the session routes
pointer gestures and renders previews. maskBrush and previewOverlay use the
same session renderer options. The renderer never writes application data.
With an editing engine, retained boxes, polygons, polylines, keypoints, and
shape decorations share detection order: higher Detection.zIndex is in front;
missing values use the detection's frame index, and equal values follow frame
order. Masks remain a prepared fill layer below this geometry, and labels and
interaction overlays stay above it. Without an editing engine, the dense renderer
keeps its separate geometry layers; zIndex orders detections within each layer.
Set interaction.preferTopmost: true to pick that editable stack rather than
prefer smaller shapes or subtargets in other detections. The same option is
available to pickDetectionAtPoint. It interprets rectangles accompanying
paths or masks as bounds, so they do not create a second box hit target; mask
fills stay below vector geometry. Keypoints and edges retain priority within
the chosen detection. Leave this option unset for the default smallest-object
policy or when accompanying rectangles are independent box targets.
Enable interaction.multiSelect for Shift-click selection toggles and
drag-selection from empty space. onSelectionChange reports the full ordered
selection; onSelect reports its primary pick. Shift-clicking a detection in
Select mode changes selection without starting a move. Shift-click and the
secondary button still delete an editable polygon/polyline vertex when its
selected vertex handle is hit; active creation tools keep their gesture priority.
Restore host-owned selections with
session.renderer.setSelectedDetection({ detectionIds: selectedIds }).
Duplicate ids are ignored, missing or hidden detections are excluded, and the
last valid id is the primary pick returned by the method. An empty list clears
selection. detectionIds takes precedence over detectionId or
detectionIndex when supplied together; singular selectors continue to select
one detection. Use the full list rather than restoring only the primary pick
after a refresh or application state update.
Synchronizing the same creation tool is idempotent: setCreationTool(null)
keeps a selection drag alive when the engine is already in Select mode. To
abort a gesture explicitly, call engine.cancel().
Route Undo to engine.undoCreation() before committed history. It removes one
vertex from an active multi-click draft and returns true, including when the
last vertex cancels the draft and releases its pointer. It never commits a
preview. A false result means no multi-click draft owns Undo; it does not
consume or cancel an active box, freehand, move, or resize gesture. Consult
committed history only when engine.getState().kind is
AnnotationGestureStateKind.Idle, cancelling an active gesture explicitly
first if needed. Escape, tool changes, and media changes still cancel through
engine.cancel(); draft vertices never enter persisted history.
createAnnotationEditingEngine() returns a DraftUndoAnnotationEditingEngine
that guarantees undoCreation(). The method is optional on the broader
AnnotationEditingEngine interface so existing custom engines remain
compatible; hosts using a custom engine check that capability before routing
draft Undo to it.
Browser-routed box creation, movement, and resizing stay inside the natural
media dimensions in both previews and commits. Moving a box preserves its size
when it fits the media; a previously oversized box is fitted to the media on
edit. Resizing can cross the opposite edge while keeping the fixed anchor inside
the media. The renderer supplies AnnotationPointerInput.mediaDimensions; callers
routing input directly can supply the same optional dimensions to enable these
constraints, or omit them for unbounded geometry editing.
Creation tools may provide onRejected() to handle a completed drag or
freehand stroke that produced no committed detection. The engine calls it
after returning to idle. Escape, tool changes, and explicit cancellation do
not call it, so hosts can clear selection on an empty drawing click without
interpreting every cancellation as a click.
The generated API reference has a separate Editing module for this entrypoint.
Rect is center-based: x and y are the media-pixel center, while width
and height are its extent. TopLeftRect is only for explicit canvas/layout
boundaries. There is no legacy top-left rectangle mode. Rect also stays
axis-aligned: it never gains a rotation field. A rotated or otherwise
non-axis-aligned box is a separate OrientedBoxGeometry on
Detection.orientedBox, four explicit media-pixel vertices ordered clockwise
from the box's own top-left corner. Nothing in supervision-js derives an
oriented box from a mask or a plain rect; a producer that only has one of
those computes the quadrilateral itself.
Advanced APIs should remain renderer-neutral. They may expose timing, diagnostics, and data-flow contracts, but they should not expose Pixi containers, textures, shaders, or Mediabunny objects.
These are implementation details, even when they are important to performance:
./react entrypoint.Prepared artifacts are runtime representations. Detections remain semantic data. Apps should feed detections and styles into a session, not construct renderer artifacts directly.
React integration should be a separate thin adapter later. It should create and
destroy vanilla MediaSession instances, subscribe to session state, and pass
props into session.setPresentation() or session options.
It should not own media decoding, media timing, frame stepping, render loops,
detection buffering, inference ingestion, worker orchestration, or Pixi
composition. Timeline UI should subscribe to session state and read
state.renderer?.presentedTime for the displayed timestamp, then call session
navigation methods. renderer.onFrame is a per-sample diagnostic callback for
pulled renderers, not a provider-independent display clock.
The browser package remains vanilla TypeScript/JavaScript. React wrappers should
wrap MediaSession; they should not shape media timing, rendering, buffering,
or prepared artifact internals.
React Native support is experimental and private. The current mobile package depends on the platform-neutral core concepts, not on the browser package. Pixi, Mediabunny, DOM APIs, browser workers, and IndexedDB remain browser implementation details.
The private package now has a generic createMediaSession() core, a
package-owned MediaSessionView and useMediaSession() hook at
supervision-js-react-native/react, and platform adapter subpaths. These are
mobile experiments, not exports from supervision-js and not part of the
stable browser-package promise.
Mobile apps can feed detections from on-device inference engines, but inference is outside the rendering package boundary. The library renders and interacts with detections regardless of how they were produced.
The experimental iOS saved-video path is analysis-paced: it processes each
decoded frame as quickly as inference permits rather than trying to match wall
clock playback. createReactNativeVideoFileSession() presents the same
MediaSession controls and state surface as the generic path, while keeping
its native decoder, worklet runtime, and Skia resources private to the package.
Pause, play/resume, and stop are available; seeking is intentionally
unsupported until native decoding can reposition accurately. The older
createReactNativeVideoSession() name remains a deprecated forwarding alias.
Saved-video decoding on Android is implemented as an experimental
Nitro/C++ source backed by AMediaExtractor and AMediaCodec, delivering an
API-26+ RGBA AHardwareBuffer to the existing ExecuTorch and Skia consumers
with explicit timestamp and release ownership. It requires Android API 26;
older hosts report the stable android-video-file-source-requires-api-26
reason, and hosts without the native module keep the usual fallback
diagnostics. Rotated videos (portrait phone recordings with a
rotation-degrees track metadata) are rejected with an explicit error until
the GPU rotation pass lands. The pipeline is validated end-to-end on an
emulator; physical-device validation and performance numbers are still pending.
React Native currently shares editing geometry, picking, and gesture semantics
through createReactNativeAnnotationGestureAdapter. Native hosts own drawing
editing affordances from AnnotationOverlayStyle until a native overlay
renderer is introduced.
The experimental ./react/live-inference entrypoint owns the live VisionCamera
worklet through useReactNativeLiveInference(); applications provide model
runners and serializable configuration, not frame callbacks. This keeps the
generic ./react entry usable without the optional Worklets peer.
The package is pre-1.0. The strongest compatibility promise is around the session-first model:
See Migrating to 0.2 for source changes required by the release, including interaction presentation options.
When adding exports, prefer one of these outcomes:
Pass renderer: { pixelInspection: { minScale: 3 } } to createMediaSession()
(or pixelInspection to createMediaRenderer()) to display distinct source
pixels at high zoom. The threshold is the actual media-to-screen scale in CSS
pixels per natural media pixel, including fit and user zoom; it is independent
of display pixel ratio. A positive, finite minScale is required.
Media is smoothly sampled below the threshold, and distinct pixels are restored
when zoom, container resizing, or a new frame crosses it. This policy affects
only media display: annotations keep their configured styles, and captureFrame()
still returns the presented source pixels. Brightness/contrast adjustments retain
the configured renderer resolution, including on Retina displays. Omit the option for smooth sampling
at every zoom.
renderer.setDisplayAdjustments({ brightness, contrast, gamma, autoContrast })
changes only media display. Brightness, contrast and gamma default to 1; gamma
above 1 brightens midtones. For still images, autoContrast: true applies
Contrast Limited Adaptive Histogram Equalization (CLAHE) instead of manual
contrast. Brightness and gamma remain active. Auto contrast is ignored for video;
passing an empty object restores the unadjusted display. Source pixels and
annotation styles are unchanged.
renderer.setViewportTransform({ scale, x, y }) applies an exact transform in
natural media pixels and container-relative CSS pixels. Explicit updates work
while the viewport is locked and can restore scales outside the ordinary gesture
zoom range. setViewportLocked(true) blocks pointer pan/zoom; toolbar resets and
restored host state remain available. After unlocking, zoom gestures can move a
restored scale gradually toward the ordinary range without jumping to its bounds.