5.5.1 - September 23, 2021

fenderman

fenderman

Staff member
Mar 9, 2014
36,892
21,407
The DeepStack AI feature to detect/ignore static objects has been improved by
implementing some hysteresis—it now takes time (up to 2 minutes) to consider an object
“gone” from the scene. This prevents false alerts caused by static objects that only
temporarily disappear from detection. Also these algorithms are now applied to all objects,
not just those enumerated in the to confirm box.
Utilizing the new dynamic group layout functionality, the group setting to Only cycle when at
least one camera is detecting motion, triggered or alerted behaves on the browser or client app
as it does on the console—showing all cameras at once that meet this requirement.
The camera layout option to Open in desktop frame is now memorized per group as well as per
camera. When selecting a group on the console, cameras are automatically moved to the
desktop or back to the console. Cameras that are not in the selected group are left as they
were. Camera desktop window position is currently not group dependent at this time.
 
  • Like
Reactions: looney2ns, kc8tmv, sebastiantombs and 1 other person
Excited to see how ignore objects works. I have a parked car excluded from motion area now because of so many issues
 
  • Like
Reactions: kc8tmv
I had to roll back to version 5.5.1 from 5.5.2 because of extremely high CPU usage. I'm using an I9 processor with 16gb of memory and I was spiking at +100 CPU every couple of seconds. I also have deepstack enabled on five of my 14 cameras. I'm using substreams on all cameras, which usually idles my cameras at about 5% of CPU, so these 100% jumps are unusual. They do not occur with anywhere near the same frequency with 5.5.1. (though they do occur). Attached are two screenshots of a typical couple of seconds with 5.5.2. It looks like deepstack is contributing the most to the CPU hikes, as I'm seeing 40% CPU use for each python thread that is active, but I also see the Blue Iris UI flag CPU usage at 100% every couple of seconds. The BI CPU jumps correspond with the deepstack thread CPU jumps. Deepstack is running on the same machine as BI and I'm using hardware acceleration on all cameras (though some of my .265 cameras do not seem to take advantage of vpp).


BlueIris100Percent.png

Here's the memory shot.
BlueIris100PercentMemory.png
 
  • Like
  • Wow
Reactions: ARAMP1 and sebastiantombs
CrazyAsYou said:
This is not an answer to your CPU issue as it seems like a bug from what you've said but can I ask what GPU your running? reason for the ask is that I've found using the GPU (CUDA) version of deepstack performs signicantly better - I'm running an older Nvida 970GTX
Click to expand...
I'm not running a separate GPU as the I9 has a GPU on the chip. I have been considering adding a GPU for deepstack, but have not seen anything that is priced reasonably for the limited application that I need it for (and it appears that I would also need to use NVidia to take advantage of hardware acceleration). But perhaps with the current bans on crypto currencies, the GPU prices will finally start coming down....
 
Has anyone esle got an issue where 5.5.1.x seems to be saving all alert images to the alerts folder and not just Deepstack confirmed? As you can see from the below I'm database only and the Burn lable mark-up in AI previously only saved confirmed alerts with the mark-up to the alerts folder.

1632993835914.png
 
CrazyAsYou said:
Has anyone esle got an issue where 5.5.1.x seems to be saving all alert images to the alerts folder and not just Deepstack confirmed? As you can see from the below I'm database only and the Burn lable mark-up in AI previously only saved confirmed alerts with the mark-up to the alerts folder.

View attachment 103271
Click to expand...

That has been happening since DS was introduced to BI if you check that Burn label box. I am still on 5.4.x.x something and it happens.

If you uncheck that box, the images are not saved, but they need to be saved in order to have that box around the objects.
 
  • Like
Reactions: sebastiantombs
wittaj said:
That has been happening since DS was introduced to BI if you check that Burn label box. I am still on 5.4.x.x something and it happens.

If you uncheck that box, the images are not saved, but they need to be saved in order to have that box around the objects.
Click to expand...

TBH I think it has bounced backwards and forwards a few times, at first it only did confirmed alerts and I recall it broke/changed in a few 5.4.x.x versions but then worked (only stored confirmed alerts) in later versions of 5.4.x.x
 
@Buxton
I'm running an i9-9900K and have noticed increased CPU usage too. Things like just opening UI3, without any motion going on, will sometimes spike it up to 50% when it normally wouldn't even be noticeable before.
 
ARAMP1 said:
@Buxton
I'm running an i9-9900K and have noticed increased CPU usage too. Things like just opening UI3, without any motion going on, will sometimes spike it up to 50% when it normally wouldn't even be noticeable before.
Click to expand...
Yes, I ended up rolling back all the way to 5.4.9.18 as there are a number of bugs in the 5.5 implementation. I don't mind testing new BI software, as I've had Ken correct a number of bugs that I've found in the past. But it gets old when basic things like deleting clips through UI3 is broken and there's really no central place to log a bug and then follow-up on its status.
 
Buxton said:
Yes, I ended up rolling back all the way to 5.4.9.18 as there are a number of bugs in the 5.5 implementation. I don't mind testing new BI software, as I've had Ken correct a number of bugs that I've found in the past. But it gets old when basic things like deleting clips through UI3 is broken and there's really no central place to log a bug and then follow-up on its status.
Click to expand...
It gets old when people complain about issues is a new release despite being told by the software that 5.4.9.18 IS the most stable release. Pro tip, if you want to stop testing software stop downloading the latest version.
 
  • Like
Reactions: sebastiantombs
fenderman said:
It gets old when people complain about issues is a new release despite being told by the software that 5.4.9.18 IS the most stable release. Pro tip, if you want to stop testing software stop downloading the latest version.
Click to expand...
Ok got it. You know you could help the cause by establishing a "central place to log a bug and then follow-up on its status". Why not create a sub folder on the forum called "bug reports" and then monitor the status of the bug fix for each submission.
 
Buxton said:
Ok got it. You know you could help the cause by establishing a "central place to log a bug and then follow-up on its status". Why not create a sub folder on the forum called "bug reports" and then monitor the status of the bug fix for each submission.
Click to expand...
You know you could do that by creating a thread with your bug then post the status of the resolution? You know, Columbo, in the subforum called troubleshooting? Perhaps you should look at a vms that only provides updates once or twice a year. That way your OCD wont kick in and force you to download an unstable version because you cant wait a few weeks until the version is marked stable. I know, its difficult.
 
  • Like
Reactions: sebastiantombs
kklee said:
I found that the integrated GPU wasn't quite powerful enough to handle Deepstack and HA at the same time. I added a Quadro P400 and Deepstack runs great set on High. I'm still using the Intel GPU for HA.
Click to expand...

What are you running Deepstack on? I've been trying to get GPU run on unraid with no luck.
 
This morning I emailed Ken after noting that new Cliplist events were no longer showing at the top.
(I recall reading another post where someone else may have noticed this too, but I cannot locate it.)

His reply...
Some changes in the works.
Design should keep scroll at top if it's already at the top or you enable the NOW button on the timeline.
Idea is not to change the view if you're searching for something or when you switch views position to the same time shown in the timeline.

Enabling the 'Now' button did the trick for me.
The planned changes sound good.
 
  • Like
Reactions: ARAMP1 and fenderman
You must log in or register to reply here.
Top Bottom