This article walks through the Video Tab settings that also need to be considered when connecting cameras. We assume you went through the Camera Connector article in order to setup the BI camera connection correctly.
We also assume you went through the Camera setup article in order to make sure the encoding settings on the camera works well with BI.
If you prefer to watch the webinar associated with this article, checkout the Camera Connections and Streams webinar.
Video tab
Best practice
Below are settings that generally work. The highlighted settings are the ones that usually get people in trouble when set or unset from the default values.
Details
Below are details on features that can affect the camera.
Camera settings -> Video tab.
Below is the list of BI settings that can affect streaming.
Hardware decode (aka hardware video acceleration, HWVA).
Used to turn HA on/off for live camera feeds.
- Global settings -> Cameras tab. Turn on/off globally for All cameras.
- Camera settings -> Video tab. Turn on/off for a particular camera.
Camera setting takes precedence over global setting.
Mix and Match GPUs
If you have multiple GPUs on your machine, it is possible to assign different cameras to different GPUs to distribute the load. Turn HA off globally and assign GPUs on a per camera basis.
Intel Processors choose Intel + VPP
If for some reason you experience instability, try the Intel selection without VPP.
AMD Processors choose DirectX
Not a big fan of using external graphics cards (NVidia, AMD) for encoding/decoding.
The Choosing hardware for Blue Iris article referenced in Hardware Recommendations article has some interesting insights.
The software now turns off HA automatically for a camera if it determines the stream is not compatible and this is logged to Status->log as well.
If you want to fix the problem, you can go to the camera settings on the camera and adjust the encoding to a more simple format that may start working with your hardware. A simple example is if the camera was set to H.264 High encoding, adjust the setting to H.264 Baseline. If you were using H.265, switch to H.264.
Or wait for the next driver update that may fix the issue caused by the current driver.
See GPU link for even more information on GPU hardware.
Limit decoding unless required.
Used on the Live view stream. However, largely not needed anymore with the popularity of dual streams.
Limit decoding (as stated in Help) will only decode key frames. One side affect is if your kfps = 0.5, then you are receiving 1 key frame every 2s.
Thus, if you have a time overlay on your camera view, you will see video updates every 2s, not every 1s.
Overlays
Overlays can slow video. If your cameras are lagging, you may want to turn off overlays.
Also BVR
Used to turn HA on/off during video playback. 99% of the time it is better to leave this option off. The playback window allows you to scan backwards and forward. This work load is not conducive for hardware acceleration. Hardware acceleration is effective with smooth, consistent streams of video.
Image size (resolution) & FPS
FPS
Many users think they can adjust the FPS on a camera using the Max. rate setting on the Camera settings -> Video tab.
This is impossible. You can ONLY adjust FPS on the camera. This setting is used for better memory allocation. If you know the FPS for the camera is 5 FPS, you can tell BI accordingly so it can allocate RAM for this camera more efficiently. If you set it incorrectly, no worries. As BI receives the video feed, it automatically adjusts this value (which is why many users noticed it changed from their user setting).
Image size
Many users think they are changing the camera resolution. Again, this is impossible. You can ONLY adjust resolution on the camera. This setting is applied after the stream arrives at BI. Users can alter the resolution further. This feature was occasionally used by users to get a better fit of their cameras on their iPad or Tablet endpoint. However, with the new layout editor, this use case is no longer needed.
See 5.5 Release Notes for details.
Use with caution. I'm not sure of a valid use case for using anamorphic anymore. See Trigger gotcha due to the Anamorphic setting.
Many users think they can adjust the FPS on a camera using the Max. rate setting on the Camera settings -> Video tab.
This is impossible. You can ONLY adjust FPS on the camera. This setting is used for better memory allocation. If you know the FPS for the camera is 5 FPS, you can tell BI accordingly so it can allocate RAM for this camera more efficiently. If you set it incorrectly, no worries. As BI receives the video feed, it automatically adjusts this value (which is why many users noticed it changed from their user setting).
Image size
Many users think they are changing the camera resolution. Again, this is impossible. You can ONLY adjust resolution on the camera. This setting is applied after the stream arrives at BI. Users can alter the resolution further. This feature was occasionally used by users to get a better fit of their cameras on their iPad or Tablet endpoint. However, with the new layout editor, this use case is no longer needed.
See 5.5 Release Notes for details.
Use with caution. I'm not sure of a valid use case for using anamorphic anymore. See Trigger gotcha due to the Anamorphic setting.
At this point, you should have connected your camera to BI and the live stream should look smooth and clear. The final piece is considering how to record the streams coming into the camera. See Record format for details.
Statistics: Posted by varghesesa — Mon Oct 25, 2021 2:10 am
]]>