I tried 5.6.0 and 5.6.0.1 and the GUI lost all triggers and confirmations and kept "not responding". Mobile App was fine, so I emailed support and rolled back to 5.5.9.6, are you not having issues?Also, this error which is bogus as the AI is running and works perfect. Ken has told me this will be fixed in 5.6.0.2
View attachment 136943
Essential to ensure your sub-stream is of sufficient quality to identify objects (both resolution and bit-rate).When checked, it uses the camera main stream. But as the AI resizes to 640px anyhow, it needs additional CPU power for resizing before analyzing. So in most cases feeding the sub stream is better.
I tried 5.6.0 and 5.6.0.1 and the GUI lost all triggers and confirmations and kept "not responding". Mobile App was fine, so I emailed support and rolled back to 5.5.9.6, are you not having issues?
For me to understand please, is the resolution shown in the Blue Iris Status alert image (example attached) normally different the 640x480 to which you refer? On my system, the image resolution in BI Status is different for different cameras. Where possible in the camera, I use 640x480 for the substream to hopefully save CPU time. Please clarify.Essential to ensure your sub-stream is of sufficient quality to identify objects (both resolution and bit-rate).
Same here, you may also notice similar errors to the ones below. I sent the details to Ken.I tried 5.6.0 and 5.6.0.1 and the GUI lost all triggers and confirmations and kept "not responding". Mobile App was fine, so I emailed support and rolled back to 5.5.9.6, are you not having issues?
Your sub-stream configuration is fine. Nothing to worry about, there will be some minor image size differences in the alerts, that is to be expected as they are re-sized.For me to understand please, is the resolution shown in the Blue Iris Status alert image (example attached) normally different the 640x480 to which you refer? On my system, the image resolution in BI Status is different for different cameras. Where possible in the camera, I use 640x480 for the substream to hopefully save CPU time. Please clarify.
Thanks
View attachment 136988
View attachment 136989
Nope mine is running fine on 5.6.0.1 using CPU CodeProject AI
OK thanks spammenotinoz but I guess the argument that using 640x480 to save on CPU cycles by not re-encoding for AI analysis is not valid then? It looks like images are still re-encoded to a 16:9 format?Your sub-stream configuration is fine. Nothing to worry about, there will be some minor image size differences in the alerts, that is to be expected as they are re-sized.
Wow is right...even CPU times are FAST ! Also this time I did NOT uninstall AI but just installed over previous version with BI 5.6.0.2 running. Everything went smooth !
They do have plans on adding Intel GPU support.Do they have plans to make use of the onboard intel GPUs or is there no point as they are gutless
Mike do you run the docker version or windows installable version? Might give this a go over the weekend, have an i5-6500, 16Gb RAM but additional GPU just what’s on the CPU.
Only because you mention Intel specifically . . . earlier in this thread you referenced the post (which I'll copy here) that they were FIRST going to use DirectML that would support more than just Intel (AMD is the one of particular interest to me). Do you know if that is already done and already contributed to the better "CPU" performance, or if they skipped that to jump to CUDA support, or ???They do have plans on adding Intel GPU support.
I think they were working on Intel and NVidia support in parallel and Nvidia won. Below are some posts related to Intel GPU supportOnly because you mention Intel specifically . . . earlier in this thread you referenced the post (which I'll copy here) that they were FIRST going to use DirectML that would support more than just Intel (AMD is the one of particular interest to me). Do you know if that is already done and already contributed to the better "CPU" performance, or if they skipped that to jump to CUDA support, or ???
View attachment 137177