Big oops. I went back and fixed it. The IL is the one with lousy detection.Did you type that wrong?
You start saying the S3 is bad then show numbers saying it detects Better?
Big oops. I went back and fixed it. The IL is the one with lousy detection.Did you type that wrong?
You start saying the S3 is bad then show numbers saying it detects Better?
So, it looks like, on average, IL static handles static scenes better, but S3 works better for moving objects.


The 3449 TIOC (IPC-Color4M-T) is a terrible camera. You couldn't pay me to use it. It is the only product I've ever returned to EmpireTech. Fuzzy, overcontrasty, constant color issues, motion blur, lack of detail even in broad daylight, serious AI artifacts at dusk/night, etc.So what’s the difference between the 54PRO and 3449 TIOC Pro - they both have the same sensor too along with the IL
The naming nomenclature sucks to be honest
I have to agree that the IPC-Color4M-T sucks @$$ - the picture quality is DULL and washed out and as you said, "constant color issues, and lack of detail even in broad daylight" and is sadly same foam factor as the varifocal 5442 S3 turret@tigerwillow1 One of the differences I'm noticing consistently between the pictures you shared of those two cameras is that the 541R-S3 uses TV range encoding, while the IL appears to use Full range encoding. Blue Iris is hardcoded to use Full range decoding, even though most cameras (and H.264/5 streams) are specifically encoded in TV range. This results in a lack of contrast and the colors being off slightly in Blue Iris compared to what you'd see on the camera's UI, or in snapshots taken directly from the camera. I have found that if you enable Intel hardware decoding in Blue Iris, the Intel decoder uses TV encoding range, resulting in the contrast and colors being correct on most cameras (they'd be over contrasty on the IL).
The 3449 TIOC (IPC-Color4M-T) is a terrible camera. You couldn't pay me to use it. It is the only product I've ever returned to EmpireTech. Fuzzy, overcontrasty, constant color issues, motion blur, lack of detail even in broad daylight, serious AI artifacts at dusk/night, etc.
Speaking of this (and the above), the cheap 2449T-S-PRO (IPC-Color4M-TL) is a vastly superior camera that also outputs full range encoded streams that render correctly in Blue Iris by default.
Yet another thing I didn't know. I turned on "Intel" hardware decoding for the S3. I don't see any immediate difference in the image, but it's a cloudy day and all the colors are muted. I'll keep an eye on it. Thanks.@tigerwillow1 One of the differences I'm noticing consistently between the pictures you shared of those two cameras is that the 541R-S3 uses TV range encoding, while the IL appears to use Full range encoding. Blue Iris is hardcoded to use Full range decoding, even though most cameras (and H.264/5 streams) are specifically encoded in TV range. This results in a lack of contrast and the colors being off slightly in Blue Iris compared to what you'd see on the camera's UI, or in snapshots taken directly from the camera. I have found that if you enable Intel hardware decoding in Blue Iris, the Intel decoder uses TV encoding range, resulting in the contrast and colors being correct on most cameras (they'd be over contrasty on the IL).
I tried CPAI when I first set up BI, and it didn't work out well. The system was unstable in that it had to be rebooted every week or two. I'm open to the possibility that it was fixable, I just don't have infinite time to spend on it. Since removing CPAI, the BI installation hasn't needed any rebooting for over a year. Plus, CPAI wasn't all that hot at identifying animals, and after a camera false alert, CPAI often found a rock or fencepost to identify as some kind of animal. Once BI 6 goes stable with its built in AI I might give that a try.Time to use Code Project AI for animal detection.![]()
Yeah I didn't think it would work for you which is why I put the ROFL emoji.I tried CPAI when I first set up BI, and it didn't work out well. The system was unstable in that it had to be rebooted every week or two. I'm open to the possibility that it was fixable, I just don't have infinite time to spend on it. Since removing CPAI, the BI installation hasn't needed any rebooting for over a year. Plus, CPAI wasn't all that hot at identifying animals, and after a camera false alert, CPAI often found a rock or fencepost to identify as some kind of animal. Once BI 6 goes stable with its built in AI I might give that a try.
Looking at the 5459-IL images, I would suggest dropping 2D NR (under Camera -> Exposure) from 50 to 25 and see if you get sharper results. I'm noticing its over-smoothing artifacts in quite a few of the sample images you provided. You could even try 0 if it doesn't make the image too grainy. Note that Dahua cameras have a firmware bug that causes that setting to internally revert back to 50 when you close the admin session. Rebooting the camera after closing it restores it to the value you saved.By now I have a pretty good feel for image quality between the S3 and IL, so probably my last mass-posting of side-by-side images. Conclusions are:
- In situations with even daytime lighting, it's an overall tie.
- In situations with large difference bright and dim areas, IL wins.
- At night with IR lighting, IL wins.
I've realized there is a bigger elephant in the room, in that so far the IL's object detection kind of sucks. Details in the next post.
Images where the S3 looks better (IMO of course):
View attachment 236180View attachment 236181
View attachment 236182View attachment 236183
Images where the IL looks better:
View attachment 236184View attachment 236185
View attachment 236186View attachment 236187
View attachment 236189View attachment 236190
View attachment 236193View attachment 236194
View attachment 236195View attachment 236196
Dahua cameras have a bug in virtually everything software-wise. Its too bad we can't have nice things in the land of the free unless we are prepared to spend 3x-4x the price of a 5442 camera.Looking at the 5459-IL images, I would suggest dropping 2D NR (under Camera -> Exposure) from 50 to 25 and see if you get sharper results. I'm noticing its over-smoothing artifacts in quite a few of the sample images you provided. You could even try 0 if it doesn't make the image too grainy. Note that Dahua cameras have a firmware bug that causes that setting to internally revert back to 50 when you close the admin session. Rebooting the camera after closing it restores it to the value you saved.