Back to your car analogy, doing something that you know will make the car stall while on the highway wouldn't be very smart would it. If the car had a self destruct button would you push it?
In the case of the metaphorical car there are things your could do to increase it's performance, there's nothing you can do here.
Honestly the best thing you can do is going to be reset everything back to the default and then make small changes to the settings and try not to change too many things at once. Think of adjusting it more like a science experiment where you only change one thing at a time, keep some notes about what you did and whether it made the picture better or worse or introduced other problems. While you're at it do some searching to learn about what each setting does. Leave the frame rate and bit rate and sub stream resolution alone to identity if there's anything more than your settings causing your issue, otherwise you're just wasting everyone's time.
Life isn't a video game, high frame rates aren't very useful in most security applications they just result is a lot of wasted storage meaning you wipe out your recordings a lot sooner. 10-15 FPS is actually pretty common. You aren't likely to benefit from anything above 30fps. The substream's purpose is to provide a lower resolution image that can be used for things like displaying multiple cameras on the NVR's video output or when viewing all the cams at once on your computer without using up all the resources available.
The cameras and NVR each only have a certain amount of CPU and RAM. It's a balance between certain features as to what the camera or NVR can do. There are network and storage bottle necks too even if they're internal to the NVR. Only so many mbps of data are going to get written to the hard drive, this is arguably the most important spec on an NVR. When you enable motion detection for example it drives up the CPU usage. If you increase the frame rate or bit rate it increases the storage usage and CPU usage and network bandwidth used. Some codec are more storage intensive others are more cpu intensive. Some settings on the camera will actually disable others that it doesn't have the resources for. The composition of your image can even effect resource use and lead to camera blackouts in some cases. Your Pixel 2 XL has way more ram and processing power than the camera or nvr. There's likely some combination of settings that would work at 60fps, but trying to find it is completely pointless and would mean disabling all sorts of far more useful functions.
If you try to record only on motion detection you'll miss events you wish you recorded. Alternatives to the traditional motion detection like line crossing or intrusion result in far fewer false alerts.
First, thanks for taking the time to explain some things.
Your comments on the car analogy are the first time anyone here has implied that the cams are not actually INTENDED to be run at that high of frame rate. That's what i was looking for before, some confirmation on the specifications. If the 1080p @ 60fps rating is a theoretical image resolution and frame rate under only the most perfect ideal conditions, then that is something i wouldn't have known having no knowledge of this industry. All i know to do is compare it to things I'm familiar with, like TV and phone camera resolutions and frame rates.
Back to the troubleshooting:
If you look at my past posts, I've actually done precisely what you are recommending. Perhaps it's not clear, and it's definitely spread out over multiple posts now. But I've restored both cams to default settings and methodically gone through the image settings one by one so as to isolate a single variable (i have a bit of science background
) during the troubleshooting. What i haven't done is restore the whole NVR to default, mainly because i really haven't changed many non-cam settings on it at all. Like i said before, i haven't played around too much. Almost all the settings I've changed have been in the camera image and encoding screens, both of which are back to default now. What you say is interesting about the MD. I can remove that and just do continuous to see how that responds, but IIRC i had the issue before setting MD. I actually forgot i planned to do continuous anyway since i now have 2MP cams and an NVR capable of up to 16?GB storage.
I get what you're saying in the hardware side. But I'm running two 2MP cameras on a 5216 4k. This thing is supposed to be capable of running 16 4k cams simultaneously. Do i think it actually could? Hell no. But i did expect it to not even bat an eyelash at a mere two 2MP cams, regardless of settings. The specs on the NVR say it should be able to handle this no problem, which is why all my questing is coming about. I wasn't only looking at the cam specs.
Not tonight, probably tomorrow night, I'm going to reset all the MD settings and go back to continuous. If that has no affect, I'm going to upgrade firmware (assuming it needs to be). Then if all else fails, I'll fully restore the NVR. That removes all doubt on the software end, right?
Also, do you happen to have any feedback on what exactly is going on with those light artifacts in the backdoor cam? Any way to get rid of them?
Thanks
Sent from my Pixel 2 XL using Tapatalk
