Prebuffer setting ignored in 5.0.2.0?

reverend

Pulling my weight
Jun 18, 2015
310
193
UK
I finally got around to the 5.x upgrade going from the last 4.x release to 5.0.1.0 - I've updated to 5.0.2.0 today and it seems my cameras are now ignoring the prebuffer setting (I have it set to 3 seconds for triggered motion).

Is anyone else seeing this please?

Looking at the captured alerts this was working fine in 5.0.1.0 and has only started on 5.0.2.0 - possibly something to do with the new alert code for the AI post processing? I just wanted to check before I log a support ticket.

Thanks
 
I finally got around to the 5.x upgrade going from the last 4.x release to 5.0.1.0 - I've updated to 5.0.2.0 today and it seems my cameras are now ignoring the prebuffer setting (I have it set to 3 seconds for triggered motion).

Is anyone else seeing this please?

Looking at the captured alerts this was working fine in 5.0.1.0 and has only started on 5.0.2.0 - possibly something to do with the new alert code for the AI post processing? I just wanted to check before I log a support ticket.

I have Pre-Trigger video buffer set to 3 seconds on all my cameras. I have not noticed any problems where a motion triggered event does not include the 3 seconds of video before the trigger. Does your camera's Frame rate match the I-Frame interval?
 
You've upgraded to 5.0.2.0 which was released yesterday?

This setup has been fine for two years until 5.0.2.0.

In terms of iframe I've got a mixture of some matching and some set at double the frame rate.

I'm just upgrading Windows to 1903 to see how that goes.
 
  • Like
Reactions: beepsilver
I don't think the pre-trigger buffer has been working at all in 5. I had it set to 2, now I've increased it to 3, and it definately doesn't start the clip 3 seconds before the actual trigger.
 
Was working with 5.0.1.0. Confirmed it is not working with 5.0.2.0.
 
I'd like to revert to 5.0.1.0 if anyone has it?
 
I was in touch with Ken this morning...tonight's update fixed the issue.
 
I'm sorry for resurrection this thread but my Bi ver is 5.0.8.2 and was playing with Pre trigger buffer with no success, there is no difference at all even if I set 30 sec.

Do you guys have the same (the latest) version with Pre trigger working ?
 
What do you expect to happen that is not happening ?
Are you doing continuous recording of record only on motion ?
 
I'm expecting to have at least 5 sec video before it triggers the motion. I have set my i frame to match my 15 fps set on my hik cam (the latest firmware).

I'm doing Continuous recording 24/7 with Zone Crossing motion detection. I don't see what happened 5 sec before it triggered the notification and I have to manually do it which is frustrating a bit.

Any help is much appreciated !
 
Last edited:
Not sure where your problem is.

I am using the lastest version of BI 5.0.8.2. When I click the alert window preview picture in the BI console the alert playback starts the correct number of seconds before the actual alert. In UI3 when I click the alert windows preview picture the alert playback starts the correct number of seconds before the actual alert. The pretrigger buffer is checked and set to 10 seconds. All cameras have the frame rate and Iframe values set to the same value, so the time between complete frames is 1 second.

I do not use email or SMS notifications for alerts.
 
I'm sorry for resurrection this thread but my Bi ver is 5.0.8.2 and was playing with Pre trigger buffer with no success, there is no difference at all even if I set 30 sec.

Do you guys have the same (the latest) version with Pre trigger working ?
If you have "Use Decoding Only When needed" turned on, this will cause a problem at times, see the help file.
 
Thanks for your replies. I think I have found a solution to my problem. When I was testing it I triggered the camera manually (external triggerby pressing the button in BI) then I have parked my car after some time and realised that it woks as the notification shows video 10 sec before I entered my property.