Mini-Review EmpireTech IPC-Color4M-T
- Thread starter wittaj
- Start date
Chokolinho
Getting comfortable
same results, output quality doesn't change at all.
Because I was thinking about using M for recording, S1 for DMSS and S2 for HA cards via go2rtc.
That is usually the type of field of view that we see these cameras struggle and was what I was expecting to see.
The camera is trying to process resolving every angular corner of the dirt/grass/what not and it can't keep up. We will see that with gravel and water ripples too.
And then trying to do multiple streams adds processing power to it and overloads it.
And sometimes the bitrate limits out too low to fix it.
The camera is trying to process resolving every angular corner of the dirt/grass/what not and it can't keep up. We will see that with gravel and water ripples too.
And then trying to do multiple streams adds processing power to it and overloads it.
And sometimes the bitrate limits out too low to fix it.
I see! Can confirm because the other camera looking only at the porch does support well the 2nd stream. While the other one with grass and gravel does not.
Ok so I guess I am stuck with mainstream and sub1@D1 (don't think it is a good idea for DMSS and mobile view to use 720p)
Ok so I guess I am stuck with mainstream and sub1@D1 (don't think it is a good idea for DMSS and mobile view to use 720p)
I was wondering: if I'm gonna disable MD/SMD and keep only IVS with 2/3 rules, I guess I could save enough cpu to use the 1st sub as 720 right? Home connection and mobile connection are more than beefy enough to support the load from the 6 cameras
Thanks, I'll do that!
EDIT: I can also use go2rtc to have a "low quality" dashboard for mobile connection when in spotty areas. So I can keep using only main stream and sub1 while a low quality sub is done directly via HA
EDIT: I can also use go2rtc to have a "low quality" dashboard for mobile connection when in spotty areas. So I can keep using only main stream and sub1 while a low quality sub is done directly via HA
Last edited:
I am trying to configure the 6MP version of the Color4M-T camera, but I am having an issue with the combination of IVS and Smart Illumination. When I use MD with area masks and SMD, it is possible to constrain Smart Illumination to a specific area. However, when I enable IVS, Smart Illumination works across the entire scene. I need to partially disable Smart Illumination when IVS is active. Is this possible?
for me MD masks never worked for Smart Illumination on 3449-PRO..
Now I know why - I used IVS..
quality of firmware on newer Dahua cams is going spiral down...
I am sure there is a difference in working of Smart Ilumination when IVS is enabled. At least with range. when I was using MD+ SMD only, SI works more or less up to 7m. It was similar to the mask set in MD. Now when I enabled IVS (with large AI model) then range is doubled, almost entire scene.
I suppose thats possible when enabling the large AI model.
I'm just saying that on the 54PRO and 34PRO Smart Illum will detect across its field of view (with IVS and SMD OFF) if enabled. I never measured distance.
I'm just saying that on the 54PRO and 34PRO Smart Illum will detect across its field of view (with IVS and SMD OFF) if enabled. I never measured distance.
Last edited:
I have just made a test and MD masks work with SI. (SMD set on too). IVS disabled. Camera - 3649H AS PV Pro.
Wild
So unlike the AS fixed lens version, the 3449H ZAS-PV-PRO does NOT activate white LEDs solely by having Smart Illum set with NO IVS.
When IVS is enabled, only then will Smart Illum turn on the white LEDs. IVS seems to be a must for the white LED's to activate.
On the other hand, I've shown clearly before that the fixed AS version will indeed turn on white LED's using only Smart Illum. No IVS required.
Different FW
ZAS - V3.140.0000000.16.R, Build Date: 2025-06-20
AS- V3.140.0000000.7.R, Build Date: 2024-10-18
Like the 5442's, BOTH cameras dim IR LED's when IVS is enabled. A Lot!
Fixed Lens
ZE varifocal
So unlike the AS fixed lens version, the 3449H ZAS-PV-PRO does NOT activate white LEDs solely by having Smart Illum set with NO IVS.
When IVS is enabled, only then will Smart Illum turn on the white LEDs. IVS seems to be a must for the white LED's to activate.
On the other hand, I've shown clearly before that the fixed AS version will indeed turn on white LED's using only Smart Illum. No IVS required.
Different FW
ZAS - V3.140.0000000.16.R, Build Date: 2025-06-20
AS- V3.140.0000000.7.R, Build Date: 2024-10-18
Like the 5442's, BOTH cameras dim IR LED's when IVS is enabled. A Lot!
Fixed Lens
ZE varifocal
Last edited:
And while testing for that I discovered something member @Zoltán Szabó brought to my attention that I had not known.
When you turn off IVS rules, the camera, on its own, takes it upon itself to change a bunch of image settings… seems to effect 5442 series, 3449 PRO series (4M-T) and 54PRO series. Maybe others…
Scroll to Page 2 of this thread, post#21
When you turn off IVS rules, the camera, on its own, takes it upon itself to change a bunch of image settings… seems to effect 5442 series, 3449 PRO series (4M-T) and 54PRO series. Maybe others…
Scroll to Page 2 of this thread, post#21
it's strictly different firmware version behavior - not different HW model behavior...
ZAS you have on firmware version after Dahua added Large Scale AI models.
Another time, when they add some feature and they destroy other by bad code design...
I was thinking about disabling all substreams on the cameras and use go2rtc to take the mainstream and then restream a 720p and 360p.
This could save some additional resources on the camera itself, right?
Just to be sure: IVS runs on the mainstream right? I can safely disable the substreams without losing any detection capability, correct?
This could save some additional resources on the camera itself, right?
Just to be sure: IVS runs on the mainstream right? I can safely disable the substreams without losing any detection capability, correct?