Dahua 2231S generates very high main stream transfer rate

P

Perimeter

Getting comfortable
Feb 18, 2023
557
584
Europe
I am confronted with an oddity I can't really solve:
I have a dahua 2231 cam (2MP), that is set to a data transfer rate of 6144. My other 5442 cams are set to ~8000.
When I look at the cams (IE11, SmartPSS or NVR), the 5442s behave as advertised while the 2231 shows very high values, like around 20000 kbps.
When I go and set the value anew, it drops to 6000 shortly, then goes up again. The camera is working fine otherwise.
it is running h264, cbr, dumb codec 15fps/15i, no substream.
I just throttled it to 4096 in IE11. It promptly obeys. I'll see how long this lasts.
(And yes, I did hit save!)
Edit: 20 min later it is up again.

Did a limited reset to defaults. Trying again now.
Now it still holds these values. Might have solved it.
 
Last edited:
Comment applicable only if using a Dahua NVR.
My NVR pushes the camera names it has to the cameras. If I change a camera name on the camera interface, the NVR changes it right back to what's set in the NVR, so I have to change camera names using the NVR's GUI. Could the NVR also be changing bit rates? I don't know, just something to be suspicious of. I never saw what you're seeing with my 2231.
 
  • Like
Reactions: Perimeter
Yes I am using a dahua NVR. I was suspecting something like that. But I changed the transfer rate in all viewing devices including NVR.
What I think may have happened is that I connected it at some early stage to the NVR or SmartPSS as a .108 cam after I had a 5442 at the address before. And I did set the 5442 to 20000. Strange though that it sticked even after the IP and the interface was reconfigured.
Maybe 20000 did set a 1-bit for 16000 which would not be deleted when the speed was later adjusted to 6000. As the 1 for the 16000 is not used in representing 6000. A reset to defaults may just have erased it then.
It would still not explain why 6000 was obeyed for a while.
 
  • Like
Reactions: JDreaming
Very occasionally I run into something with how a camera operates with the NVR, and the only way I've found to fix it is to delete the camera from the NVR and add it back in. I don't remember what the "something" is. I know it when I see it happen, less than once a year on average. I'm running a non-POE nvr, and maybe the delete+re-add behavior could be different with the built-in POE switch.
 
  • Like
Reactions: bigredfish, JDreaming and Perimeter
^^^^^^^^^^^^
Good possibles

Another good reason why I only make setting changes on the camera GUI itself. (Outside of network and Recording Schedule)

Once you start making changes on the NVR, SmartPSS, etc things can get wonky. Also get used to clicking Save AND Refresh on each change. In theory that helps synch settings back to the NVR.
 
  • Like
Reactions: looney2ns, JDreaming and CanCuba
CanCuba said:
It's the ROI. I had the same thing happen with a 2431 variant. Like 13k to 15k stream when set to 6k.
Click to expand...
Yeah, it looks like it. Without roi, it is stable at 6k until now.
If so, it might be an interesting way to up the image quality. Why would Dahua limit it at 6k, when the camera can do 20k?
Surely, there is a point of diminishing returns.
 
  • Like
Reactions: CanCuba
Perimeter said:
Yeah, it looks like it. Without roi, it is stable at 6k until now.
If so, it might be an interesting way to up the image quality. Why would Dahua limit it at 6k, when the camera can do 20k?
Surely, there is a point of diminishing returns.
Click to expand...

Interesting question. But I've never had a great experience with ROI and it's actually negatively affected the image quality overall with little, if any improvement in the designated ROI. I'm guessing the processors can't handle over 6k without the image being negatively affected.

The two cams that I had an issue with had almost no motion in them but the bitrate went through the roof. If I recall correctly, there was a lot of stuttering going on which is what tipped me off.
 
  • Like
Reactions: looney2ns and bigredfish
CanCuba said:
Interesting question. But I've never had a great experience with ROI and it's actually negatively affected the image quality overall with little, if any improvement in the designated ROI. I'm guessing the processors can't handle over 6k without the image being negatively affected.

The two cams that I had an issue with had almost no motion in them but the bitrate went through the roof. If I recall correctly, there was a lot of stuttering going on which is what tipped me off.
Click to expand...

I already ditched some area with privacy masking, because nothing will ever happen there and I don't want to waste bandwidth on it. Of the remaining area, some lower part will not informative but will be a stable background motion trigger trap. So I kept it but excluded it from ROI. Well, there goes that idea...
 
  • Like
Reactions: JDreaming, bigredfish and CanCuba
Perimeter said:
I already ditched some area with privacy masking, because nothing will ever happen there and I don't want to waste bandwidth on it. Of the remaining area, some lower part will not informative but will be a stable background motion trigger trap. So I kept it but excluded it from ROI. Well, there goes that idea...
Click to expand...

Always a hiccup in getting to where we want to be.

Did you find an improvement in the ROI area when it was active?
 
  • Like
Reactions: JDreaming
You must log in or register to reply here.
Top Bottom