IPC-Color4K-T and IPC-Color4K-T180 230227 Firmware

hadn't heard of that issue. It's two cameras on 1 POE port so it's rated for 802.3at power. not 802.3af power.

I don't know that garbled video is common. Earlier in this thread it was reported by at least one other person (but i see now that it was for a Color4K-T not Color4K-T180). I remember seeing it in a few other threads too, but don't have access to them right now.
IPC-Color4K-T and IPC-Color4K-T180 230227 Firmware

To clarify a bit, yes, that GUI I posted is from BI. Based on the suggestions from earlier in this thread, I made sure to use H264 and the result is the same. I can replicate it 100% of the time by switching on one of the backlight modes such as WDR or HLC. If all dynamic lighting modes are off, then it's fine. Also, this seems to only affect the main stream since the overview in BI never shows garbled video. It's only when viewing the camera in single camera mode (which I assume is main stream) that the video gets unusable.
 
I don't know that garbled video is common. Earlier in this thread it was reported by at least one other person (but i see now that it was for a Color4K-T not Color4K-T180). I remember seeing it in a few other threads too, but don't have access to them right now.
IPC-Color4K-T and IPC-Color4K-T180 230227 Firmware

To clarify a bit, yes, that GUI I posted is from BI. Based on the suggestions from earlier in this thread, I made sure to use H264 and the result is the same. I can replicate it 100% of the time by switching on one of the backlight modes such as WDR or HLC. If all dynamic lighting modes are off, then it's fine. Also, this seems to only affect the main stream since the overview in BI never shows garbled video. It's only when viewing the camera in single camera mode (which I assume is main stream) that the video gets unusable.
Do you restart the cams in Blue Iris after you make changes to the settings in the cam?
 
Found the other post where this issue is discussed. Seems it's not specific for Color4k-T180, but any models using WizColor processing. What I'm seeing almost exactly match the conditions mentioned in that post. Observations from steve1225 seem to be spot on and clarifies things quite a bit.


Solution is to avoid using WDR/SSA.

For the record, yes, restarting the cam in BI fixes the issue until the next time WDR/SSA is enabled. This means you can't use different backlight settings for profile switching between day/night.
 
So do we call that a +1 for NVR’s

Nope because the OP thread mentioned above is with an NVR. Now bigredfish has an older NVR so maybe that is part of why he doesn't have a problem?

Or there is something else going above with some other type of codec that he isn't using.
 
  • Like
Reactions: JDreaming
Nope because the OP thread mentioned above is with an NVR. Now bigredfish has an older NVR so maybe that is part of why he doesn't have a problem?

Or there is something else going above with some other type of codec that he isn't using.
I suppose I missed that, I just saw something about restarting the cam in BI a couple posts up. As well I probably should have added a smiley face or something to indicate I was just being a smart ass.
 
Yeah the guy with the recent garbled video is using BI apparently.
Is he using default video sizing?
Someone came in once with their hair on fire about this type of thing, and after about 5 posts we found out he manually set the video size in BI and that was the problem.
 
  • Like
Reactions: JDreaming
Sorry to ask this, but I'm confused: are both 4K-T and 4K-T180 using the same firmware ?

Andy's support site is showing different versions, 2025-06-27 for 4K-T but 2023-12-24 for 4K-T180...
 
Did you do the 3 times factory reset, flash firmware, then 3 times factory reset or did you just go for it?
Wow, 3 times factory reset twice ?! Should we spin around the camera three times and make a special reset dance in front of it ?!

I agree with you, and even if I found the 4K-T a bit laggy (especially with higher resolutions), I'll keep the initial firmware for now as tripwire works fine and local SD card storage records correctly. (Surprising to read that I should use Internet explorer to have a quicker video player...) (unclear how it ended for you, @mephisto_uk)
 
  • Haha
Reactions: Flintstone61
Wow, 3 times factory reset twice ?! Should we spin around the camera three times and make a special reset dance in front of it ?!

I agree with you, and even if I found the 4K-T a bit laggy (especially with higher resolutions), I'll keep the initial firmware for now as tripwire works fine and local SD card storage records correctly. (Surprising to read that I should use Internet explorer to have a quicker video player...) (unclear how it ended for you, @mephisto_uk)

It comes from the developers that get "under the hood" of the firmware and have seen in some instances it takes multiple factory resets for the firmware to take properly.

It doesn't mean that people haven't had issues by just updating it directly without doing it, but if people have problems, we typically find they did not do a factory reset first and when they follow this procedure, it then takes and works.

Same with Explorer. While newer cameras are supposed to work with other browsers and not need the plug-in nonsense, keep in mind to ensure full compatibility, IE is still preferred. And this isn't specific to just Dahua either. And sometimes the plug-in nonsense is needed.

It comes down to IE was the most popular browser when these cameras started to be made, so they centered the firmware around one particular browser and they got lazy and never updated the internals of the program to play nice with other browsers as more became available and IE started to fade.

Back when the firmware was written, it was probably a pain to get it to play nice with every different browser, so they went with the most popular one.

They haven't had a need to address this because their intended market (remember it isn't us) is mainly businesses where they have enough light they can stay in default settings so they don't have a need to login to the camera via browser. It is us homeowners that push these to the limits and actually change settings.

As long as their intended market simply uses the NVR as a recording device and to display it on a monitor, they have no need to change what works for their intended market.


Further, Steve1225, who is an installer and works closely with Dahua, said it best here in this post:

1741262948757.png



Even though Microsoft has sunset Explorer, it is still available in Windows 11 (hidden). Many older programs rely on the old Trident (HTML-) Engine from IE, even stuff as basic as the old Control Panel. Old browsers are old, so unlike modern browsers where the WebView can be its own component, it's either all or nothing. And since the engine is still required not to break Windows functionality and apps from before 2015, it's still included (but mostly hidden). The whole file manager system is still based on IE. That's also why Device Manager and Control Panel are still there too. Similar to Dahua and Hikvision, Microsoft changed the UI and not the core, and added new features to upgrade its OS. A lot of legacy stuff are hidden.

So contrary to popular belief, Internet Explorer isn't going away anytime soon.

YMMV
 
  • Like
Reactions: Arn0
Time and time again, I see firmware fuckarounds gain nothing, except adding a new chinese backdoor, Internet Explorer was big in China, now I'm sure they have something newer with exploits built in approved by Fearless Leader.
It's all because of Communist rule.
They can make the cameras without needing IE. But then they lose their backdoors, So in order for the gov't to allow production, they want access. It's a surveillance country.
I'm not saying that cant use other browsers but they are restricted.

1756285306200.png