5.4.9 - June 25, 2021

And as of this morning, 8 July 21, the latest version of Deepstack appears to be v1.2.1. The CPU version for Windows installer filename is DeepStack-Installer-CPU-2021.02.1.exe.
 
  • Like
Reactions: JNDATHP, fenderman and sebastiantombs
Uhhh, maybe look at the file dates in the DeepStack directory? Or look at the file you installed from? The answer is always right there, behind the milk :)

The deepstack.exe on my machine has a file date of 02/06/2021 which I think is the latest.
 
  • Like
Reactions: looney2ns, beepsilver and kc8tmv
sebastiantombs said:
Uhhh, maybe look at the file dates in the DeepStack directory? Or look at the file you installed from? The answer is always right there, behind the milk :)

The deepstack.exe on my machine has a file date of 02/06/2021 which I think is the latest.
Click to expand...

I have the same date for deepstack.exe and used the installation file version I mentioned above.
 
  • Like
  • Haha
Reactions: kc8tmv and sebastiantombs
Just updated to 5.4.9.6 and got a 170 error right out of the gate again. I'll let it run until after dinner before reverting back again if it's too error prone.
 
  • Like
Reactions: looney2ns and beepsilver
I'm just getting 170 errors, no 100 and no -1. I am getting "can't find this file" when I try to play back clips from one camera that I've tested, so far. The same behavior as last time is still happening, "can't find this file" then if I click on the previous lip that was successfully identified, it will play through the clips that give the file error. As usual, tuning shows detection in all of them. So, from my perspective 5.4.9.5 id no better than the rest of the 5.4.9.x series. Back to 5.4.8.2 yet again.
 
wittaj said:
So I just took the plunge with 5.9.4.6 and knock on wood, so far I am not getting the errors. All the custom models are working. Now to confirm the onvif triggers and what not work.
Click to expand...
Still happy enough with 5.9.4.6? Server Errors all gone, even with custom models?
 
I'm still getting error 100--when they happen early in the analysis, the alert is canceled when it should be confirmed.
 
  • Like
Reactions: sebastiantombs
I let it go all night with dark.pt included. Lots of 100 and 170 errors. I have shut off models and will let it run today that way to see if there's a change on my system without a model.
 
  • Like
Reactions: beepsilver
sebastiantombs said:
I let it go all night with dark.pt included. Lots of 100 and 170 errors. I have shut off models and will let it run today that way to see if there's a change on my system without a model.
Click to expand...
I'll do the same, but not hopeful that the default model will work as well at night...we'll see :D
 
With just a couple of hours running on the stock model, the detection rate is way up and there's only a few error, mostly 170. I'll see how it does overnight. When detection is working better, more like it does in tuning, it does work fairly well at night so we'll see what happens.
 
  • Like
Reactions: kc8tmv
sebastiantombs said:
With just a couple of hours running on the stock model, the detection rate is way up and there's only a few error, mostly 170. I'll see how it does overnight. When detection is working better, more like it does in tuning, it does work fairly well at night so we'll see what happens.
Click to expand...
This is 5.9.4.6, with custom models? If so, which custom models?
 
I'm attending the BI webinar right now. I asked Ken about DS errors 100 and 170. Here's his response.

Is there info on the possible Deepstack errors? Specifically 100 and 170?

ken 11:12 AM
These both indicate DS did not complete or did not respond. Only known solution is to restart DS. Blue Iris will attempt this for you if it’s configured to also start/stop DS for you.
 
  • Like
Reactions: beepsilver and sebastiantombs
You must log in or register to reply here.
Top Bottom