EmpireTech IPC-T5442T-ZE and Blue Iris Configuration

In terms of getting the most out of the camera, here is my "standard" post that many use as a start for dialing in day and night that helps get the clean captures and help the camera recognize people and cars for IVS.

Start with:

H264
8192 bitrate
CBR
15FPS
15 iframes

Every field of view is different, but I have found you need contrast to usually be 6-8 higher than the brightness number at night.

We want the ability to freeze frame capture a clean image from the video at night, and that is only done with a shutter of 1/60 or faster. At night, default/auto may be on 1/12s shutter or worse to make the image bright.

In my opinion, shutter (exposure) and gain are the two most important parameters and then base the others off of it. Shutter is more important than FPS. It is the shutter speed that prevents motion blur, not FPS. 15 FPS is more than enough for surveillance cameras as we are not producing Hollywood movies. Match iframes to FPS. 15FPS is all that is usually needed.

Many people do not realize there is manual shutter that lets you adjust shutter and gain and a shutter priority that only lets you adjust shutter speed but not gain. The higher the gain, the bigger the noise and see-through ghosting start to appear because the noise is amplified. Most people select shutter priority and run a faster shutter than they should because it is likely being done at 100 gain, so it is actually defeating their purpose of a faster shutter.

Go into shutter settings and change to manual shutter and start with custom shutter as ms and change to 0-8.3ms and gain 0-50 (night) and 0-4ms exposure and 0-30 gain (day)for starters. Auto could have a shutter speed of 100ms or more with a gain at 100 and shutter priority could result in gain up at 100 which will contribute to significant ghosting and that blinding white you will get from the infrared or white light.

Now what you will notice immediately at night is that your image gets A LOT darker. That faster the shutter, the more light that is needed. But it is a balance. The nice bright night static image results in Casper blur and ghost during motion LOL. What do we want, a nice static image or a clean image when there is motion introduced to the scene?

In the daytime, if it is still too bright, then drop the 4ms down to 3ms then 2ms, etc. You have to play with it for your field of view.

Then at night, if it is too dark, then start adding ms to the time. Go to 10ms, 12ms, etc. until you find what you feel is acceptable as an image. Then have someone walk around and see if you can get a clean shot. Try not to go above 16.67ms (but certainly not above 30ms) as that tends to be the point where blur starts to occur. Conversely, if it is still bright, then drop down in time to get a faster shutter.

You can also adjust brightness and contrast to improve the image. But try not to go above 70 for anything and try to have contrast be at least 7-10 digits higher than brightness.

You can also add some gain to brighten the image - but the higher the gain, the more ghosting you get. Some cameras can go to 70 or so before it is an issue and some can't go over 50.

But adjusting those two settings will have the biggest impact. The next one is noise reduction. Want to keep that as low as possible. Depending on the amount of light you have, you might be able to get down to 40 or so at night (again camera dependent) and 20-30 during the day, but take it as low as you can before it gets too noisy. Again this one is a balance as well. Too smooth and no noise can result in soft images and contribute to blur.

Do not use backlight features until you have exhausted every other parameter setting. And if you do have to use backlight, take it down as low as possible.

After every setting adjustment, have someone walk around outside and see if you can freeze-frame to get a clean image. If not, keep changing until you do. Clean motion pictures are what we are after, not a clean static image.
 
It appears this option has been removed from BI (prior 5.8.0.14)

It isn't removed, it is just named something else. I think it might be called External or something similar. Post screenshots and I can tell you, or someone running a newer version can chime in with what it is called now.
 
In terms of getting the most out of the camera, here is my "standard" post that many use as a start for dialing in day and night that helps get the clean captures and help the camera recognize people and cars for IVS.
.
.
.
.

This is extremely helpful. Thank you for all your time you put into this.
 
These cameras have different image sensors and many other factors so I would not expect the Reolink settings in BI to perform the same. Are you using the BI motion sensor settings or have you setup IVS rules in the camera. You may experiment with both to achieve your desired results. If using IVS rules within the camera then you will need to uncheck motion sensor in BI and check "Camera's digital input or motion alarm" and select "get ONVIF trigger events" in the Video/Configure tab. Your alerts will show EXTERNAL if triggered by the camera as opposed to MOTION if triggered by BI's internal settings.
Well, I have this working like a charm. I haven't completely tested the two different options you mention above but for now I am sticking with the IVS rules. One thing I haven't figured out is how to determine what triggers the rule (i.e. vehicle, person) without the use of CodeProject.AI (or the likes). The trigger event BI receives/calls is RulesEngine/FieldDetect. For now I still have CodeProject enabled but I find this so fragile. One slight tweak to either CP setting/modules or AI setting within BI can cause real havoc. I would like to do without if possible.
 
I guess the real question is do you specifically need to see in the image text whether the trigger was a car or person or are the thumbnail images sufficient for you to see whether it was a car or person?

With using the camera AI, the only real reason to then use CodeProject is if you really need the little orange person or vehicle icon. Like you said, it can be fragile and one tweak can wreak havoc on the system.

For me, I just tell BI to show me the external triggers and then I scroll thru the thumbnail alert to see which ones were a person and which ones were a vehicle.

If you want to dive into the Trigger events, BI is still a work in progress on making it more user-friendly, but here is a thread on how folks went about it to pull whether it was a person or vehicle from that triggered event.

 
Thanks everyone for help me through this. I have everything pretty much running pretty good for now. @wittaj I think you are right about need (or not need) to see the image text. With the combination of IVS rules and BI ONVIS triggers I pretty much got what I need. This camera is awesome. Maybe a few more in the future ;)
 
Hope you all had a great Christmas!

I've been reading this thread with interest and have a question;

I've always set my EmpireTech cameras up to use the motion detection built into BI. I never thought about using the IVS on the cameras and telling BI to capture the events.

What are the benefits of using IVS over BI motion?
 
Hope you all had a great Christmas!

I've been reading this thread with interest and have a question;

I've always set my EmpireTech cameras up to use the motion detection built into BI. I never thought about using the IVS on the cameras and telling BI to capture the events.

What are the benefits of using IVS over BI motion?

IVS has AI so it will only trigger for human and/or vehicle.

So if all you can about are those for a trigger, then you eliminate the false triggers of just BI motion.

Now if you want triggers for other objects like animals, then you would need to do BI motion detection.

Another benefit of using the camera for triggering is it uses less CPU on the BI computer.

 
IVS has AI so it will only trigger for human and/or vehicle.

So if all you can about are those for a trigger, then you eliminate the false triggers of just BI motion.

Now if you want triggers for other objects like animals, then you would need to do BI motion detection.

Another benefit of using the camera for triggering is it uses less CPU on the BI computer.


Thank you. I'm going to change my setup using IVS. Wish me luck!