Dear member,
Yes — in most professional deployments, basic Motion Detection should be disabled when using advanced analytics such as Line Crossing or Intrusion Detection.
Why?
Motion Detection is pixel-based analysis.
Line Crossing and Intrusion Detection are rule-based VCA analytics with target filtering (human/vehicle classification on supported models).
If Motion Detection remains enabled:
You will get duplicate triggers
Increase use of storage
Event logs become cluttered
False alarms increase (trees, rain, shadows, insects, etc.)
Best Practice for Event Recording/Perimeter Protection
1. Use VCA as the Primary Trigger
When Line Crossing or Intrusion is required:
Disable standard Motion Detection
Enable the required smart event only
Set the linkage under smart event to:
Trigger Recording
Notify Surveillance Center (if used)
Send Email (if required)
Audible Warning (if configured)
2. Enable Human/Vehicle Filtering
If the camera supports AcuSense or deep learning classification:
Enable “Human” and/or “Vehicle” detection
Disable “All Targets”
Set min and max sizes
Create multiple intrusion zones or line crossing when covering a large area with 1 camera
This significantly reduces false alarms.
