Filtering captures in iOS/iPadOS vs SecSpy Browser
Hi Ben, question about iOS/iPadOS app and the way it filters movie captures vs how the SecSpy Browser works:
In SecSpy browser, if for example there's a "human/vehicle moves" event captured in a continuous recording (even when motion recording is disabled), then if the browser filter is set to "human motion" or "all motion events", then the list of all continuous-record movies for a given date is filtered to show only the movies where those events occurred. (Note: I have "when any recording is happening" selected for Motion detection/classification/presence detection on all cameras)
But in the iPadOS app, if I choose "human" for the same date, it shows nothing. I can't seem to filter continuous recordings to see only motion events the same way I can in the SecSpy browser.
Is this a known issue?
Comments
-
This is a limitation of the web/iOS view.
In the Browser, if you have Continuous-Capture (CC) files, it is able to look inside those files and find all events and list them. But from web/iOS, it's a more straightforward listing of files.
The default recording setup (and the one that the vast majority of users prefer) is to use Motion-Capture (MC) recording, with one file created per event. Then you get equivalent functionality from web/iOS, because you can filter the files by event type.
One workaround here would be to enable both CC and MC, giving you the best of both words. If you are doing CC already, then adding MC won't affect your storage requirements much (a few percent).
-
Yes, I'm CC'ing and MC'ing. I just wasn't certain if this was a difference in features or a bug. The browser feature to filter by motion events/human events, etc is very useful and it's my goto way of quickly reviewing all motion events that occur independent of whether a motion capture was triggered. All cameras here CC 24/7, and then motion/action triggers are enabled during high-security times (away, sleep, etc). I find it very useful though to quickly scan through all detected motion in the Browser and would love to see that functionality migrate to the iPadOS version of the app at some point.
