Pre-Trigger Buffer with Sentry

BlueWave

Getting the hang of it
Jan 12, 2018
69
38
Small observation I've noticed is that if you have your pre-trigger buffer set high (I had mine at 5 seconds) that when it sends the alert to Sentry for processing it seems to send some of the first frames in the alert which could very likely be nothing if the subject is out of frame during the pre-trigger buffer time.

When I lowered my pre-trigger buffer down to about 1 second that seemed to resolve the issue at the expense of possibly losing some video due to lag, make times....etc.
 
I run 5 seconds prebuffer on all my cameras. If I go out my front door quickly and off the side of the porch I am only in camera frame 2 seconds. Sentry texted an image of me right in the middle of the camera view.

Not sure exactly what sentry is using for analyses. The only place I've seen any option about including pretrigger images is in configuring email alerts where you can select or disable to include pretrigger image.
 
Small observation I've noticed is that if you have your pre-trigger buffer set high (I had mine at 5 seconds) that when it sends the alert to Sentry for processing it seems to send some of the first frames in the alert which could very likely be nothing if the subject is out of frame during the pre-trigger buffer time.

When I lowered my pre-trigger buffer down to about 1 second that seemed to resolve the issue at the expense of possibly losing some video due to lag, make times....etc.
Make sure your I frame interval matches your FPS. Blue Iris does not begin recording until a new i frame is sent when using direct to disc
 
  • Like
Reactions: TXgolfer
Make sure your I frame interval matches your FPS. Blue Iris does not begin recording until a new i frame is sent when using direct to disc

I have set Blue Iris to 15fps per the "Optimizing CPU" page since I have 16 cameras... is there another setting for "i frame" intervals?
 
Does the pre-trigger time have an effect? I have seen this also. My i-frames all match my frame rates at 15.
 
Does the pre-trigger time have an effect? I have seen this also. My i-frames all match my frame rates at 15.

No. At the present time the frame that is sent is the one that triggered the event, not the first frame of the recording. This may change in the future as Sentry sometimes misses recognition because the frame is too early.
 
No. At the present time the frame that is sent is the one that triggered the event, not the first frame of the recording. This may change in the future as Sentry sometimes misses recognition because the frame is too early.

Ok, thanks. I'm seeing this pretty often, at least 50% of the time. Looking for what settings to change to help it.
 
If you use zone crossing the trigger will be when the target has moved into at least the second zone and should be in full view.
 
If you use zone crossing the trigger will be when the target has moved into at least the second zone and should be in full view.

I do and it works well for triggering on motion and my setup that I use to send images to sighthound. But the images I'm getting from Sentry 50% of the time are missing the person. Unless they are slow (like my UPS guy, lol)
 
The image you get via SMS or email isn't the image sent to Sentry. It's the current image when BI gets the Positive back from Sentry. Usually 5-7 seconds after the trigger image. (It's the time taken to send image to Sentry, Sentry to process and send a positive back to BI and for BI to send the SMS/email.)

I'm waiting for Sentry to change this (send the trigger image) before I pay for the service.
 
Ahhhhhh...that makes a lot more sense as to why I'm seeing that. No wonder the hit rate is so low. With my sighthound integration I save the initial image captured, if I get a hit then I SMS that image.
 
Getting the image right in the alerts is a high priority. Should be quickly resolved after the 5.0 release.

Thanks for sharing the zone crossing tip. I'll add it to my tips and tricks.

-- Sam from Sentry
 
  • Like
Reactions: jrf and fenderman