Search results

Anyone have issues with h265 streams and recordings with 5.5.6? None of my h265 recordings will play using ui3 and the cameras will not show the h265 mainstream when viewing live (Sub stream is h264). Soon as I downgrade to 5.5.5 it all works normally. My cameras that use h264 for both main and...

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.

New BI has support for Deepstack

It should be fine since Ai is doing all the notifications through telegram once it processes an image. I never tried unchecking everything since the main one I use is "Extern" that creates an alert when AI sends a trigger to BI (External).

Try removing the trigger part so that it looks like this: http://192.168.5.15:8181/admin?camera=backyard1&user=aiuser&pw=password&flagalert=3&memo=[detection]&flagclip

This is the one I use. http://127.0.0.1:81/admin?camera=[camera]&flagalert=3&memo=[summary]&user=[Username]&pw=[Password]&flagclip That will flag and set it as a confirmed alert (S logo). If you just want to flag it then use flagalert=1. My alert settings are setup like this...

Seems it was intentional before 5.3.7.13. When I added "trigger" to the url (/admin?trigger&camera=) the clips would get flagged but then I had some other issues with clips being labeled as 0 secs. I contacted BI support, explained how I have mine setup and they replied: A day later I received:

Yes it started around the Jan 2 update. https://ipcamtalk.com/threads/tool-tutorial-free-ai-person-detection-for-blue-iris.37330/post-516698 I rolled back to 5.3.7.5 and they work fine.

Seems the documentation added a variable called flagclip which seems to flag it properly when I trigger the camera manually and run the url twice in a broswer. Will test to see if it works when BI detects someone...

I've noticed the latest version(s) of BI breaks flagged and confirmed tagging. I've tried it manually in a browser to verify it wasn't AITool and it still didn't work (as of 5.3.7.10). I rolled it back to 5.3.7.5 and it fixed the issue. I'm also going to try the confirmed alert tag which will...

I use WInSCP to manage files using a GUI (I use SFTP protocol to connect) while using X-Shell for a command line terminal. Both are free. I also use Visual Studio Code to edit the files.

The problem is Unifi Protect. It causes the keyframe rate to be too low. Ideally it should be 1.00 as shown below: There is a post on BI of possible fixes for cameras themselves: https://blueirissoftware.com/forum/viewtopic.php?t=1460 Now as for protect there is a variable that causes the...

There are newer docker images now as well. docker pull deepquestai/deepstack:cpu-2020.12 docker pull deepquestai/deepstack:gpu-2020.12 The latest list of docker images can be found here for those interested. Docker Hub

Here is a compiled version based on his latest code (Last update was 6 days ago). Just be aware it may have unfinished or broken features. http://www.mediafire.com/file/zn7r3aq0u01clio/AiTool_Oct27_Release.zip/file

This is the one I use docker run --restart=always -e VISION-DETECTION=True -v localstorage:/datastore -p 81:5000 --name deepstack deepquestai/deepstack:cpu-x5-beta Just change 81 to the port you want to use.

I noticed BI changed what stream the JPEG image is saved from recently. It used to use the sub stream but now it uses the main stream so you may need to edit your mask image again.

If anyone wants to change their telegram bot icon you can do it using the following https://taradevko.com/bots/configure-telegram-chatbot/ I made a round AI logo for mine if anyone wants to use it.

You need to be able to compile the source code to add it. To avoid multiple versions from multiple people I've made a Pull Request of the changes I made for mine so maybe @Chris Dodge can add it to his version.

It's possible for sure and just requires a few small edits in the code. My edited result looks like: https://iili.io/2fFWu4.jpg

Same issue here

I modified and compiled the code to add the binding boxs and include a caption on the image of what it detected.

I've had no issues so far with images being sent. When I started had it send the full res camera image 2688x1520 until I switched to the 640x360 sub stream which still works. https://iili.io/dPwyWN.jpg

It's the same url you put into the ai tool settings page. If you're running a browser on the same machine as deepstack it would be localhost:<port> or 127.0.0.1:<port> However I found the api_key part of the container command might be the issue...

It's giving a HTTP 401 error. It should be 200 which is a HTTP code for OK. Error 401 = "Unauthorized client error". Seems I missed that the first time you posted it. Did you try visiting your deepstack container in a web browser to make sure it's activated?

It looks the same as mine. Yours is running 10x faster than my cpu version on a i7-4790 so it might be using your gpu. Mine typically runs 500-700ms per query. If you right click on the docker system tray icon and select Dashboard you can view the same info there. You can also stop and delete a...

You can install multiple versions of deepstack to test while only running one container at a time (or two if you wish). Installs normal version with AVX and uses the CPU docker pull deepquestai/deepstack Installs gpu version docker pull deepquestai/deepstack:gpu Now you can select which one...

It might be because you don't have "Motion zones" checked. I would have to test to verify that but it would have worked before because it was being triggered externally using the url (Extern is checked in your picture).

I can't remember if I did. You can load deepstack in a web browser once it's running to activate it anyway. That is correct. My test setup was an old xeon that didn't support AVX. If you have a processor with avx you use "deepquestai/deepstack". Also if you have a nvidia gpu you can try...

Use the windows terminal: Example for what I used before I switched to the beta version: Download Deepstack: docker pull deepquestai/deepstack Setup the container. docker run --restart=always -e MODE=Low -e VISION-DETECTION=True -v localstorage:/datastore -p 5000:5000 --name deepstack...