That is up to you, but many of us would suggest getting used to BI and getting it to work first before jumping into the AI.
And then of course, depending on the cameras you have, the AI in that may be more than sufficient for your needs.
The camera AI is useful to many people, but BI has way more motion setting granularity than the cameras, and some people need that additional detail, especially if wanting AI for more than a car or person.
There isn't really a best practice because every field of view is different and use case and needs are different.
To many here, BI motion is more than adequate for what they do.
To many here, camera AI is more than adequate for what they do.
To many here, using the BI AI adds additional functionality that the above alone can not do.
It comes down to testing with each field of view and which one gives you the most consistent results.
If you decide to go with the camera AI, then set up the IVS rules within the camera and let it do its thing!
Go into the camera and set up smart plan with IVS, then go to the IVS screen and draw IVS rules (tripwire or intrusion box) and then select the AI you want it to trigger on (human or vehicle).
Then in BI, there are a few places you need to set this up in BI (assuming you already set up the IVS rules in the camera GUI):
In Camera configure setting check the box "Get ONVIF triggers".
Hit Find/Inspect on the camera setting to pull the coding for the triggers.
Go into Motion Setting and select the "Cameras digital input" box.
On the Alerts tab uncheck the Motions Zones tab (those are alerting you to any BI motion in those areas in Zones A thru H)
On the alerts tab set up how to be notified.
It has come to my attention that certain Dahua cameras come with built in AI that distinguishes between human & cars. I was unaware of this. Well, always saw the AI word used in the reviews but never really thought about it because I thought it was a Dahua NVR integration only. I am currently...
ipcamtalk.com
