Worlds First Review - Dahua DH-IPC-HDW5849H-ASE-LED / IPC-Color4K-T - 2.8mm Turret

I've got this unit mounted and running. Image looks pretty sharp as far as I can tell. WDR washout seems to be worse than 5442 however so I have it turned off right now. I'm curious with those of you running CBR @ h.265 what bit rate did you set for? I have mine at 10000 kbps at h.265 currently. I normally use 8192 @ h.265 for 4MP cams like the 5442.
 
  • Like
Reactions: duplo
I recall the WDR being overly powerful as well. I dont run ANY cameras on H.265 so cant help you there.
From what I have read it mainly depends on what generation your CPU on your BI box is. I am sure there are other factors too...


@wittaj Has a good post explaining h.264 vs. h.265:
 
  • Like
Reactions: CanCuba
From what I have read it mainly depends on what generation your CPU on your BI box is. I am sure there are other factors too...


@wittaj Has a good post explaining h.264 vs. h.265:

But @bigredfish uses an NVR and not BI.

And it is a big misconception about what computers can use H265 - it is only 6th generation and above that can use hardware acceleration with H265 and the previous generations cannot use hardware acceleration with H265.

But an older computer can use H265 just fine, it just cannot use hardware acceleration with the internal onboard GPU.

But yes my post about H265 versus H264 is relevant regardless of how someone records. It comes down to individual field of view and what they are trying to accomplish between the two. Some run H265 just fine for their needs.
 
But @bigredfish uses an NVR and not BI.

And it is a big misconception about what computers can use H265 - it is only 6th generation and above that can use hardware acceleration with H265 and the previous generations cannot use hardware acceleration with H265.

But an older computer can use H265 just fine, it just cannot use hardware acceleration with the internal onboard GPU.

But yes my post about H265 versus H264 is relevant regardless of how someone records. It comes down to individual field of view and what they are trying to accomplish between the two. Some run H265 just fine for their needs.

I'd imagine that an NVR would have hardware geared for decoding the supported codecs.

I could be wrong though.
 
I'd imagine that an NVR would have hardware geared for decoding the supported codecs.

I could be wrong though.

You are correct. And there are many NVRs that will force H265 to keep bandwidth down as the unit is limited in bandwidth capacity.

But just because they can decode it doesn't necessarily mean it is a better codec, especially in context with my examples.
 
You are correct. And there are many NVRs that will force H265 to keep bandwidth down as the unit is limited in bandwidth capacity.

But just because they can decode it doesn't necessarily mean it is a better codec, especially in context with my examples.

I took your advice long ago and went h.264 or h.264H if the camera supports it, and CBR. Big difference!

Thanks for all the great advice you put on this forum!
 
Last edited:
I've got this unit mounted and running. Image looks pretty sharp as far as I can tell. WDR washout seems to be worse than 5442 however so I have it turned off right now. I'm curious with those of you running CBR @ h.265 what bit rate did you set for? I have mine at 10000 kbps at h.265 currently. I normally use 8192 @ h.265 for 4MP cams like the 5442.

For what it's worth on the 4Kx I'm running h264H at 16864 on the mainstream and 4032 @ 1080P on the sub. Those figures are plus or minus a few KB as from memory.

I run the sub highish because I run BVR.
 
For what it's worth on the 4Kx I'm running h264H at 16864 on the mainstream and 4032 @ 1080P on the sub. Those figures are plus or minus a few KB as from memory.

I run the sub highish because I run BVR.

I really like that second substream videoclip option. Nice to focus on an area of interest and get it in 1080p
 
Anyone using backlight with this camera? WDR is a mess on it as far as I can tell. Setting it to 50 provides waaaay to much color saturation. Bumping it down to ~45 immediately washes out the image and begins to turn it black and white. So you are basically left with play from 45 - 50. Also, a couple of times, when adjusting the WDR strength, the camera would hard lock and I'd have to reboot it.

For now, I have backlight left off but I think WDR is broken on this camera.
 
I basically had the same experience today. I used SSA in its previous location and it wasnt great but was better than WDR

I'm seeing another issue - Pulsing, which I believe is directly related to how much light is available
I noticed it early this morning when I hung the 4K-T and again later today as the light begins to fade..

Running 30fps, 10240 bitrate and Iframe of 60

When I run Iframe 30 (matching FPS as I do on all my cameras) the pulsing is just faster. 60 helps but its still there just slower. Reducing to 15FPS/15 iframe provided no change


Daytime bright sunshine it seems ok, but its there
View attachment Gator_ch5_20230511170040_20230511170121.mp4

















Watch the area circled Red Home_Color4K-T-GatorCam_main_20230511170038_@5.jpg

Now close to 7pm and sun is starting to go dimmer - 30FPS/60Iframe
View attachment 30FPS=60Ifr_ch5_20230511183950_20230511184019.mp4
 
Last edited:
^Yeah that seems to be a common issue people have posted.

I see it when I try to run too fast of a shutter at night.

I think it is simply a byproduct of Dahua trying to squeeze as much as possible in color in low light conditions.

So I had to decide between a faster shutter and some pulsing or slower shutter and no pulsing. I went with the faster shutter as the pulsing doesn't affect the image of capturing a freeze frame of a perp.

Plus my Pizza Hut delivery people aren't as hot as yours LOL, so I am only watching video if something happens.
 
I wonder if the pulsations are due to the buffer dumping eating the CPU
time slots, thus slowing the processing of the scene.
 
  • Like
Reactions: JDreaming