The obvious things to check are what everything has in common aside from Blue Iris.
I always say start simple. It will get complicated soon enough all by itself. LOL
You've determined that signal loss doesn't seem to actually be occurring on the network, but is somehow being affected to the extent that Blue Iris is confused about what to do with it -- if streams are indeed getting to it. Without going back through your entire post for a reference to how you are directly accessing the cameras to confirm their online state, you may want to do a simple test at the same switch as the Blue Iris machine is using and try some VLC RTSP sessions of a 'no signal' camera from a laptop to make sure there's an active stream there on port 554 vs. a port 80 web interface session. If there's a clean RTSP stream with no errors, then Blue Iris should be receiving the same input and that would at least settle that.
Another very simple test for possible network issues coming into play is pick a trouble camera and just ping the snot out of it for a few hours with large packets, say 2048 or 4096 bytes. They should still be in the ~10ms range if things are really clean. There should be zero loss even if there is some lag or congestion. Again, plug into the same switch as Blue Iris with a laptop and go for it.
Do as many general network performance tests as may be applicable to how a clean and efficient IP video network should perform with or without Blue Iris or any other VMS platform. If everything comes up roses there, on to the rig, its components and their configuration compatibility, and any overkill features and functions not necessary for basic Blue Iris functionality including CPAI and any multi-functional GPU configurations that may just be banging into each other. Break it down to only the requirements needed by Blue Iris to efficiently and effectively run a handful of cameras as would normally be expected. Re-introduce the other stuff once a trouble free solid foundation has been established. You'll likely find the problem source sooner than later.
Review configurations. Certain little things matter, others don't. Again, keep it as simple as possible for the troubleshooting. Ensure the correct CPU/GPU references are in place, properly recognized and functioning appropriately. Make sure camera webUI based configuration settings match the corresponding Blue Iris configurations.
All basic stuff. Can take time with lots of cameras, though this particular issue affecting all cameras is more than likely a server issue. Still, start with one camera at a time. If you find a fix for one, you've probably found it for others as well.
A couple things out of the gate. I don't see sub streams in the configuration examples. I see limit decoding checked. I see 'default' for processor type. You list any number of possibilities there in your system specs. Who's on first?
Another item I noticed is a defrag schedule. Not something you want to do with the Blue Iris database and storage structure. Hopefully it is limited to non-Blue Iris storage devices but could really disrupt things if it's trying to trim and defrag BI drives. And speaking of storage, depending on how things are set up management-wise, non-alignment with how BI likes to see things and dynamically manage them usually creates issues and can waste resources as well.
A.C. power stability. All good? Maybe some fluctuation up there on the hill? POE all good? No excessive wiring lengths and solid copper ethernet cabling used everywhere? No CCA aluminum bargain junk CatX wiring anywhere mission critical?
Lastly, time sync. I noticed Windows Time running. Are we all on the same page there? Time sync is very important.
Simplify what you're expecting from the rig. Break it down. Get rid of anything that Blue Iris doesn't need to effectively run your handful of cameras reliably in a basic surveillance configuration 24x7x365..., or at least maybe for a whole day for starters?
My drastic suggestion would be to get Blue Iris off the existing box and all the other clutter and into a basic Win10 Pro Intel iCore rig with a modest i7 8500, 32GB RAM, SSD of your choice and a big-ass spinner for initial storage with a couple more on the side if you need the archives. It would be much happier -- and so would you!
Anyway, just my $.02 and some things to chew on.
Statistics: Posted by Pogo — Wed Mar 13, 2024 2:34 am
]]>