To answer the question RE: Tour & IVS, the answer is YES
Specifically as a tour is calling a set preset, each preset can have its own IVS rules and on a PTZ those IVS/Deep IVS rules can feature Alarm Track (Auto Track) time. Therefore if you called preset 2 on a tour when the PTZ arrives at preset 2 it will then look for anything that activates IVS rules configured within that preset. If something trips the IVS rule within the preset (and crucially before the time for the tour to move onto another preset) then Auto Tracking would kick in (if configured and supported) and capture/track the target. Therefore when combining both make sure you leave enough headroom between touring to another preset AND Alarm Track time required per location.
Another thing I am an advocate of and have helped others configure is IVS based Auto Track equivalent or what I also call nested IVS rules. This is where you configure 1 view (say an overview FOV) to activate a PTZ preset when an IVS rule is tripped, then within that 2nd preset have other IVS rules to call further presets/movement of camera OR Auto Tracking. This allows for a much more crisp approach to PTZ tracking often beating out Auto Tracking for accuracy and allows PTZ;s that do NOT have Auto Tracking to benefit from a pseudo tracking setup. Just remember when using nested IVS rules to set IDLE time back to your Overview Preset (in this example).
Then finally the other options available are PTZ activation called by fixed cams as others have mentioned. You need an NVR platform (standalone or BI etc) to perform this but then you get what I call the Spotter & Overwatch setup. This is where your fixed cam spots and calls your overwatch (PTZ) to a specific preset ready to capture the target as it moves into view. I do this with triangulated and larger configs and works really well but you do have to take your time the more complex you go
HTH
Specifically as a tour is calling a set preset, each preset can have its own IVS rules and on a PTZ those IVS/Deep IVS rules can feature Alarm Track (Auto Track) time. Therefore if you called preset 2 on a tour when the PTZ arrives at preset 2 it will then look for anything that activates IVS rules configured within that preset. If something trips the IVS rule within the preset (and crucially before the time for the tour to move onto another preset) then Auto Tracking would kick in (if configured and supported) and capture/track the target. Therefore when combining both make sure you leave enough headroom between touring to another preset AND Alarm Track time required per location.
Another thing I am an advocate of and have helped others configure is IVS based Auto Track equivalent or what I also call nested IVS rules. This is where you configure 1 view (say an overview FOV) to activate a PTZ preset when an IVS rule is tripped, then within that 2nd preset have other IVS rules to call further presets/movement of camera OR Auto Tracking. This allows for a much more crisp approach to PTZ tracking often beating out Auto Tracking for accuracy and allows PTZ;s that do NOT have Auto Tracking to benefit from a pseudo tracking setup. Just remember when using nested IVS rules to set IDLE time back to your Overview Preset (in this example).
Then finally the other options available are PTZ activation called by fixed cams as others have mentioned. You need an NVR platform (standalone or BI etc) to perform this but then you get what I call the Spotter & Overwatch setup. This is where your fixed cam spots and calls your overwatch (PTZ) to a specific preset ready to capture the target as it moves into view. I do this with triangulated and larger configs and works really well but you do have to take your time the more complex you go
HTH
And that's what I "thought" not being clear in the Dahua documentation: IVS rules on different preset positions is something "unknown", and let's face it, also very difficult to accomplish.
What about simple Motion Detection? I see in your video above "Video Detection" (second menu higher than Smart Plan) - are those MD setup's per preset?
Thank you!
CC