- Aug 11, 2014
- 701
- 685
Blue Iris Update Bot updated Blue Iris Updates (64 bit) with a new update entry:
5.8.9.5
Read the rest of this update entry...
5.8.9.5
New stream.
Read the rest of this update entry...
New stream.
New stream.
New stream.
Same!Updating to 5.8.9.7 causes "clips: disk can't keep up" errors. Had to roll back to 5.8.9.6.
Updating to 5.8.9.7 causes "clips: disk can't keep up" errors. Had to roll back to 5.8.9.6.
Maybe it has something to do with your shiny new gaming machine (i7-14700F - 32GB DDR5 Memory) while mine is an old piece of junk (i7-4790 - 16GB Memory).I upgraded about 5 hours ago. No issues so far.
New stream.
Maybe it has something to do with your shiny new gaming machine (i7-14700F - 32GB DDR5 Memory) while mine is an old piece of junk (i7-4790 - 16GB Memory).
Same here.Updating to 5.8.9.7 causes "clips: disk can't keep up" errors. Had to roll back to 5.8.9.6.
New stream.
Just installed an AXIS P3245-LVE camera. I used the same parameters as my other cameras for the AI. No matter what I do, I keep getting "AI not responding". Is there something that I need to do through AXIS IP Client? Any help or directions will be appreciated (I've already searched the forums before I asked this question).
I assume you mean CodeProject AI and this error is in BI?
If so, BI simply takes the video feed from the camera and if the video is showing in BI, then it isn't an issue with the camera itself.
Try shutting CodeProject service down and restarting and see if that gets it working.
Tried shutting down and restarting CodeProject A, still I get that the AI is not responding.
This probably isn't the correct thread to continue this troubleshooting - but what are your AI make times? Maybe you have saturated the system and it can't handle one more camera?
After you shut down CodeProject and restarted, did you then shut down BI and restart it?
New stream.
Windows Location API integration for mobile systems, Other minor enhancements and bug fixes.
I still got the "disk can't keep up error" on 5.8.9.8 but so far only when my cam did a scheduled restart. I'll ask support.
UPDATE: this issue was fixed in the 5.8.9.9 update.
View attachment 192933