Blue Iris

Re: "New" Setup and CPU utilization question

2023-07-29T16:36:15+00:00

Are you going to record 24/7, or only on motion or other interest? I changed my BI-setup recently to use substreams for analysis and record only alarms in high definition (3.1MP to 8k). My camera setup is single 8k Reolink, single 4.1MP Honeywell, two 3.1 MP MileSights and two 4.1 MP HikVisions. My BI-computer is Asrock DeskMini 300 with Win11, Ryzen 3 3200G cpu, 32GB RAM, single 128GB SSD as system disk and single 2.5" 500Gb 7200rpm laptop hard drive for recordings. HDD isn't even NAS-variety, just recycled it from my old Lenovo workstation laptop.

I'm using direct disk recording (h.264 or h.265 depending on camera). I have CodeProject.AI to recognise objects and have Google Coral USB. I have set camerra buffer RAM to around 18Mb per camera and using five second pre-recording. Google Coral cost me about 60€, since I had time to wait. Codeproject and Coral are somewhat experimental still.

Previously, when I used main streams for all purposes, processor load was around 35%. After changing to sub streams for analysis, processor load is around 2-3%. Difference between substream and mainstream is such big that it can differentiate between using old hardware, or buying new! It definitely shows in electricity use in common energy efficient household. Ryzen 3200G is low end cpu by all means, but with good system architecture, it's able to do some heavylifting!

So, my suggestion for this case and everyone else, check the substreams!

Edit:typo

Statistics: Posted by honkkis — Sat Jul 29, 2023 4:36 pm

Re: "New" Setup and CPU utilization question

2023-07-22T13:29:54+00:00

So i am asking for help if anyone knows where this setting is on my cameras. Lorex LNB8111-C

Found this through a search on another site:

turns out that that tho the UI is dumbed down, the underlying (Dahua) API still mostly works, so one can use commands to set things the GUI may not present, like I-frame interval (called GOP in the API):

for example, this gets you the current configuration (note that "GOP" stands for "Group of Pictures"):

http://192.168.0.73/cgi-bin/configManag ... ame=Encode

and on my Lorex E891ab, this returns the following:

table.Encode[0].ExtraFormat[0].Audio.Bitrate=64
table.Encode[0].ExtraFormat[0].Audio.Channels[0]=0
table.Encode[0].ExtraFormat[0].Audio.Compression=AAC
table.Encode[0].ExtraFormat[0].Audio.Depth=16
table.Encode[0].ExtraFormat[0].Audio.Frequency=8000
table.Encode[0].ExtraFormat[0].Audio.Pack=DHAV
table.Encode[0].ExtraFormat[0].AudioEnable=false
table.Encode[0].ExtraFormat[0].Video.resolution=704x480
table.Encode[0].ExtraFormat[0].Video.BitRate=256
table.Encode[0].ExtraFormat[0].Video.BitRateControl=CBR
table.Encode[0].ExtraFormat[0].Video.Compression=H.264
table.Encode[0].ExtraFormat[0].Video.CustomResolutionName=D1
table.Encode[0].ExtraFormat[0].Video.FPS=15
table.Encode[0].ExtraFormat[0].Video.GOP=15
table.Encode[0].ExtraFormat[0].Video.Height=480
table.Encode[0].ExtraFormat[0].Video.Pack=DHAV
table.Encode[0].ExtraFormat[0].Video.Priority=0
table.Encode[0].ExtraFormat[0].Video.Profile=High
table.Encode[0].ExtraFormat[0].Video.Quality=4
table.Encode[0].ExtraFormat[0].Video.QualityRange=6
table.Encode[0].ExtraFormat[0].Video.SVCTLayer=1
table.Encode[0].ExtraFormat[0].Video.Width=704
table.Encode[0].ExtraFormat[0].VideoEnable=true
table.Encode[0].ExtraFormat[1].Audio.Bitrate=64
table.Encode[0].ExtraFormat[1].Audio.Channels[0]=0
table.Encode[0].ExtraFormat[1].Audio.Compression=AAC
table.Encode[0].ExtraFormat[1].Audio.Depth=16
table.Encode[0].ExtraFormat[1].Audio.Frequency=8000
table.Encode[0].ExtraFormat[1].Audio.Pack=DHAV
table.Encode[0].ExtraFormat[1].AudioEnable=false
table.Encode[0].ExtraFormat[1].Video.resolution=704x480
table.Encode[0].ExtraFormat[1].Video.BitRate=1024
table.Encode[0].ExtraFormat[1].Video.BitRateControl=CBR
table.Encode[0].ExtraFormat[1].Video.Compression=H.264
table.Encode[0].ExtraFormat[1].Video.CustomResolutionName=D1
table.Encode[0].ExtraFormat[1].Video.FPS=30
table.Encode[0].ExtraFormat[1].Video.GOP=60
table.Encode[0].ExtraFormat[1].Video.Height=480
table.Encode[0].ExtraFormat[1].Video.Pack=DHAV
table.Encode[0].ExtraFormat[1].Video.Priority=0
table.Encode[0].ExtraFormat[1].Video.Profile=High
table.Encode[0].ExtraFormat[1].Video.Quality=4
table.Encode[0].ExtraFormat[1].Video.QualityRange=6
table.Encode[0].ExtraFormat[1].Video.SVCTLayer=1
table.Encode[0].ExtraFormat[1].Video.Width=704
table.Encode[0].ExtraFormat[1].VideoEnable=false
table.Encode[0].ExtraFormat[2].Audio.Bitrate=64
table.Encode[0].ExtraFormat[2].Audio.Channels[0]=0
table.Encode[0].ExtraFormat[2].Audio.Compression=AAC
table.Encode[0].ExtraFormat[2].Audio.Depth=16
table.Encode[0].ExtraFormat[2].Audio.Frequency=8000
table.Encode[0].ExtraFormat[2].Audio.Pack=DHAV
table.Encode[0].ExtraFormat[2].AudioEnable=false
table.Encode[0].ExtraFormat[2].Video.resolution=704x480
table.Encode[0].ExtraFormat[2].Video.BitRate=1024
table.Encode[0].ExtraFormat[2].Video.BitRateControl=CBR
table.Encode[0].ExtraFormat[2].Video.Compression=H.264
table.Encode[0].ExtraFormat[2].Video.CustomResolutionName=D1
table.Encode[0].ExtraFormat[2].Video.FPS=30
table.Encode[0].ExtraFormat[2].Video.GOP=60
table.Encode[0].ExtraFormat[2].Video.Height=480
table.Encode[0].ExtraFormat[2].Video.Pack=DHAV
table.Encode[0].ExtraFormat[2].Video.Priority=0
table.Encode[0].ExtraFormat[2].Video.Profile=High
table.Encode[0].ExtraFormat[2].Video.Quality=4
table.Encode[0].ExtraFormat[2].Video.QualityRange=6
table.Encode[0].ExtraFormat[2].Video.SVCTLayer=1
table.Encode[0].ExtraFormat[2].Video.Width=704
table.Encode[0].ExtraFormat[2].VideoEnable=false
table.Encode[0].MainFormat[0].Audio.Bitrate=64
table.Encode[0].MainFormat[0].Audio.Channels[0]=0
table.Encode[0].MainFormat[0].Audio.Compression=AAC
table.Encode[0].MainFormat[0].Audio.Depth=16
table.Encode[0].MainFormat[0].Audio.Frequency=8000
table.Encode[0].MainFormat[0].Audio.Mode=0
table.Encode[0].MainFormat[0].Audio.Pack=DHAV
table.Encode[0].MainFormat[0].AudioEnable=false
table.Encode[0].MainFormat[0].Video.resolution=3840x2160
table.Encode[0].MainFormat[0].Video.BitRate=4096
table.Encode[0].MainFormat[0].Video.BitRateControl=CBR
table.Encode[0].MainFormat[0].Video.Compression=H.264
table.Encode[0].MainFormat[0].Video.CustomResolutionName=3840x2160
table.Encode[0].MainFormat[0].Video.FPS=15
table.Encode[0].MainFormat[0].Video.GOP=30
table.Encode[0].MainFormat[0].Video.Height=2160
table.Encode[0].MainFormat[0].Video.Pack=DHAV
table.Encode[0].MainFormat[0].Video.Priority=0
table.Encode[0].MainFormat[0].Video.Profile=Main
table.Encode[0].MainFormat[0].Video.Quality=4
table.Encode[0].MainFormat[0].Video.QualityRange=6
table.Encode[0].MainFormat[0].Video.SVCTLayer=1
table.Encode[0].MainFormat[0].Video.Width=3840
table.Encode[0].MainFormat[0].VideoEnable=true
table.Encode[0].MainFormat[1].Audio.Bitrate=64
table.Encode[0].MainFormat[1].Audio.Channels[0]=0
table.Encode[0].MainFormat[1].Audio.Compression=AAC
table.Encode[0].MainFormat[1].Audio.Depth=16
table.Encode[0].MainFormat[1].Audio.Frequency=8000
table.Encode[0].MainFormat[1].Audio.Mode=0
table.Encode[0].MainFormat[1].Audio.Pack=DHAV
table.Encode[0].MainFormat[1].AudioEnable=false
table.Encode[0].MainFormat[1].Video.resolution=3840x2160
table.Encode[0].MainFormat[1].Video.BitRate=4096
table.Encode[0].MainFormat[1].Video.BitRateControl=CBR
table.Encode[0].MainFormat[1].Video.Compression=H.264
table.Encode[0].MainFormat[1].Video.CustomResolutionName=3840x2160
table.Encode[0].MainFormat[1].Video.FPS=15
table.Encode[0].MainFormat[1].Video.GOP=30
table.Encode[0].MainFormat[1].Video.Height=2160
table.Encode[0].MainFormat[1].Video.Pack=DHAV
table.Encode[0].MainFormat[1].Video.Priority=0
table.Encode[0].MainFormat[1].Video.Profile=Main
table.Encode[0].MainFormat[1].Video.Quality=4
table.Encode[0].MainFormat[1].Video.QualityRange=6
table.Encode[0].MainFormat[1].Video.SVCTLayer=1
table.Encode[0].MainFormat[1].Video.Width=3840
table.Encode[0].MainFormat[1].VideoEnable=true
table.Encode[0].MainFormat[2].Audio.Bitrate=64
table.Encode[0].MainFormat[2].Audio.Channels[0]=0
table.Encode[0].MainFormat[2].Audio.Compression=AAC
table.Encode[0].MainFormat[2].Audio.Depth=16
table.Encode[0].MainFormat[2].Audio.Frequency=8000
table.Encode[0].MainFormat[2].Audio.Mode=0
table.Encode[0].MainFormat[2].Audio.Pack=DHAV
table.Encode[0].MainFormat[2].AudioEnable=false
table.Encode[0].MainFormat[2].Video.resolution=3840x2160
table.Encode[0].MainFormat[2].Video.BitRate=4096
table.Encode[0].MainFormat[2].Video.BitRateControl=CBR
table.Encode[0].MainFormat[2].Video.Compression=H.264
table.Encode[0].MainFormat[2].Video.CustomResolutionName=3840x2160
table.Encode[0].MainFormat[2].Video.FPS=15
table.Encode[0].MainFormat[2].Video.GOP=30
table.Encode[0].MainFormat[2].Video.Height=2160
table.Encode[0].MainFormat[2].Video.Pack=DHAV
table.Encode[0].MainFormat[2].Video.Priority=0
table.Encode[0].MainFormat[2].Video.Profile=Main
table.Encode[0].MainFormat[2].Video.Quality=4
table.Encode[0].MainFormat[2].Video.QualityRange=6
table.Encode[0].MainFormat[2].Video.SVCTLayer=1
table.Encode[0].MainFormat[2].Video.Width=3840
table.Encode[0].MainFormat[2].VideoEnable=true
table.Encode[0].MainFormat[3].Audio.Bitrate=64
table.Encode[0].MainFormat[3].Audio.Channels[0]=0
table.Encode[0].MainFormat[3].Audio.Compression=AAC
table.Encode[0].MainFormat[3].Audio.Depth=16
table.Encode[0].MainFormat[3].Audio.Frequency=8000
table.Encode[0].MainFormat[3].Audio.Mode=0
table.Encode[0].MainFormat[3].Audio.Pack=DHAV
table.Encode[0].MainFormat[3].AudioEnable=false
table.Encode[0].MainFormat[3].Video.resolution=1280x720
table.Encode[0].MainFormat[3].Video.BitRate=1024
table.Encode[0].MainFormat[3].Video.BitRateControl=CBR
table.Encode[0].MainFormat[3].Video.Compression=H.264
table.Encode[0].MainFormat[3].Video.CustomResolutionName=720P
table.Encode[0].MainFormat[3].Video.FPS=15
table.Encode[0].MainFormat[3].Video.GOP=30
table.Encode[0].MainFormat[3].Video.Height=720
table.Encode[0].MainFormat[3].Video.Pack=DHAV
table.Encode[0].MainFormat[3].Video.Priority=0
table.Encode[0].MainFormat[3].Video.Profile=High
table.Encode[0].MainFormat[3].Video.Quality=4
table.Encode[0].MainFormat[3].Video.QualityRange=6
table.Encode[0].MainFormat[3].Video.SVCTLayer=1
table.Encode[0].MainFormat[3].Video.Width=1280
table.Encode[0].MainFormat[3].VideoEnable=true
table.Encode[0].SnapFormat[0].Audio.Bitrate=64
table.Encode[0].SnapFormat[0].Audio.Compression=G.711A
table.Encode[0].SnapFormat[0].Audio.Depth=16
table.Encode[0].SnapFormat[0].Audio.Frequency=8000
table.Encode[0].SnapFormat[0].Audio.Pack=DHAV
table.Encode[0].SnapFormat[0].AudioEnable=false
table.Encode[0].SnapFormat[0].Video.resolution=3840x2160
table.Encode[0].SnapFormat[0].Video.BitRate=5120
table.Encode[0].SnapFormat[0].Video.BitRateControl=VBR
table.Encode[0].SnapFormat[0].Video.Compression=MJPG
table.Encode[0].SnapFormat[0].Video.CustomResolutionName=3840x2160
table.Encode[0].SnapFormat[0].Video.FPS=0.100000
table.Encode[0].SnapFormat[0].Video.GOP=60
table.Encode[0].SnapFormat[0].Video.Height=2160
table.Encode[0].SnapFormat[0].Video.Pack=DHAV
table.Encode[0].SnapFormat[0].Video.Priority=0
table.Encode[0].SnapFormat[0].Video.Profile=Main
table.Encode[0].SnapFormat[0].Video.Quality=5
table.Encode[0].SnapFormat[0].Video.QualityRange=6
table.Encode[0].SnapFormat[0].Video.SVCTLayer=1
table.Encode[0].SnapFormat[0].Video.Width=3840
table.Encode[0].SnapFormat[0].VideoEnable=true
table.Encode[0].SnapFormat[1].Audio.Bitrate=64
table.Encode[0].SnapFormat[1].Audio.Compression=G.711A
table.Encode[0].SnapFormat[1].Audio.Depth=16
table.Encode[0].SnapFormat[1].Audio.Frequency=8000
table.Encode[0].SnapFormat[1].Audio.Pack=DHAV
table.Encode[0].SnapFormat[1].AudioEnable=false
table.Encode[0].SnapFormat[1].Video.resolution=3840x2160
table.Encode[0].SnapFormat[1].Video.BitRate=5120
table.Encode[0].SnapFormat[1].Video.BitRateControl=VBR
table.Encode[0].SnapFormat[1].Video.Compression=MJPG
table.Encode[0].SnapFormat[1].Video.CustomResolutionName=3840x2160
table.Encode[0].SnapFormat[1].Video.FPS=0.100000
table.Encode[0].SnapFormat[1].Video.GOP=60
table.Encode[0].SnapFormat[1].Video.Height=2160
table.Encode[0].SnapFormat[1].Video.Pack=DHAV
table.Encode[0].SnapFormat[1].Video.Priority=0
table.Encode[0].SnapFormat[1].Video.Profile=Main
table.Encode[0].SnapFormat[1].Video.Quality=5
table.Encode[0].SnapFormat[1].Video.QualityRange=6
table.Encode[0].SnapFormat[1].Video.SVCTLayer=1
table.Encode[0].SnapFormat[1].Video.Width=3840
table.Encode[0].SnapFormat[1].VideoEnable=true
table.Encode[0].SnapFormat[2].Audio.Bitrate=64
table.Encode[0].SnapFormat[2].Audio.Compression=G.711A
table.Encode[0].SnapFormat[2].Audio.Depth=16
table.Encode[0].SnapFormat[2].Audio.Frequency=8000
table.Encode[0].SnapFormat[2].Audio.Pack=DHAV
table.Encode[0].SnapFormat[2].AudioEnable=false
table.Encode[0].SnapFormat[2].Video.resolution=3840x2160
table.Encode[0].SnapFormat[2].Video.BitRate=5120
table.Encode[0].SnapFormat[2].Video.BitRateControl=VBR
table.Encode[0].SnapFormat[2].Video.Compression=MJPG
table.Encode[0].SnapFormat[2].Video.CustomResolutionName=3840x2160
table.Encode[0].SnapFormat[2].Video.FPS=0.100000
table.Encode[0].SnapFormat[2].Video.GOP=60
table.Encode[0].SnapFormat[2].Video.Height=2160
table.Encode[0].SnapFormat[2].Video.Pack=DHAV
table.Encode[0].SnapFormat[2].Video.Priority=0
table.Encode[0].SnapFormat[2].Video.Profile=Main
table.Encode[0].SnapFormat[2].Video.Quality=5
table.Encode[0].SnapFormat[2].Video.QualityRange=6
table.Encode[0].SnapFormat[2].Video.SVCTLayer=1
table.Encode[0].SnapFormat[2].Video.Width=3840
table.Encode[0].SnapFormat[2].VideoEnable=true

then this URL will SET the gop (for the main pulled rtsp stream) to 15 (was 30)

http://192.168.0.73/cgi-bin/configManag ... deo.GOP=15

Statistics: Posted by Thixotropic — Sat Jul 22, 2023 1:29 pm

Re: "New" Setup and CPU utilization question

2022-03-28T23:52:06+00:00

Looks like these Lorex do not have the setting, unless its buried somewhere else!

Capture.JPG

Sorry for posting this old thread. Did you ever figure this out? I have a bunch of Lorex cameras as well and cannot change the keyframe/frame interval since there is no setting in the cameras for it. My ratios at always at 0.50 no matter what I do.

Statistics: Posted by IronSheepdog — Mon Mar 28, 2022 11:52 pm

Re: "New" Setup and CPU utilization question

2020-06-10T20:19:43+00:00

I have looked and Googled for the better part of a couple weeks now and cannot find any reference to Frame Intervals, key frames, or anything else they go by on my cameras. So i am asking for help if anyone knows where this setting is on my cameras.

Vodoo magic...

I'm an engineer and ever since middle school I have found unit analysis very helpful. If you look at the units on a number (ie km/hr) you can usually easily figure out how to get hrs by simple * and /.

The reason I bring this up is that I am ALWAYS annoyed by the lack of clarity on units in this setting in particular.

I have always heard that it is the interval that key frames are saved. So if you have raw 30 frames per second stream, then perhaps you want 1 key frame for every 30 real frames (or one key frame every second).

So what are the units?????? Who the heck knows. I never understood.

Statistics: Posted by HeneryH — Wed Jun 10, 2020 8:19 pm

Re: "New" Setup and CPU utilization question

2020-06-10T20:06:47+00:00

Looks like these Lorex do not have the setting, unless its buried somewhere else!

Statistics: Posted by brokenarrow03 — Wed Jun 10, 2020 8:06 pm

Re: "New" Setup and CPU utilization question

2020-06-10T18:59:10+00:00

I wish I could help. Mine aren't Lorex and from my (much shorter time spent) Googling, I came up dry too. It looks like they just want you to use their NVR - of course Perhaps someone else here has already run into this.

While it won't help you at all, this is what mine looks like:

Statistics: Posted by Matts1984 — Wed Jun 10, 2020 6:59 pm

Re: "New" Setup and CPU utilization question

2020-06-10T16:43:49+00:00

I have looked and Googled for the better part of a couple weeks now and cannot find any reference to Frame Intervals, key frames, or anything else they go by on my cameras. So i am asking for help if anyone knows where this setting is on my cameras.

Lorex LNB8111-C

Thanks

Statistics: Posted by brokenarrow03 — Wed Jun 10, 2020 4:43 pm

Re: "New" Setup and CPU utilization question

2020-05-22T18:13:06+00:00

You bet, that is a dramatic improvement. Try it and make sure you don't have any unacceptable consequences but for me - I don't. You certainly have higher quality cameras than I do.

I do see that you can improve your keyframes though. Per the BI document, they should be approximately 1/s and you're around 2/s. This is a setting somewhere directly on the cameras that would have to be updated. My understanding is the FPS in your screenshot is fine (around 15) but the "key" should be as close to 1 as possible. The lingo in your cameras interface may vary but for mine it is called "Frame Interval". Try setting that to the same value as your FPS (by default my cameras did not set this according to BI recommendation). If you're able to tweak that, your CPU should drop even more. Additionally, you should see the numbers in the Status screen update in real time as you tweak the cameras so you'll know quickly if you made it worse or better.

Statistics: Posted by Matts1984 — Fri May 22, 2020 6:13 pm

Re: "New" Setup and CPU utilization question

2020-05-21T23:27:42+00:00

Here are the pictures you requested. It seems that after selecting the "Limit Decoding unless required" the CPU dropped from 85% down to about 30% with all 6 cameras running. I appreciate your help.

Statistics: Posted by brokenarrow03 — Thu May 21, 2020 11:27 pm

Re: "New" Setup and CPU utilization question

2020-05-21T21:31:14+00:00

Thank you for the replies thus far. I did upgrade to the full license after my demo period went so well with the 1 camera. I will post some screenshots when I get a second.

Statistics: Posted by brokenarrow03 — Thu May 21, 2020 9:31 pm

Re: "New" Setup and CPU utilization question

2020-05-20T23:51:50+00:00

I REALLY hate to sound like someone who shall forever remain nameless, but... you can get an awesome BI machine that can handle many cameras for less than a grand. Way less.

Absolutely. You can, for example, get decent used servers (rack style, usually) for very reasonable prices on eBay, way less than the cost of a build. Even building a box with all new parts you can come in way under $1000.

I built my BI box only because I had about 80% of the pieces laying around and because a friend sold me an extra i7-7700 3.6 GHz he had for practically nothing. If I had it to do over again I'd set my budget and then go to eBay or the Dell refurbished merchandise store. I wouldn't build a whole new PC again.

I've often wondered if a fully-loaded Raspberry 4 would work as an entry-level BI box. With the new sub-streaming feature I think it makes it more feasible, but probably only for a small set of cameras, maybe 2 to 4 medium-resolution cams.

Statistics: Posted by Thixotropic — Wed May 20, 2020 11:51 pm

Re: "New" Setup and CPU utilization question

2020-05-20T23:16:24+00:00

I REALLY hate to sound like someone who shall forever remain nameless, but... you can get an awesome BI machine that can handle many cameras for less than a grand. Way less.

Statistics: Posted by HeneryH — Wed May 20, 2020 11:16 pm

Re: "New" Setup and CPU utilization question

2020-05-20T14:55:13+00:00

I don't think it's fair to say terrible but no, it's not the newest. Since they are Xeons they don't support QuickSync but I believe can still do the job. There may be a few tradeoffs that can easily be made vs dropping a large sum on a completely new system. It may in the end be worth looking at a CPU upgrade but the OP is likely still going to be limited by what the mobo is capable of. By the looks of it, for an LGA1156 socket, the highest is a Xeon X3480 which appears in short supply so it quite expensive compared to an X3470... and then it's not that much of a change.

My recommendation is to continue trying to tweak, I still think you can make it. If not, since you have the drives you can generally find old (well less old than what you have) servers online for pretty cheap. My dual-socket server with no drives cost $200.

Statistics: Posted by Matts1984 — Wed May 20, 2020 2:55 pm

Re: "New" Setup and CPU utilization question

2020-05-20T14:24:06+00:00

That CPU is pretty old and fares poorly in the benchmarks

Other names: Intel(R) Xeon(R) CPU X3440 @ 2.53GHz
CPU First Seen on Charts: Q4 2009
Overall Rank: 1207

and it may not even support QuickSync. (from what I see it doesn't)

All in all, this seems like a TERRIBLE choice for BI.

Statistics: Posted by HeneryH — Wed May 20, 2020 2:24 pm

Re: "New" Setup and CPU utilization question

2020-05-20T12:19:07+00:00

I have a few thoughts for you. First, you mentioned BI Demo mode... have you upgraded that to a full licensed version? I know some features are disabled in demo and that could make a difference. Second, could you share the output from the Status > Cameras tab? What I'm referring to is below, the most important content is highlighted in red if you don't want to put up a full screenshot. This info can help a lot.

Other than tweaking settings that might be discovered from that information, if you are POSITIVE you're doing Direct to Disk, the biggest optimization I have found beyond that is to turn on 'Limit Decoding unless required'. This is found in the settings for each camera at the bottom of the 'Video' tab. What this setting is intended to do is for BI to only decode the keyframes received from the camera(s) which in theory should be one per second (we can verify if you post the information requested above). As it stands now, your server is actually decoding 15 frames per second, per camera. With 6 cameras you're talking 90 frames per second or with this setting you can make that 6. The system will automatically ramp up if you are live streaming one of the feeds so it will cycle up if needed to your default frame rate. Recorded videos are also captured at your default frame rate since you're doing Direct to Disk. In my experience, having this decode down to 1 fps still allows my BI motion detecting to work perfectly fine though I understand this could vary per use case. Ultimately, the system just doesn't need to process near cinema quality video (24 fps) if it's just chugging along watching for movement. If you're actually watching the stream in the console, UI3, or mobile app... it spins up instantly. If I do have the console open and the mosaic of all my cameras are displayed - but none are selected - they update at the slower 1 fps which actually surprisingly isn't THAT bad. My system is a bit different than yours but I run typically around 10% and ramp up to 30-40% when I give it a demand.

I think we can probably get your current system tweaked to run your cameras. Alternatively, eBay is your friend. I just purchased four new (to me) septacore Xeon processors for $20 total. I only need 2 but it was a batch of 4 so I figured I had some options if one or two didn't work. They are not installed yet though.

Statistics: Posted by Matts1984 — Wed May 20, 2020 12:19 pm