While that will work, one thing I've learned is that there is nothing quite like a fresh restart...like you said, dummy proof and works every time.
By my estimation your current load is 576 megapixels per second. I am running 678 megapixels per second right now on an i7-3770K (not overclocked) at 40-50% usage. You are using 40 cameras however, while I am using 24. There may be a bit of a performance penalty for each incoming stream. Or maybe there isn't. I just don't know. One thing is for certain, your settings are not optimal otherwise your CPU load would be much lower.
Outgoing streaming from Blue Iris always requires expensive transcoding, even if you are streaming out h.264, which is why you see a noticeable increase in load from it. This is one of the reasons you should strive to keep usage well below 80% during normal running.
Anyway, regarding the settings, I'll expand on what fenderman said.
First of all, make sure you are streaming ordinary H.264. Not "H.264+" or "H.265". Blue Iris can't deal with those as efficiently as H.264.
Go here and note the highlighted settings.
You want hardware acceleration set to "Yes (H.264)". Do not choose the VideoPostProc option, as that will make things much worse. Restart Blue Iris for this change to take effect. Also set a live preview rate limit as I have shown. This only affects the local Blue Iris GUI which you have said you do not use much, so it should be fine to set it to 1 FPS for the best performance.
Now, each of your cameras should be set up for direct to disc recording in Blue Iris DVR format as shown by the highlighted settings here:
The last things I will mention are here:
The Max rate setting (which is maddening and should not be necessary) needs to be set a few FPS higher than the camera's actual FPS, because you get visual corruption in direct to disk recordings if the frame rate temporarily fluctuates higher than the Max rate setting.
Now, this is more personal choice than anything, but I uncheck the "Also use for BVR playback" box, which forces Blue Iris to use H.264 software decoding for clips instead of hardware decoding. This box is checked by default, but it causes some minor problems with clip playback so I turn it off for all my cameras. It is important to note that if you play multiple clips simultaneously using the timeline then having this box unchecked will make that require more CPU.
Lastly, since you use direct to disk, you don't need Blue Iris's timestamp overlay. You can delete that overlay via the Edit button at the bottom of the Video tab, as shown in the screenshot above. You should make sure your cameras keep accurate time via NTP (see NetTime - Network Time Synchronization Tool for a free NTP server you can run) and have the cameras embed their own timestamps so they always appear in recordings.
By my estimation your current load is 576 megapixels per second. I am running 678 megapixels per second right now on an i7-3770K (not overclocked) at 40-50% usage. You are using 40 cameras however, while I am using 24. There may be a bit of a performance penalty for each incoming stream. Or maybe there isn't. I just don't know. One thing is for certain, your settings are not optimal otherwise your CPU load would be much lower.
Outgoing streaming from Blue Iris always requires expensive transcoding, even if you are streaming out h.264, which is why you see a noticeable increase in load from it. This is one of the reasons you should strive to keep usage well below 80% during normal running.
Anyway, regarding the settings, I'll expand on what fenderman said.
First of all, make sure you are streaming ordinary H.264. Not "H.264+" or "H.265". Blue Iris can't deal with those as efficiently as H.264.
Go here and note the highlighted settings.
You want hardware acceleration set to "Yes (H.264)". Do not choose the VideoPostProc option, as that will make things much worse. Restart Blue Iris for this change to take effect. Also set a live preview rate limit as I have shown. This only affects the local Blue Iris GUI which you have said you do not use much, so it should be fine to set it to 1 FPS for the best performance.
Now, each of your cameras should be set up for direct to disc recording in Blue Iris DVR format as shown by the highlighted settings here:
The last things I will mention are here:
The Max rate setting (which is maddening and should not be necessary) needs to be set a few FPS higher than the camera's actual FPS, because you get visual corruption in direct to disk recordings if the frame rate temporarily fluctuates higher than the Max rate setting.
Now, this is more personal choice than anything, but I uncheck the "Also use for BVR playback" box, which forces Blue Iris to use H.264 software decoding for clips instead of hardware decoding. This box is checked by default, but it causes some minor problems with clip playback so I turn it off for all my cameras. It is important to note that if you play multiple clips simultaneously using the timeline then having this box unchecked will make that require more CPU.
Lastly, since you use direct to disk, you don't need Blue Iris's timestamp overlay. You can delete that overlay via the Edit button at the bottom of the Video tab, as shown in the screenshot above. You should make sure your cameras keep accurate time via NTP (see NetTime - Network Time Synchronization Tool for a free NTP server you can run) and have the cameras embed their own timestamps so they always appear in recordings.
You may have a memory leak do to a faulty intel hd driver...search "memory leak"
Its not odd, its supposed to work that way..you need to set it in the camera...the release notes explain, the reasons for this..
