5.4.9 - June 25, 2021

[sebastiantombs]

They're right on the clip displayed by BI in the alerts column. Right now I'm thinking, seriously, about shutting DS down until this is fixed or DS gets dropped from BI. The missed detections are running at a 2:1 or 3:1 ratio compared to detections. This all comes at the cost of a higher than normal CPU load. The problem I have is that it can, when it works reasonably, eliminate false triggers on a few cameras. Maybe I'll just shut it down on the cameras I really want it on. As far as analysis when looking at the clips or dat files, they work fine and show detections, but that doesn't translate into a successful detection in BI. Therein lies the problem. Incidentally I still don't see the blue border on any of the clips not matter how I view them.

 

[IAmATeaf]

I’m not using DS at all, just using ONVIF to trigger the cam and then have a clone of the cam with BI motion detection to trigger the clone.

 

[sebastiantombs]

I did shut DS down on those two cameras. Within a half hour it missed someone coming up the driveway and approaching the front door, on a Segway up the driveway and on foot to the door. That's a total of four different cameras report "deepstack: 170" and "deepstack: 100". So I'm back to 5.4.8.2 now and everything seems to be working much, much, better. Cameras involved: 2431T-ZAS, 5442T-AS, 2431T-ZAS and another 5442T-AS and all are "clone masters".

 

[kklee]

I did shut DS down on those two cameras. Within a half hour it missed someone coming up the driveway and approaching the front door, on a Segway up the driveway and on foot to the door. That's a total of four different cameras report "deepstack: 170" and "deepstack: 100". So I'm back to 5.4.8.2 now and everything seems to be working much, much, better. Cameras involved: 2431T-ZAS, 5442T-AS, 2431T-ZAS and another 5442T-AS and all are "clone masters".

Hmm, curious, I wonder what's going on with your system? For what it's worth, my system is an i7-7700K with 16GB RAM, SSD boot drive and two Seagate skyhawks for local storage.

I have a mix of 5442's, Hikvision OEM 8MP, a couple of Amcrest cameras, and an EZVIZ DB1C doorbell.

I have 9 cameras configured for BI motion detections with DS enabled. Masters are used for motion detection (clones for continuous recording) and have been working well with 5.4.9.x using DS (after I turned off face detection).

I have a custom Powershell script configured to send alerts via Pushover to my Android devices when there's DS confirmad alert.

DS detection seem to be working well with most of the cameras, there's an occasional Deepstack message, maybe about 5% of the time.

I have one camera (Hikvision 8MP) that generates most of the Deepstack messages. This camera is aimed at my deck and can see the alley beyond a fence about 20 feet away. It triggers whenever anything passes by on the alley, but rarely manages to identify the object due to the angle, other than occasionally mistaking my covered barbeque as a person. It used to report 'nothing' before the Deepstack message was added, now it reports Deepstack messages about 75% when it can't identify an object.

 

[sebastiantombs]

My system is a generation older, 6700K, and has 32GB of RAM. I'm running 19 cameras at the moment and all but three are Dahua. I could subscribe to the idea that it's a system problem IF it didn't work so well on 5.4.8.2. It was so-so on 5.4.9.0, and .1 but fell apart completely on .2 and .3. Whatever changes were made in the .9 series have had bad effects on detection performance and run well into the seconds for total detection time. The system has been optimized and CPU sits around 20% during the day with 15MB/ps and around 12MP/ps. The thing that is really frustrating is when played through "tuning" detection happens so, in my mind at least, there's something significantly different going on between "tuning" and real time detection parameters.

 

[beepsilver]

I'm experimenting using DS without any custom models (was using dark.pt). Every trigger that should have been an alert but failed had Error 100 in the custom section of the analysis. I'll update when I've got more info.

 

[looney2ns]

I cured my DS ills. How you ask, I used the Uninstall function.

 

[sebastiantombs]

I have found 5.4.8.2 to be the "best" version so far. The 5.4.9 series has been loaded with problems at least for me and some of the others.

 

[kc8tmv]

5.4.9.4 went into DeepStack 100 error world.
Sample of logs:
3 7/2/2021 7:15:21.154 PM FrontTest MOTION
3 7/2/2021 7:15:21.403 PM FrontPorch MOTION
0 7/2/2021 7:15:22.203 PM App DeepStack has been restarted
1 7/2/2021 7:15:31.756 PM FrontTest DeepStack: Server error 100
0 7/2/2021 7:15:31.756 PM FrontTest DeepStack: Alert cancelled (DeepStack: 100)
1 7/2/2021 7:15:32.289 PM FrontPorch DeepStack: Server error 100
0 7/2/2021 7:15:32.299 PM FrontPorch DeepStack: People:85% [52,432 252,797] 513ms
0 7/2/2021 7:15:34.273 PM App DeepStack has been restarted
10 7/2/2021 7:16:29.821 PM Server ::ffff:192.168.200.220: Connected
10 7/2/2021 7:16:29.834 PM hs ::ffff:192.168.200.220: Login
3 7/2/2021 7:17:05.753 PM FrontTest MOTION
3 7/2/2021 7:17:19.457 PM FrontPorch MOTION
1 7/2/2021 7:17:19.903 PM FrontTest DeepStack: Server error 100
0 7/2/2021 7:17:19.903 PM FrontTest DeepStack: Alert cancelled (DeepStack: 100)
0 7/2/2021 7:17:22.289 PM App DeepStack has been restarted
10 7/2/2021 7:17:31.225 PM hs ::ffff:192.168.200.220: Logout, 1:02
1 7/2/2021 7:17:32.600 PM FrontPorch DeepStack: Server error 100
0 7/2/2021 7:17:32.612 PM FrontPorch DeepStack: person:90% [68,505 299,806] 8053ms
0 7/2/2021 7:17:34.825 PM App DeepStack has been restarted
3 7/2/2021 7:17:35.248 PM Drive MOTION
3 7/2/2021 7:17:40.533 PM Garage MOTION
1 7/2/2021 7:17:49.445 PM Garage DeepStack: Server error 100
0 7/2/2021 7:17:49.445 PM Garage DeepStack: Alert cancelled (DeepStack: 100)
1 7/2/2021 7:17:49.545 PM Drive DeepStack: Server error 100
0 7/2/2021 7:17:49.556 PM Drive DeepStack: person:93% [1318,685 1681,1378] 8054ms
0 7/2/2021 7:17:49.563 PM Drive DeepStack: People:92% [1277,668 1718,1395] 8054ms
0 7/2/2021 7:17:52.350 PM App DeepStack has been restarted
3 7/2/2021 7:18:29.532 PM Upper_Basement MOTION
0 7/2/2021 7:18:39.470 PM Upper_Basement DeepStack: person:80% [798,474 1021,1219] 8145ms
0 7/2/2021 7:18:39.471 PM Upper_Basement DeepStack: People:53% [805,446 1052,1225] 8145ms
Then Alert window looks like this:


Wanted to go back to 5.4.9.2 (wasn't too bad for me), but don't see it as an option in the drop down to roll back to.
Anyone know how to get that version back?

 

[sebastiantombs]

Yeah, I tried it too. Funny thing is it seemed to work for one, and only one, detection then went "nothing found for two detections and finally settled into "deepstack:100". Back to 5.4.8.2

I have to again stress that there is a problem, at least with the CPU version for Windows, with contrast and lighting. I'm running dark.pt as well as the standard .pt and in the evening it missed way more than it should. At night I am getting around 50% while it was previously around 10%.

Look here -

Blue Iris Update Vault

Blue Iris Updates (64 bit) - History

ipcamtalk.com

 

[beepsilver]

5.4.9.4 went into DeepStack 100 error world.
Wanted to go back to 5.4.9.2 (wasn't too bad for me), but don't see it as an option in the drop down to roll back to.
Anyone know how to get that version back?

Were any of those error 100s not in the custom portion of the analysis?

 

[kc8tmv]

Were any of those error 100s not in the custom portion of the analysis?

Not sure. Would probably need to go back to that version and run it through the analysis window, right?

 

[beepsilver]

Not sure. Would probably need to go back to that version and run it through the analysis window, right?

I don't think you'd need to go back to that version; if the .dat file for any of those cams that reported the error are still in your alerts folder, you can drag them into the DS tab of the status window and take a look. If you're not using any custom models like dark.pt or any other ones, then don't bother, that answers the question. But if you are using custom models, I'd like to know if the errors are constrained to the custom portion of the analysis. A couple of screenshots would be helpful too
Were you able to download 5492?

 

[105437]

Anyone else experiencing camera connectivity issues with any of the 5.4.9.x releases?

 

[wittaj]

Well .4 broke my machine.

From 5.4.8.X to current, after I would see it had trouble or getting errors or things like RDP would not work and reboot would take forever, I would rollback and all is good.

Today I tried .4 and same issues, so I rolled back and it now takes forever for the computer to come back from a reboot.

I do not know if BI is somehow causing startup of the computer to struggle? I have done DISM and SFC and it all comes back clean.

@105437 - in my observations, I think the most recent versions do not like Hardware Acceleration and that is what the cause of the connectivity issues are. In 5.4.6.3 mine all work fine with HA, when I would update, at least half the cameras had issues until I disabled HA.

 

[105437]

Well .4 broke my machine.

From 5.4.8.X to current, after I would see it had trouble or getting errors or things like RDP would not work and reboot would take forever, I would rollback and all is good.

Today I tried .4 and same issues, so I rolled back and it now takes forever for the computer to come back from a reboot.

I do not know if BI is somehow causing startup of the computer to struggle? I have done DISM and SFC and it all comes back clean.

@105437 - in my observations, I think the most recent versions do not like Hardware Acceleration and that is what the cause of the connectivity issues are. In 5.4.6.3 mine all work fine with HA, when I would update, at least half the cameras had issues until I disabled HA.

It's interesting, in my case... when BI shows that it is unable to connect to a camera, I also can't connect to it directly from a web browser. It's almost like it has the camera locked up somehow.

 

[wittaj]

Interesting. I think somehow the newer updates are changing things we would not expect it to like some cameras are having SMD and MD turned on with a BI update.

And then my crazy issues with reboots and Remote Desktop that would go wonky until I rolled back, but now that is messed up too.

 

[105437]

I'm running 5.4.8.2 with DS enabled. When new releases come out, I test. I've sent Ken some emails explaining the issues I'm having with 5.4.9.x releases, hopefully he'll find the fix.

 

[kc8tmv]

Interesting. I think somehow the newer updates are changing things we would not expect it to like some cameras are having SMD and MD turned on with a BI update.

And then my crazy issues with reboots and Remote Desktop that would go wonky until I rolled back, but now that is messed up too.

Really silly question and no disrespect to the developer at all, but don't the developers and Beta Testing team see these issues? Are they doing something different than us?

 

[fenderman]

Really silly question and no disrespect to the developer at all, but don't the developers and Beta Testing team see these issues? Are they doing something different than us?

There is a single blue iris developer. Its a one man show aside from a recent tech support add on. You are the beta team. That is why there is an option to only install the latest stable update. You chose to beta test.
The alternaitve is for BI to push releases every six months to a year like other VMS, which would completely suck. You have the option to install the update or not. Dont let OCD get the best of you.