VIP/Dahua - how to reset (and make sense of the settings...)

Jeff12345

n3wb
Jul 27, 2019
13
0
Australia
Greetings IPCT folk.
I have a VIP/rebranded Dahua NVR and cameras.
I've had nothing but trouble with this thing.
Constant false alarms - even when there is nothing in the playback.
Inability to reliably identify humans (vs shadows, vehicles, etc.) - even though humans have been nominated, not vehicles, but processing power is still going to putting boxes around vehicles.
Hopeless playback (hallucinations from other times when moving the tiny red square).
Basically completely unreliable/unusable.
Settings are so needlessly complicated that it's impossible to know which Settings to go to to fix the numerous problems.

Question: can anyone direct me to a simplified guide to THE BASIC Settings?
Also, is it possible to do a full reset to eliminate what are obviously incorrect Settings that I can't track down individually?
Firmware is supposedly the most recent.
Seriously, how can VIP sell this rubbish. I've paid over $1,000 for this shit.

Thanks in advance.
 
The cameras came with the VIP NVR. They supposedly have 'AI', but I use actual AI, and I know that if VIP does have actual AI, it would have no trouble whatsoever distinguishing between a shadow and a human...
The cameras are VIP Pro AI, Turret IP cameras, 8MP, 2.8mm, model H08-VSIPP-8DG-ID4.
NVR is model G43_NVR8PRO-1
 
Last edited:
Are you making the changes in the NVR or the camera GUI?

Have you turned off Motion Detection and Smart Motion Detection and using only Smart Plan and IVS?

Some model numbers and screenshots of your settings would be helpful.
 
Are you making the changes in the NVR or the camera GUI?

Have you turned off Motion Detection and Smart Motion Detection and using only Smart Plan and IVS?

Some model numbers and screenshots of your settings would be helpful.
wittaj, thanks for the reply. And no, I haven't turned off motion detection because for someone operating at my level of expertise, that would seem to be exactly what I want... And I don't recall coming across 'Smart motion detection' but I'll go in and see if I can find it. And the number of screenshots would be enormous, given what I'm complaining about re the complexity in Settings...
Can I assume that there isn't something like a very basic guide? In which case, can you direct me to the most relevant instructions?
I can get into camera settings, but only seeing Image, overlay, encode, PoE, remote maintenance, and update. Which, if any, are relevant?
And the closest to 'smart motion detection' is 'smart object detection', but 'config is not supported'...
 
wittaj, I don't want to take up your time, so perhaps I just have to invest the time studying the instructions/guide. Where do I find such a guide? Does the Dahua version suffice?
 
Yeah, so every Dahua OEM will have a little different look/feel based on how much the reseller wanted to change it.

Some could be simple color changes, while others may rename some things.

The only people here that use motion detection are those with dumb cameras that don't have AI. Motion Detection and Smart Motion Detection is why you have all the false triggers.

None of my cameras are using MD/SMD are all using Smart Plan/IVS as are most here.

This is for a Dahua OEM NVR (the general look/feel should be the same):

To get into the camera GUI from the NVR, you need to first access the NVR GUI by going to a computer and opening up a browser (preferably Internet Explorer (yeah we know) but Pale Moon will work as well) and type in the IP address of the NVR and login that way. Next go into the camera settings page on the NVR and look for the Microsoft e Web Browser and select it and it will go to the camera GUI (photo credit bigredfish from his PSA thread). Your screen may look a little different to get into the camera gui and see if doing it this way gets you access to some other features the NVR is blocking - do not worry about the Port number and circle as that was from another issue someone posted.


1715729692343.png







The user/pw for the cameras should be the same as the NVR unless YOU changed the camera user/pw.


How to enable native Internet Explorer in Windows 10 and 11:
  • Open Notepad:
    • Copy then paste the single line of code below into Notepad:
    • CreateObject("InternetExplorer.Application").Visible=true
    • Save as OpenIE.vbs
  • Make sure the the file name ends in .vbs not .txt, If it ends in .txt you must rename to .vbs
  • Create a shortcut to the above file and double-click it anytime you want native Internet Explorer.


And yes, the Dahua version should be sufficient to get you 90% of the way. Names may have changed some, but generally the same.


When did you buy? If recent, please list the model numbers as maybe it could be returned and you get something better for roughly the same price.
 
So the NVR is ok, but the cameras are crap.

They are basically the equivalent of the 3849 and here is a post with links to issues folks have had with it. It is a consumer camera where they shoved 8MP on a sensor designed for 2MP so the processor is way under powered.

But at the same time, for basic AI it should be working better than you have experienced.

With that NVR you could buy a few better cameras for a mission critical location.

Here is a "manual" specific to that model:

 
The cameras aren't great but they dont sound to be your biggest problem. The NVR is good. Not great but good enough.

You have a huge knowledge gap and have a system that is far beyond the simple stick up battery powered junk sold at hardware stores.
It would literally take days to get you up to speed on here, and its going to take you a good week or two to get familiar with all of the options and how they interact.

First thing to know is dont make settings on the NVR. Login to each camera and make the settings there.
The only thing you need to do on the NVR for now is make sure its recording via the recording schedule under Storage. Make sure ALL cameras and all colored lines (types of recordings) are recording 24/7 for now every day.

@wittaj - can you give him your std basics on image setup?

Ignore and disable Motion Detection and Smart Motion Detection (SMD)
Use only Smart Plan and IVS- Tripwire or Intrusion zone

Before all that you need to get the basic camera settings decent enough for AI to be able to see whats going on. We need a screenshot of what you're seeing

Here's some material to start with on camera settings


here's a snag from an online guide about basic image settings
To configure your Dahua camera settings effectively, focus on adjusting video quality, network settings, and exposure parameters for optimal performance.

Key​

  1. Video Quality Settings:
  1. Exposure Settings:
https://www.bing.com/ck/a?!&&p=8e57...ZGUtZWFzeS1hLXN0ZXAtYnktc3RlcC1ndWlkZS8&ntb=1
  1. Noise Reduction:
  1. Additional Features:
 
Per the request of @bigredfish

In terms of getting the most out of the camera, here is my "standard" post that many use as a start for dialing in day and night that helps get the clean captures and help the camera recognize people and cars.

Start with:

H264
8192 bitrate
CBR
15FPS and iframes if using 3rd party VMS (30 if using NVR is ok)


Every field of view is different, but I have found you need contrast to usually be 6-8 higher than the brightness number at night.

We want the ability to freeze frame capture a clean image from the video at night, and that is only done with a shutter of 1/60 or faster. At night, default/auto may be on 1/12s shutter or worse to make the image bright.

In my opinion, shutter (exposure) and gain are the two most important parameters and then base the others off of it. Shutter is more important than FPS. It is the shutter speed that prevents motion blur, not FPS. 15 FPS is more than enough for surveillance cameras as we are not producing Hollywood movies. Match iframes to FPS. 15FPS is all that is usually needed.

Many people do not realize there is manual shutter that lets you adjust shutter and gain and a shutter priority that only lets you adjust shutter speed but not gain. The higher the gain, the bigger the noise and see-through ghosting start to appear because the noise is amplified. Most people select shutter priority and run a faster shutter than they should because it is likely being done at 100 gain, so it is actually defeating their purpose of a faster shutter.

Go into shutter settings and change to manual shutter and start with custom shutter as ms and change to 0-8.3ms and gain 0-50 (night) and 0-4ms exposure and 0-30 gain (day)for starters. Auto could have a shutter speed of 100ms or more with a gain at 100 and shutter priority could result in gain up at 100 which will contribute to significant ghosting and that blinding white you will get from the infrared or white light.

Now what you will notice immediately at night is that your image gets A LOT darker. That faster the shutter, the more light that is needed. But it is a balance. The nice bright night static image results in Casper blur and ghost during motion LOL. What do we want, a nice static image or a clean image when there is motion introduced to the scene?

In the daytime, if it is still too bright, then drop the 4ms down to 3ms then 2ms, etc. You have to play with it for your field of view.

Then at night, if it is too dark, then start adding ms to the time. Go to 10ms, 12ms, etc. until you find what you feel is acceptable as an image. Then have someone walk around and see if you can get a clean shot. Try not to go above 16.67ms (but certainly not above 30ms) as that tends to be the point where blur starts to occur. Conversely, if it is still bright, then drop down in time to get a faster shutter.

You can also adjust brightness and contrast to improve the image. But try not to go above 70 for anything and try to have contrast be at least 7-10 digits higher than brightness.

You can also add some gain to brighten the image - but the higher the gain, the more ghosting you get. Some cameras can go to 70 or so before it is an issue and some can't go over 50.

But adjusting those two settings will have the biggest impact. The next one is noise reduction. Want to keep that as low as possible. Depending on the amount of light you have, you might be able to get down to 40 or so at night (again camera dependent) and 20-30 during the day, but take it as low as you can before it gets too noisy. Again this one is a balance as well. Too smooth and no noise can result in soft images and contribute to blur.

Do not use backlight features until you have exhausted every other parameter setting. And if you do have to use backlight, take it down as low as possible.

After every setting adjustment, have someone walk around outside and see if you can freeze-frame to get a clean image. If not, keep changing until you do. Clean motion pictures are what we are after, not a clean static image.
 
  • Like
Reactions: bigredfish
That's a hell of a lot of information thrown into this thread over a simple configuration of SMD/IVS issues.
Tweaking the image settings can come after we've sorted out the detection rules/alerts.

Configuring camera settings through the NVR (local or web) is perfectly fine. You don't need to login to the camera directly! The NVR is still going to acquire the config in the background the same way.
 
That's a hell of a lot of information thrown into this thread over a simple configuration of SMD/IVS issues.
Tweaking the image settings can come after we've sorted out the detection rules/alerts.

Configuring camera settings through the NVR (local or web) is perfectly fine. You don't need to login to the camera directly! The NVR is still going to acquire the config in the background the same way.

But camera parameter settings can have a direct impact on the AI detection.

We have seen many instances though were making camera settings in the NVR doesn't quite work that way and a reboot results in settings getting all mixed up.

While in theory, it shouldn't matter whether the settings are done in the NVR or the camera GUI, reality has shown in many instances it does make a difference and should be done within the camera GUI.

In my neighbors system, he set everything up in the NVR and when I logged into the camera GUI, the settings were completely different than what the NVR was showing. And on a reboot, they both changed LOL.

If you haven't had issues, especially after reboots, then you have been lucky!

As always YMMV.
 
We have seen many instances though were making camera settings in the NVR doesn't quite work that way and a reboot results in settings getting all mixed up.
While in theory, it shouldn't matter whether the settings are done in the NVR or the camera GUI, reality has shown in many instances it does make a difference and should be done within the camera GUI.

In my neighbors system, he set everything up in the NVR and when I logged into the camera GUI, the settings were completely different than what the NVR was showing. And on a reboot, they both changed LOL.
If you haven't had issues, especially after reboots, then you have been lucky!
As always YMMV.
Settings about IVS itself get stored on the IPC, unless you are using AI by Device (NVR).
NVR is subscribed to the camera's configuration event changes through internal SDK.

The NVR not acquiring config indicates a communication issue between the NVR & Camera(s) OR the firmware versions (thus, SDK) between both are terribly out of date.
 
That's a hell of a lot of information thrown into this thread over a simple configuration of SMD/IVS issues.
Tweaking the image settings can come after we've sorted out the detection rules/alerts.

Configuring camera settings through the NVR (local or web) is perfectly fine. You don't need to login to the camera directly! The NVR is still going to acquire the config in the background the same way.

First, the OP admittedly doesn’t understand the basics.
Question: can anyone direct me to a simplified guide to THE BASIC Settings?
Also, is it possible to do a full reset to eliminate what are obviously incorrect Settings that I can't track down individually?


And I can say confidently that image settings can indeed effect the accuracy of AI detection

I looked for a good basic image setup video by my Google Fu failed

While I understand the theory of using the NVR to make settings, and that they should synch, there are settings that aren’t even available in the NVR UI

I don’t have one of the new geek wiz NVR’s, can you set Exposure on them?
 
Last edited:
Settings about IVS itself get stored on the IPC, unless you are using AI by Device (NVR).
NVR is subscribed to the camera's configuration event changes through internal SDK.

The NVR not acquiring config indicates a communication issue between the NVR & Camera(s) OR the firmware versions (thus, SDK) between both are terribly out of date.

Maybe for a system that the NVR and camera are all the same series on same versions bought at same time.

But what about someone, say @bigredfish with an older NVR and he gets newer cameras. He won't see all of the camera settings from the NVR nor will the NVR communicate settings to the camera appropriately due to conflicting versions between NVR and camera that you mention.

Which is why best practice continues to be make all the camera settings in the camera GUI. Similar to using Internet Explorer, this is the best practice to ensure all settings are seen and stick within the camera.

Doesn't mean someone won't have an issue, similar to not factory resetting before a firmware update, but that doesn't mean it is the best practice to ensure minimal issues.