VIGIVO FIELD GUIDE

Your first camera.
Your first useful rule.

A little preparation makes monitoring easier. Here is the path from a Windows PC to a rule you can review and trust.

Before you begin

• A Windows x64 PC. Windows 11 is recommended. The current app targets Windows 10 22H2 or newer; use an edition still supported by its vendor.
• Memory and storage. We suggest at least 8 GB RAM and enough free disk space for your chosen recording retention. Performance depends on your hardware, streams and analysis rate.
• A camera you are authorized to use. Have its RTSP stream address and separate camera username/password ready. ONVIF profile retrieval is available for supported devices.
• A suitable network. Confirm that the PC can reach the camera. Multicast discovery may not cross VLANs or isolated Wi-Fi networks.

CPU detection works without NVIDIA hardware. DirectML acceleration is optional and depends on compatible hardware and drivers. The packaged app does not require customers to install Python, Node.js, Docker or a development SDK.

1. Connect one camera

Follow the welcome wizard or choose Camera Management → Add RTSP camera. Enter the stream address and credentials separately. Use Test connection & preview to check the unsaved settings against a real decoded frame, then save with monitoring enabled.

Start with one camera at around two analysis frames per second. A live picture does not establish detection quality; review both the image and actual events before expanding.

2. Make the scene easy to review

Open Live Cameras, select a layout and confirm that frames are advancing. Adjust fit/fill for your scene. Source-audio preview starts muted and can lag the image because it uses complete buffered segments.

Draw an analysis privacy mask where needed. These masks do not redact original evidence recordings or their thumbnails. Configure masks on the camera itself if the recorded source must exclude an area.

3. Describe a specific rule

In AI Rule Studio, try “Notify me and record when a dog enters the garden.” Choose Interpret instruction, then review the object classes, actions, confidence and schedule. Select or draw the intended zone and save the rule.

The interpreter handles supported object and rule patterns. It does not determine intent, guilt or complex human behavior. Review every generated condition before activation.

4. Check a real event

Use Events & Alerts to review a genuine detection and its action outcomes. Adjust confidence, duration, cooldown and zones as needed. Simulate event is a labeled action test; it does not test the AI detector.

5. Review the recording

In Recordings, wait for a clip to finalize, then play or export it. Event recording preserves the original encoded source and optional source audio. Pre-event coverage depends on buffer warm-up and camera keyframes. Review each clip's status: partial or interrupted footage is different from a complete recording.

6. Set your operating preferences

Choose retention, storage limits, notification behavior, camera health alerts and the inference provider in Settings. The independent Windows service performs monitoring; desktop popups and sounds need the signed-in companion. Keep your PC powered, review available disk space and check camera health regularly.