Recent content by Shap

Good point - to be more precise we actually need to use the angle of view instead, as focal length and sensor size both play a role. BTW, what camera model is it?

I think you need 6mm or more in such an environment to get a close picture of the person. Your camera looks like 2.8mm, and regardless of camera brand, you will not be able to capture details well enough.

I just try to understand the numbers - are they suppose to sum to 100%? i.e. 70+ fatality rate + survival rate should be 100%? In this case, the fatality rate should be 5.4%, no? What am I missing?

Agree - first it is really not the best idea to use /22 subnet. But if I use /22 I would really prefer to use my DHCP server for that :) I am using Unifi UDM - it does support using /22 subnets, but you are right - many routers may not

I read through the thread, and have a question - why not set up a DHCP server with static IP assignments? You will achieve exactly the same result and it will be actually more easy if you decide to move the camera into another subnet later. I have all my cameras with DHCP but am assigned a...

One of the things I wish we had in BI is a detailed debug log on what is happening... The current log file does not provide such a level of details ...

I have only one Alerts folder and JPG and DAT files are created there w/o a problem with DB Only option set. (the resolution is low, but that is expected).

Correct on both items. (I am using DS CPU version and 4MP camera). For the camera, I used: Loryta IPC-T5442TM-AS-LED , 4MP camera. I also tried with Amcrest FCM-IP8M-T2499EW28MM, 8MP camera.

Well, it is much better - now you recovered 2 sec(!) of possible identifications! Same behavior here - so there are 4 bugs (I already open tickets for that, but support used 2MP cameras that do not trigger this problem. They need to use 4Mp+ cameras for that): ------ 1. When Hi-Res JPEG option...

I have a similar experience. I still do not understand why there is a problem pulling 4-5MB files each second on a very powerful machine. Should not be an issue at all. Anyway, pay attention that you have the same problem I had - you have T-562 and then twice T+2108. And you do not have T+0...

You have the same problem I had - not only you do not get T+0, you also have a duplicate frame sent to DS: (T+598). This also probably causes you to have many false-negative responses from DS. I bet you have this option set to "Hi res JPEG" - set it to DB Only and it will fix the problem

Thank you - I can not explain that, but in my case, it is reproducible on any camera any time I turn this option on. I am using Intel+VPP, the latest BI+DS. Nothing really special about my config, all drives are SSD (so read/write is fast), CPU is 10% on average. The manual trigger will cause...

I have "begin analysis with motion-leading edge” unchecked (tried with check as well). Pre trigger buffer is 5 sec. FPS ratio is 1.0 Sent from my KB2005 using Tapatalk

Hello guys, using latest BI+DS. Can anyone confirm if they are getting T+0 in the deepstack analysis window? I am constantly getting T+50 up to T+100 msec. So the image sent to DS and motion rectangle is a bit off.

1. Followed the procedure from here: OOps - Need a Clean Start - How ? - Blue Iris 2. It was set to the default setting, "Database Only".