Pre-trigger video buffer stopped working

tsutton

Young grasshopper
Joined
May 26, 2016
Messages
79
Reaction score
5
Has anyone noticed that the Pre-trigger video buffer has stopped working or just me? I've set it up for 8 seconds. On the JPG image, I can see an movement so I viewed it, but it was already gone. Basically there were nothing captured in the 8 seconds buffer that it was supposed to do!

Did something change?
 

srglassw

Getting the hang of it
Joined
Jun 17, 2014
Messages
89
Reaction score
27
Location
Vancouver Island, BC, Canada
Has anyone noticed that the Pre-trigger video buffer has stopped working or just me? I've set it up for 8 seconds. On the JPG image, I can see an movement so I viewed it, but it was already gone. Basically there were nothing captured in the 8 seconds buffer that it was supposed to do!

Did something change?
It looks like something has changed between Blue Iris server versions 4.7.6.13 and 4.7.6.17. I was on '13 and buffer was fine so I just now updated to '17 and now alert video starts at the point of first motion... no pre-trigger buffer. I have emailed support on this issue.
 
Last edited:

tsutton

Young grasshopper
Joined
May 26, 2016
Messages
79
Reaction score
5
Thanks, glad it's not just me then!!

I'll email them as well to back up the evidence that this is no longer working.
 

tsutton

Young grasshopper
Joined
May 26, 2016
Messages
79
Reaction score
5
Ken has just said that it's more likely to be a config issue involving direct to disc & keyframes, rather than a bug.

So, I am looking at the config again... but it still doesn't explain why it used to work before and now it doesn't work after an upgrade.
 

J Sigmo

Known around here
Joined
Feb 5, 2018
Messages
997
Reaction score
1,333
After updating to 4.7.6.17, I was getting the red borders when my cameras detected movement, but nothing was being written to the HDD.

This sort of magically fixed itself when I went into each camera to check on the "camera properties/trigger" and "camera properties/record settings", and then, instead of getting out by clicking on the "cancel" button, I clicked on "OK" so that it re-started the camera. Doing that for each camera seemed to cure the problem. But note that this was only for some ReoLink cameras. The Dahuas never missed a beat. So that probably means something! :)
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
Ken has just said that it's more likely to be a config issue involving direct to disc & keyframes, rather than a bug.

So, I am looking at the config again... but it still doesn't explain why it used to work before and now it doesn't work after an upgrade.
because direct to disk begins recording on the keyframe, if you have a long iframe interval, sometimes it will record the pretrigger and sometimes it wont...match the iframe interval to the fps and see what happens.
 
Top