Thank you for the quick reply. I downloaded ASP right before I read your post. Got it up and working, so at least I can see the cameras from my laptop remotely now and adjust some of the settings. They are all hooked up to an Amcrest 8 port NVR, but I do have a separate POE switch that I can use if necessary. Still digesting some of you post, thanks.
BrianQ
Too many night videos and other issues
Re: Too many night videos and other issues
To be honest, factory reset if the camera in fact doesn't work like my Dahua did, would be better to reset camera using a POE switch. Normally a reset over NVR can lead others that don't do it often, confused to why the NVR has lost connection with the reset camera. Once figured out password change that needs to be done in NVR it gets worked out. Having 10 different recorders and more then my share of cameras I wanted to point out some issues learned along my way.
Seeing I have more Dahua cameras and most of my resets are done on my POE Switches I keep forgetting Dahua has some extra powers that are missing in the Amcrest counter parts.
Most important for you is to get recording to a good level and not have bugs or rain for events. I think a good place to start is resetting a camera. Starting over.
What is your end goal? Anti Dither I don't think will play a role in it..
Seeing I have more Dahua cameras and most of my resets are done on my POE Switches I keep forgetting Dahua has some extra powers that are missing in the Amcrest counter parts.
Most important for you is to get recording to a good level and not have bugs or rain for events. I think a good place to start is resetting a camera. Starting over.
What is your end goal? Anti Dither I don't think will play a role in it..
Be Safe.
Re: Too many night videos and other issues
Setting Anti-Dither to a high value, such as 15-20 seconds or more, is generally a bad idea because it can cause the system to miss genuine security events. Here’s why high values can be problematic:
Delayed Response to Real Incidents: If someone enters the camera’s field of view but leaves before the end of the long Anti-Dither period, the system won’t trigger an alarm or recording. This could lead to missed incidents, as many security events are brief.
Increased Security Risk: For critical areas where response time matters (such as entrances or high-security zones), high Anti-Dither times can leave gaps in surveillance coverage, potentially compromising security.
Missed Evidence: Longer Anti-Dither times mean the system will wait before beginning to record, which might result in crucial evidence (e.g., someone’s face or vehicle license plate) being missed entirely.
Ineffective in High-Motion Areas: In areas with consistent, relevant movement (such as parking lots or office entry points), high dither settings can prevent the system from capturing important, legitimate activities, as even sustained motion might stop and restart, resetting the dither timer.
Optimal Use
To balance between reducing false alarms and capturing meaningful events, use shorter Anti-Dither times (typically between 1 and 5 seconds). This way, the system is responsive enough to capture brief but important events without overloading with non-relevant motions.
High traffic areas I would try something around 8 to 12 max. Over that just asking for real events to be missed.
Delayed Response to Real Incidents: If someone enters the camera’s field of view but leaves before the end of the long Anti-Dither period, the system won’t trigger an alarm or recording. This could lead to missed incidents, as many security events are brief.
Increased Security Risk: For critical areas where response time matters (such as entrances or high-security zones), high Anti-Dither times can leave gaps in surveillance coverage, potentially compromising security.
Missed Evidence: Longer Anti-Dither times mean the system will wait before beginning to record, which might result in crucial evidence (e.g., someone’s face or vehicle license plate) being missed entirely.
Ineffective in High-Motion Areas: In areas with consistent, relevant movement (such as parking lots or office entry points), high dither settings can prevent the system from capturing important, legitimate activities, as even sustained motion might stop and restart, resetting the dither timer.
Optimal Use
To balance between reducing false alarms and capturing meaningful events, use shorter Anti-Dither times (typically between 1 and 5 seconds). This way, the system is responsive enough to capture brief but important events without overloading with non-relevant motions.
High traffic areas I would try something around 8 to 12 max. Over that just asking for real events to be missed.
Be Safe.
Re: Too many night videos and other issues
Sorry the anti-dither suggestion raised such alarm. I assumed the risk was failing to record wildlife, not trespassers. If that's true, try making the detection area only as big as necessary. The more precise, the better. You can also configure the detection area to simulate a tripwire.
Re: Too many night videos and other issues
@check6 You're absolutely right—that's exactly what they're dealing with. At the same time, it's important to consider that others visit the forum looking for clear solutions to their own issues. That's why I try to provide comprehensive explanations, covering both the what and why of the solution, rather than just throwing out random ideas to see what sticks.
On another forum I follow, I've noticed that people are often advised to adjust camera image settings in ways that can prevent the cameras from performing reliably when they’re actually needed.
A common issue, which I’ve experienced myself, is making multiple adjustments that don’t help, and instead of resetting to default settings, continuing to make additional tweaks that only worsen the system’s performance.
I think the best plan at this point is to Reset the camera back to factory defaults and making the adjustments for IR being off so they are working with the IR Blasters or other IR cameras. Making changes with sensitivity and threshuld on a very fine level after the fact if they are still getting to many alerts or events. Again making changes to the settings that the camera come setup for by factory defaults can make things not work as good as they should..
On another forum I follow, I've noticed that people are often advised to adjust camera image settings in ways that can prevent the cameras from performing reliably when they’re actually needed.
A common issue, which I’ve experienced myself, is making multiple adjustments that don’t help, and instead of resetting to default settings, continuing to make additional tweaks that only worsen the system’s performance.
I think the best plan at this point is to Reset the camera back to factory defaults and making the adjustments for IR being off so they are working with the IR Blasters or other IR cameras. Making changes with sensitivity and threshuld on a very fine level after the fact if they are still getting to many alerts or events. Again making changes to the settings that the camera come setup for by factory defaults can make things not work as good as they should..
Be Safe.
Re: Too many night videos and other issues
I am only trying to answer the OP's original question: "What settings can i change to avoid this?" Your answer is, apparently, "none": Reset your cameras to factory defaults and use external illumination. Okay, fine. But to suggest that I am "just throwing out random ideas to see what sticks" really offends me.
Re: Too many night videos and other issues
Sorry you feel offended, That isn't my intent and the Toss out and see what sticks isn't directed at you.. As what I said in my NEXT LINE should have cleared that up.. In other words. I didn't want to just toss out a bunch of different things to see what might work at the moment.
Why at the moment, Well because with all different types of things being done and not working if someone don't change things back to default then there is no real telling what really made the change and why it might work at 1 time of day but then no longer work at another time of day...
In another post I did after my reply I didn't want to post to here as it was kind of covered. But I posted to why and what I was saying so others that may not read all post on the forum might read it and as a reasoning for my thoughts.. https://amcrest.com/forum/ip-cameras-f1 ... 17211.html
Why at the moment, Well because with all different types of things being done and not working if someone don't change things back to default then there is no real telling what really made the change and why it might work at 1 time of day but then no longer work at another time of day...
In another post I did after my reply I didn't want to post to here as it was kind of covered. But I posted to why and what I was saying so others that may not read all post on the forum might read it and as a reasoning for my thoughts.. https://amcrest.com/forum/ip-cameras-f1 ... 17211.html
Be Safe.
Re: Too many night videos and other issues
I will be back in Arkansas in a couple of weeks so i will hold off on resetting until i get there. I am trying to play with settings on ASP ss much ss possible here to learn the program find it's capabilities. I can get to the anti dithering settings and i will see what they are and make sure they are 5 or so seconds. Then I will play with the sensitivity and threshold some more and see if that helps at all.
BrianQ
BrianQ
Re: Too many night videos and other issues
I would first make the detection area only as big as necessary (it defaults to full view). The "Import" and "Export" buttons at the top of the "Devices" page offer a way to checkpoint the configuration of the selected devices.