I thought I’d post this in case someone else experiences it in the future.
The Problem...
On a cloned camera, I assigned an Action Set (a script) to Preset 25.
However 'Move to preset' 25 was not working on that cloned camera when it triggered.
Solution...
I noticed that Preset 25 was not ALSO defined on the clone master camera.
Once I also defined a matching Preset 25 on the clone master, everything worked.
I emailed Ken about this...
Question... Is it intentional that cloned cameras may not have their own presets?
I can see how this makes sense for Presets that are true camera ptz positions.
However, it is was unexpected behavior otherwise.
Here’s his reply...
Yes that's correct right now ... the cloned cameras will send PTZ commands to the parent camera for processing. This way they don't need their own PTZ threads and all PTZ commands to the camera are serialized.
I see how this is confusing however ... I will consider how to improve that.
The Problem...
On a cloned camera, I assigned an Action Set (a script) to Preset 25.
However 'Move to preset' 25 was not working on that cloned camera when it triggered.
Solution...
I noticed that Preset 25 was not ALSO defined on the clone master camera.
Once I also defined a matching Preset 25 on the clone master, everything worked.
I emailed Ken about this...
Question... Is it intentional that cloned cameras may not have their own presets?
I can see how this makes sense for Presets that are true camera ptz positions.
However, it is was unexpected behavior otherwise.
Here’s his reply...
Yes that's correct right now ... the cloned cameras will send PTZ commands to the parent camera for processing. This way they don't need their own PTZ threads and all PTZ commands to the camera are serialized.
I see how this is confusing however ... I will consider how to improve that.
