This article is about the proper camera settings ON the camera in order to work well with BI.
There is nothing more frustrating than NOT being able to connect your cameras.
BI can only connect to equipment that supports the ONVIF protocol and/or standard video streaming formats such as RTSP, RTMP, MJPEG and JPEG.
NVR / DVR
Details on connecting an NVR/DVR.
BI supports the RTSP and ONVIF standards to get access to your cameras. This section is about BI considerations when connecting a new camera to the network. A large part of this section is about gathering the information needed for the connector article as well as maximizing the opportunity to pull ONVIF information if available on the camera.
If you are seeking guidance on troubleshooting a camera that does not connect any longer, there are two approaches:
- Error message: If the camera window shares an error code go to the Camera Errors article for guidance.
- No signal error: The No signal error can have many causes. The No Signal Error article documents known issues and fixes.
The easiest way to connect cameras to the network is to follow the manufacturer's installation instructions. Below are ways to confirm whether the cameras are connected properly:
Many cameras come with an app. Follow the manufacturer instructions to connect your camera to your phone/app. If the camera is connected to the network properly, then the app should work and you should be able to see the video from the camera.
The app will often provide the key information needed to connect BI to a camera.
Camera - Web interface
Try to login to the camera using the camera's web interface. You need to know the camera's IP address. You may need to use the techniques below to get the information needed to login.
Login to your router and identify all the cameras that are connected to the network. Note their IP Addresses.
Use Advanced Port Scanner to identify all cameras on your network.
Note the IP Address and ports available on each camera.
To login simply type the IP Address into the browser window.
The camera's login page should appear. If the browser times out you either have the wrong IP address, port number or the camera does NOT have a web interface.
Foscam is an example of a vendor that uses port 88 commonly for the web interface. Know your cameras.
If the camera has other ports available (Advanced Port Scanner) try those ports as well.
Simply type in the browser window <ip address>:<port number>, e.g. 10.0.0.7:8080.
Alternatively, if you already tried connecting the camera to BI, go to Camera settings -> Video tab. Select the URL link. If the URL opens in a browser with the login screen for the camera, then you know the IP address is correct. If the camera home screen appears after attempting login with username/password, then you have confirmed the username/password are correct.
If the camera does not have a web interface, this often means the camera is not open for 3rd party integration and can only be accessible via the proprietary phone app provided by the vendor. This may be a good time to approach the camera vendor and ask how to connect the camera to 3rd party VMS systems using RTSP. One user asked how to connect the camera to VLC. After much prying, the vendor finally gave up the information. Camera vendors would prefer you use their software and lock you into their ecosystem.
RTSP or other video formats
Leverage 3rd party players such as VLC to connect to the camera. If VLC cannot connect, more likely than not, BI will not be able to do so either.
Some vendors may still provide access to the RTSP port to pull the video stream. TP Link is one such vendor that has a proprietary app interface, yet still provides RTSP access to the video stream.
Summary of key camera settings needed to connect cameras to BI
- IP address
- Web, RTSP and ONVIF ports.
Keep in mind some cameras provide no port access. Completely closed to third party access, e.g. Ring, Arlo etc.
As little as an RTSP port, i.e. access to the video ONLY may be shared.
BI ideally works with three channels of communication with a camera.
The default web port for all internet devices is often the port used by cameras to access the web interface as well.
Keep in mind many camera vendors use Port 80 to relay ONVIF information as well. By default, BI will check for ONVIF support on Port 80.
Also keep in mind, vendors can use another port for the web interface. For example, Foscam uses port 88 for the web interface. Know your cameras.
Port 554 is the default RTSP port. This is the port to access the video stream assuming the camera allows 3rd party access.
If the camera uses another port for the video stream for heightened security, often the camera provides the port information via ONVIF.
Sometimes you may need to review the camera documentation and/or reach out to the vendor.
If cameras choose NOT to convey ONVIF information via port 80, they often choose port 8999 which is also checked by BI by default.
ONVIF Gotcha 1
KNOW your camera. If the camera states ONVIF support, but when hitting Find/Inspect, you do not see rich ONVIF information being pulled from the camera (ONVIF section below has details), then you have not established an ONVIF connection. Below is a camera that happens to use port 8080 as the default ONVIF port.
If you do not change the Discovery/ONVIF value in the IP Config Dialog from the default 8999 to 8080, BI will not know how to connect to the camera and pull the ONVIF information.
Another user had a camera that had ONVIF on port 8120. Ironically, he discovered the ONVIF port and successfully connected to the camera using ONVIF Device Manager (ODM).
Ironically he did not tell BI, ONVIF was available on port 8120 and thus BI could not connect until he changed the IP Config Dialog.
ONVIF Gotcha 2
It turns out camera vendors are adding another layer of security to their ONVIF controls. The ONVIF ports may be open by default. However, the amount of information available through the port can be limited until security permissions are set on the camera. In the Hikvision example below, access to the ONVIF capabilities were limited until we added the user account used by BI into the ONVIF user list with admin privileges.
Axis cameras also have this functionality. The username/password placed in BI needs to be an ONVIF account in order to pull in the ONVIF features.
At this point, you should know the key information needed to connect cameras to BI.
- IP Address
- Web, RTSP and ONVIF ports (if available)
This section documents quirks associated with specific camera vendors.
99% of cameras only support the RTSP protocol. On occasion, a vendor will support RTSP and RTMP. Reolink is one such vendor and the RTMP protocol seems to provide a healthier stream.
Checkout the Reolink Gotchas article for best practices on connecting Reolink cameras.
This section is about camera video settings that can affect BI. Setting the encoding and fps etc is critical to attaining a good live view in BI.
Below are the most common camera settings that can affect the video quality seen in Blue Iris. Think of these settings as levers on the camera (NOT BI) that can be adjusted to provide the optimal video stream.
- H.264 vs H.265
- H.264/265 Encoding Profiles: Baseline, Main, High etc
- Key frame interval
BI only works with the H.264 and H.265 standards. Camera manufacturers have tweaked their encoding to optimize bandwidth for their apps. H.264+, H.265+ (note the + sign) Smart Codec etc are all proprietary encodings that can only be used by the vendor apps. When customers report the cameras work on their app but not in BI, the encoding is often times the reason. The No Signal Error is almost always due to the fact that the cameras are using a proprietary encoding.
Also best to start with H.264 encoding before moving to H.265. Also, choose H.264 Main/Baseline instead of High if given the choice. Provide BI the easiest connection available first and increase the complexity if and when needed.
Older Intel CPUs (before Skylake) with QuickSync do NOT have H.265 support. If the camera is set to H.265 encoding and your QuickSync does not support H.265, the Server may crash. See Hardware Recommendations article for details.
In order to get the server running again, you may need to turn off HA in the registry. See details.
Keep settings simple such that all the streams have the same FPS. Choosing between 30 fps or 15 fps is a user preference. For most surveillance situations, 10 - 15 fps is plenty good.
Setting all streams to have the same fps makes time reconciliation easier for BI. Turns out certain vendors like Hikvision set different fps (10, 15) for different streams. Different fps settings unnecessarily complicate playback synchronization with dual streams.
Key frame ratio
A key frame ratio >0.5, ideally 1.0 leads to a healthy video stream that delivers a good user experience. BI will tell you the key frame ratio. In this example, all the camera key frame ratios = 0.1
Rule of thumb: Make sure the key frame (i-frame) interval on your camera equals the FPS for the camera. This will deliver a key frame ratio equal to 1.0.
- Camera fps = 30. key frame interval = 30 (1.0 fps). Can consider key frame interval as high as = 60 (0.5 fps)
- Camera fps = 15. key frame interval = 15 (1.0 fps). Can consider key frame interval as high as = 30 (0.5 fps)
This topic is discussed in the BI Server Settings article because it's a BI server setting that affects the user experience due to camera streams.
However, the Pre-trigger buffer goes hand in hand with the key frame ratio so placed here as well.
Largely set based on user preference (5s is recommended).
Rule of thumb:
Pre-trigger buffer >= 1/kfps
For example, if the camera stats state 0.5 for the kfps, 1/0.5 = 2s. The pre-trigger buffer for the camera should be >= 2s.
Or just use a default 5s pre-trigger buffer for all cameras.
First, keep in mind this is just a warning symbol. It's only a problem if your video is lagging, choppy or frozen. This warning is then a clue that some of your camera settings (above) are not working well with BI.
If you are receiving these warnings recently, it is because we are now also monitoring key frame ratios when the setting has an affect on your configuration, like direct to disc or limit decoding. The warning symbol appears if the key frame ratios drops below 0.4.
Fix: Revisit your camera encoding settings.
Reolink known issue: The sub stream for Reolinks often run at 0.25 kfps and the key frame interval is not configurable. Sub streams are a huge benefit for CPU load. So overall, if the video is not choppy, lagging etc, we recommend using sub streams.
From Help file:
Historically, the warning message was frequently due to the camera's FPS. BI constantly measures the fps of your cameras. At a peak time maybe the camera was sending 15 fps. Maybe because of network congestion etc. the fps for that camera temporarily dropped to 2 fps. The warning message would pop up. Unless you observe persistent frozen cameras or lagging cameras, the issue resolved itself and you can ignore. BI will display this warning when the FPS is 15% of the observed actual max frame rate.The Log page in Status contains one or more warning messages or one or more
cameras has an error condition or warning, such as low frame rate or a push
This section has learnings from past tickets.
The Camera Gotchas article shares learnings from past tickets.
Gotcha 1: Server performance
Always good to run through Windows Tuning article to make sure Windows is NOT in conflict with BI.
All checks are important. Pay attention to the Anti-virus and Firewall sections.
The biggest CPU savings are:
- Dual streams on all cameras.
- Direct to disc recording
- And hardware acceleration (e.g. Intel QuickSync).