Hi there,
I have a very demanding client! We have Express+, with 12 x Mobotix cameras. I’m really hoping to deliver the following functionality;
- Use the mobile app to enable/disable recording on motion (normal operation would be recording on motion, ability to cease recording using a command from the app but still have live feeds)
- Use the mobile app to start/stop the mics on each camera (same as above, but for the mics)
- Use the mobile app to take each camera on and offline, no recordings, no live feed.
- Use mobile app to change from any other state to continuous recordings video/audio until further notice.
I have Express +, so I have setup some manual events that I can trigger from the app. I then setup some rules so that when the event is triggered it performs the ‘Start Feed’ when I use one event, and then ‘stop feed’ when I trigger another event. This appear to have no effect!
I’m really surprised that MS would not have this presumably quite straightforward functionality on their rules wizard. There is a ‘Start Recording’ pre-definded rule which seems to work, I trigger it and everything starts to record, then if I trigger another to perform a stop action it stops then returns to its original state of recording on motion.
Any advice would be really appreciated.
Thanks,
Tom
This is how XProtect works:
If you have one rule that starts feed and stops feed on a camera or microphone the rule will safely govern the camera.
If you have two rules that starts feed and stops feed on a camera or microphone the rule that starts feed will always win. -If one rule say start you can have multiple rules saying stop, the outcome will still be start.
Exact same applies to recording rules.
This means that you will have to have a good grasp of the rules in order to make sure a stop command is honered. You will have to look at the default rules ..
I hope you can see sense in how it is designed to work.
https://force.milestonesys.com/support/articles/en_US/How_To/About-start-and-stop-recording-in-MIP-SDK-c-library
If you have further need for discussion or guidance please ask the Support Community. (Developer Forum focus is on development using MIP SDK.)
Bo, thanks for your quick reply.
I originally posted on the regular forum and they directed me here. I have setup rules to ‘start feed’ but it appears to have no effect, I will go back to the other forum but could you explain what stop feed actually does?
Thanks
In a rule start feed starts feed and stop feed stops feed.
But! Stop feed only stops the feed that is started by the rule itself.
If rule #1 and rule #2 does start feed, and the rule #1 does stop feed, the the feed is still running as rule #2 has started it and never stopped it.
In short- stop feed reverses the start feed by the same rule but nothing else.
I believe my colleague thinks that what you describe will require development work. He might be right. I think you can setup the user to govern the feeds and the recording but only if you put it as a replacement for a default behavior that starts something.
If you have further continue on this thread. (I do not want to have you pushed back and forth, sorry for that.)