5.4.5 - May 10, 2021

[fenderman]

5.4.5 - May 10, 2021
When recording continuously (including the new continuous + alerts mode), physical
recording is delayed by the duration of the pre-trigger buffer. This allows the opportunity to
record the main stream frames in the pre-trigger buffer as required. In addition, this means
that if you manually record or start/stop using the traffic signal icon, the pre-trigger buffer
will now also be recorded.
By default, the main stream is decoded when a camera is in full-screen or “solo” in the
window. A new option on the camera right-click menu allows you to disable this and force
the continued use of the sub-stream in these cases.

 

[wittaj]

I have been waiting to see this update the moment this feature started in 5.4.4. As we know, when that update rolled out, BI added the option to save substream and switch to mainstream with motion, but it would lag after motion started and would go to substream immediately when motion stopped.

So I tested this the moment the BI Bot posted the update, so I have been running it for an hour LOL.

In my testing, it has been switching to mainstream at the determined pre-trigger, but also for the post-trigger break time!

Previously, I would get about 1 hour at 3.90GB with the camera recording 24/7.

With this new feature, I got 1 hour at 140MB.

That is a tremendous savings!

Obviously bitrate, resolution, FPS, and number of triggers come into play, but it is yet another feature that can allow for higher resolutions with less storage needs.

As always YMMV.

 

[wittaj]

OK, some additional testing adding a camera at a time.

I tried it first with BI doing the motion detection but no AI - works as intended on every clip.

I tried it next with the cameras doing AI and ONVIF triggers for BI - works as intended on every clip.

I tried it next with BI DeepStack Integration - mixed bag. One car goes by and it works like intended. The next car comes by and it is halfway thru frame before it switches to mainstream. Then another one will be tagged as a vehicle by DeepStack yet it never recorded mainstream.

Next will be a cam with camera ONVIF triggers.

Curious to see what others experience.

 

[sebastiantombs]

I just switched about a half hour ago. So far DS clips are playing full res with no problems. I am using DS primarily on two cameras for street traffic. I have the pre-trigger and the post trigger both at one second so that may help. DS still keeps identifying our mailbox as a person, even though it hasn't moved in ten years. I'll update later with another camera that's in our common area so it sees a fair amount of extended people motion.

 

[tech101]

I did install the latest version earlier today. Saw my Ram Usage went to 17 gb + Anyone else experiencing something similar with latest release ?

 

[sebastiantombs]

You made me check. It does appear to be up significantly on my system just looking at UI3 stats, currently 71% and typically around 20%. Uh Oh

 

[tech101]

You made me check. It does appear to be up significantly on my system just looking at UI3 stats, currently 71% and typically around 20%. Uh Oh

Interesting, Try this - Restart the camera in blueiris it release it but I think it comes back up. Because of this I have reverted to the previous version for now.

 

[bp2008]

My memory usage is actually down from 3400 MB to about 3000 MB with this update. Not continuous recording though, and continuous recording was the focus of the update.

 

[sebastiantombs]

I had to revert back to 5.4.4.8 as well. It was over 13GB of RAM and still climbing. I switched all the cameras back to H.264 and that didn't help at all, even with a restart. So, back to 5.4.4.8 for now, anyway, and back down to ~2GB. It was nice while it lasted. I guess I could also switch to NVidia from Intel for HA but I'd rather stick with Intel. Maybe I'll try that tomorrow to see if it's HA related.

 

[wittaj]

I turned HA off with the recent updates as people were reporting issues and RAM hasn't upped from the newest update.

 

[sebastiantombs]

@wittaj Did you notice how much CPU utilization went up when you switched off HA? What's you MP/ps rate like?

 

[fenderman]

Memory usage has going to and climbing for me as well.

 

[wittaj]

With the substreams option I noticed it didn't make a big difference whether I was using HA or not. A few % increase and I am at 230MP/s

 

[sebastiantombs]

Maybe I'll try that if NVidia produces the same memory leak.

 

[wittaj]

Mine RAM stayed normal for the 4 hours I have been running this version. I just turned on HA and will see what happens!

 

[mayop]

Ram usage seems normal for me (Currently < 300mb) after a few hours. I have HA enabled with the onboard intel gpu. Main is a h265 stream and sub is h264 for a few of my cameras.

 

[wittaj]

Mine RAM stayed normal for the 4 hours I have been running this version. I just turned on HA and will see what happens!

A little after an hour later with HA on and my RAM has tripled, but I have also been opening lots of clips to see if it has gone to mainstream and the RAM jumps quite a bit and does release some when I go back, but not all.

Gonna wait for the main traffic to slow down and then will restart it and gonna run it till it restarts LOL. I want to also see if not opening clips keeps it down overnight.

Sent an email to Ken, hopefully others have as well.

 

[spankdog]

Experiencing similar issues here. Memory maxed out and BI crashing. Will roll back soon.

 

[BORIStheBLADE]

Man 5.4.4.8 has been working so well for me I wanted to put off an update for a while haha. The pressure!

 

[Kensko]

Had the same issue with memory leak. BI and Windows grinding to a halt. Seems like the 5.4.5 version has been pulled and 5.4.4.8 is the newest version available.