When should Motion/Human/Vehicle events show up in Browser

Hello all.

How "realtime" (or not) should event-tags be searchable in Browser? It looks like I can browse by tag for yesterday's videos (I have it set to one file/camera/day for continuous and motion captures). But, when I get an email alert that SecuritySpy detected a human and I go to browser and search for all motion events or all human tags, it finds none. Even several hours after event. Is this normal? Does the browser scan/search not work on "UNF" video files? Do I have to switch to one file per event (annoying for file management).

Or am I doing something wrong? I am running five cameras on Mac Mini (M1) with very fast SSD external storage. No apparent stress on CPU/GPU/HD/Memory-- in case that is relevant.

Thanks in advance for any thoughts!

Comments

  • These should be pretty much real time. However, if the Browser is already open from before, then the information it has may be a bit out of date and you'll need to do a rescan (this option is available from the Browser menu that you will see at the top of the screen when the browser is open, or Command-Shift-R on the keyboard). Does this do it?

  • ChrisNicholson
    edited December 2021

    No. Rescan doesn't seem to help.

    Events show up as ticks in the timeline pretty quickly, but not in the text list of events in the lower-left pane. It says "No Events Found" (with a message about meta data). This is about three hours after first event from today. Everything from yesterday shows up in the event list.

    I like the feature of being able to quickly see the text list of events (tagged with human / vehicle), but updates seems to be lagged by several hours. That's why I speculated that maybe the metadata isn't processed for "UNF" files, so happens at midnight (if set to one file per day). Just guessing.

    I just quit/restart (which I think creates a new daily file for each camera) and this morning's events now show up. So I'm doubling down on my theory....

  • Hi @ChrisNicholson, apologies for the delay on this. I have tracked this back to a bug, which should now be fixed in the latest beta version of SecuritySpy (currently 5.4b5). Could you please download and install this version, and let me know if the problem is fixed. Many thanks.