I think I understand the overall gist of the "Limit decoding unless required" feature, and its possible impact on motion detection.
This brings up two questions...
1) If you have a camera that's recording 24/7 with no motion detection or zones set up, would there be any reason(s) not to use the limit decoding feature? From what I've read the main side-effects are the possibility of reduced sensitivity for motion detection and the potential for some CPU spiking if the camera is in a group that activates/triggers along with the initial camera.
I may not have that exactly right, but none of my cams are linked or co-triggered, they're all independent from each other.
The one downside to using this feature is that on most of my cameras, when I enable it, the image becomes still and pixelated after a while and it doesn't recover until it's made fullscreen. Is that normal?
2) As I understand it, the limit decoding feature is intended to help reduce CPU load. My system runs at 16 to 22 percent CPU utilization, barely loafing along...should I even care about this?
Limit decoding unless required
- Thixotropic
- Posts: 747
- Joined: Wed Sep 04, 2019 7:20 pm
- Location: Low-Earth Orbit
Limit decoding unless required
Blue Iris 5.x x64 | Windows 10 Pro x64 | 16GB RAM | i7-7700 3.6 GHz | 1TB HDD | 2TB RAID NAS | 9 Cameras | Almost Dual NIC | 2KVA UPS
Re: Limit decoding unless required
I think that is one setting to leave alone.
Have you tried the new sub-stream method of reducing cpu usage ? I managed to get two out of three cams working this way (curses to you Foscam), and it dropped cpu usage from 19% to around 9% on my measly i5-3330 cpu. Nice
Have you tried the new sub-stream method of reducing cpu usage ? I managed to get two out of three cams working this way (curses to you Foscam), and it dropped cpu usage from 19% to around 9% on my measly i5-3330 cpu. Nice
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
- Thixotropic
- Posts: 747
- Joined: Wed Sep 04, 2019 7:20 pm
- Location: Low-Earth Orbit
Re: Limit decoding unless required
I haven't done anything with substreams yet. I probably will as I add more cams but for now it seems like I have CPU cycles to spare.
Blue Iris 5.x x64 | Windows 10 Pro x64 | 16GB RAM | i7-7700 3.6 GHz | 1TB HDD | 2TB RAID NAS | 9 Cameras | Almost Dual NIC | 2KVA UPS
Re: Limit decoding unless required
I did get substream to work in my older Foscam 9826p v2, But, the main stream stopped! I haven't figured that out, and I just gave up on it.
Re: Limit decoding unless required
MikeBwca: Same here with it stopping the main stream. Glad it wasn't just me, thought I was losing the plot
I'll start a new thread about it.
I'll start a new thread about it.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Limit decoding unless required
Just to pile on... I used to use Limit Decoding - and was very happy with it. But I started to have issues when viewing cameras in the console. While Limit Decoding should have updated the image once per second, it would often fall minutes behind on SOME cameras. Anyway, I changed to substreams and am very happy now.
I guess I could go substream AND Limit Decoding but I'm under 10% until I switch to main streams so it's not worth it. System is running smoothly.
I guess I could go substream AND Limit Decoding but I'm under 10% until I switch to main streams so it's not worth it. System is running smoothly.
Blue Iris 5.9.9.x | Server 2025 VM | Xeon E5-2660 v3 @ 2.60GHz - 32 Cores | 48GB RAM | 8TB RAID | Sophos UTM WAF | Mostly various SV3C Cameras