Just upgraded from BI 4 to 5 a few days ago. My pre-record buffers for all 14 cameras have completely stopped working when using substreams. If I turn the substream off for a camera, the pre-record buffer starts working again.
The pre-record buffer range 3 to 4 seconds but I increased them to 10 seconds. It's like this on all cameras. I frame interval is FPS in cameras where I can set that. Pre-record buffers all worked fine before the upgrade. I've literally not changed anything except for substreams. When I disable substreams, pre-record works again as before. Since the pre-record is for the mainstream, I don't see why this would make a difference.How long is your pre-buffer and what is the KEY frame in the Camera Status page? If the KEY is less than 1.00, that can impact the prebuffer.
I like to hit the community first before I lean on my priority support subscription.collect the required system configuration data and send an email to the developer.
See the Blue Iris Settings about tab For the Get support button, email support.
It worked fine in V4 because V4 didn't use substreams...The pre-record buffer range 3 to 4 seconds but I increased them to 10 seconds. It's like this on all cameras. I frame interval is FPS in cameras where I can set that. Pre-record buffers all worked fine before the upgrade. I've literally not changed anything except for substreams. When I disable substreams, pre-record works again as before. Since the pre-record is for the mainstream, I don't see why this would make a difference.
That's not the issue. The i-frame interval on most of them is the same as fps. Changing pre-record buffer to 10 seconds makes no difference either.It worked fine in V4 because V4 didn't use substreams...
In V5, the switch from substream to mainstream occurs on the nearest iframe, so if you had a prebuffer of 3 seconds, yet the KEY is 0.2 (or 5 seconds), then it won't get a prebuffer as the prebuffer time has to be greater than the time of the KEY...
From the help file:
When using dual-streaming, insure that your pre-trigger buffer is at least as large as the
time between key frames in the main stream. If your key frame rate is 0.5, this means at least 2.0 seconds of pre-trigger time
so that the buffer will contain at least one key frame.
I have NEVER recorded continuous. That would fill up my hard drive very quickly. I have video alerts going back months.Are you recording continuous or continuous + triggered?
It should be continuous+triggered or continuous + alerts.
If the KEY is good and you are recording +triggered, then have you tried a reboot of the computer? That will fix a lot of these issues we have seen recently when someone updates.
If that doesn't do it, then rollback to the latest stable release.
Yes. I'm familiar with this change. That has nothing to do with the fact that the pre-trigger buffer is still not actually recorded.Are you talking about the Pre-Trigger buffer on the camera record tab?
The behavior of this feature has changes in version 5.4.9. Read the help file.
Not sure what you mean? General tab under camera settings for that camera or something else?Post a capture of the cameras tab from the status page of the console.