FAQ & known limits

Does VSK do camera tracking?

Not yet - it’s the acknowledged P0 roadmap item (LiveLink integration). Today VSK is built for static or virtually-moved cameras: the physical cameras hold their framing and the CineCameras do the moving.

What platforms?

Windows, UE 5.8. Audio capture is WASAPI (Win64); the SDI path is Blackmagic DeckLink. The web remote works from any browser on the LAN, including phones and Macs.

Is the web remote secure?

It has no authentication by design - it’s a studio-LAN tool. Keep the network private, don’t expose port 8090 to the internet, and untick browser board editing before shows.

Why only stereo per SDI camera? Why no ASIO?

UE’s Blackmagic integration exposes stereo (or Surround8) embed - not 16-channel. Audio interfaces connect through WASAPI; ASIO isn’t supported, so use the interface’s WASAPI mode.

Multiple render machines?

VSK is single-machine today. Multi-machine/distributed rendering is on the roadmap (P2).

What does “Built · unverified” mean exactly?

Implemented, compiling, and smoke-tested through its API - but not yet confirmed by an operator on real studio hardware. VSK’s field log tracks every feature’s verification state, and this site’s badges mirror it. Currently in that state: the audio mixer, NDI in/out, ProRes recording, genlock/timecode, and the billboard Look-At modes.

Which settings persist but do nothing yet?

Pixel aspect ratio, Fill/Key alpha output, OCIO conversion, drop-frame timecode and per-input HDR - they’re stored and displayed, wired for a later pass, and flagged in Settings.