Disabling sub stream causes UI3 to show a cropped image of the camera.

[digger11]

I've experienced a few instances where the video for a particular camera has lagged significantly behind my other cameras.
When I've looked at a camera's settings while one of these events was happening the Status section of the General tab has shown a "Receive buffer bottleneck" warning.
Based on recommendations in another thread, on Sunday I bumped Receive buffer to 40 MB on all of my cameras.
This morning I observed another one of these events on a IPC-B54IR-Z4E-S3, again observed the Receive buffer bottleneck warning, and confirmed that the Receive buffer was set to 40 MB.

Just to see whether it might make a difference, I disabled the substream in the Video>Network IP>Stream profiles.
I then noticed that UI3 was showing a cropped image for that camera.

Here is what it looked like in UI3:


Here is what it looked like in the Blue Iris Console:

A restart of the camera had no effect.
A restart of Blue Iris had no effect.

For grins, and because the features of the latest Blue Iris version, 5.9.9.5, lists "UI3 update" I upgraded Blue Iris from 5.9.8.5 to 5.9.9.5.
The video for the camera remained cropped.

I then went into Video>Network IP>Stream profiles and enabled the sub stream again, and the UI3 window for the camera was back to a full view of the camera feed.

The behavior is reproduceable. Disable the sub stream and UI3 shows a cropped view of the camera. Enable it and the view in UI3 goes back to normal.
I also performed the same actions on an IPC-Color4k-X and saw the same behavior.

With the sub stream disabled, I've tried setting Anamorphic to both enabled and disabled with no noticeable effect.

Other than deleting the camera and adding it back I can't think of anything I haven't already tried.

@bp2008 have you ever seen this behavior?

 

[digger11]

Looks like I'm going to be contacting Blue Iris Support. I pretty much use UI3 exclusively, but I do have the Android BI app. It is also showing the cropped image.

 

[digger11]

Here's some additional information/observations...

The cropped image issue survives a system reboot.

Manually triggering 6+ cameras via a right-click>"Trigger now" caused the "Receive buffer bottleneck" to occur on one of the cameras that had its sub stream disabled, so apparently only having a main stream did not prevent the issue.

Downgrading to Blue Iris version 5.7.8.3, which has been the most stable version for me, resolves the cropped image issue.
I'm not sure if it is significant, but this is the first time after a downgrade that I've noticed the cameras all log a "Clip: Format change" event when BI started after the downgrade.

The triggering of 7+ cameras by a vehicle did not cause a "Receive buffer bottleneck" while running 5.7.8.3.
It's been awhile since I've tried the latest versions to see if the issues they cause on my system have been addressed, but apparently they have not.
Although I don't like continuing to fall further and further behind the current version of Blue Iris I'm not sure if I'm willing to put in the time and effort it would require to wipe out Blue Iris and see whether a clean install and then completely recreating my configuration from scratch would make the problems I've had with versions higher than 5.7.8.3 go away.

 

[looney2ns]

Here's some additional information/observations...

The cropped image issue survives a system reboot.

Manually triggering 6+ cameras via a right-click>"Trigger now" caused the "Receive buffer bottleneck" to occur on one of the cameras that had its sub stream disabled, so apparently only having a main stream did not prevent the issue.

Downgrading to Blue Iris version 5.7.8.3, which has been the most stable version for me, resolves the cropped image issue.
I'm not sure if it is significant, but this is the first time after a downgrade that I've noticed the cameras all log a "Clip: Format change" event when BI started after the downgrade.

The triggering of 7+ cameras by a vehicle did not cause a "Receive buffer bottleneck" while running 5.7.8.3.
It's been awhile since I've tried the latest versions to see if the issues they cause on my system have been addressed, but apparently they have not.
Although I don't like continuing to fall further and further behind the current version of Blue Iris I'm not sure if I'm willing to put in the time and effort it would require to wipe out Blue Iris and see whether a clean install and then completely recreating my configuration from scratch would make the problems I've had with versions higher than 5.7.8.3 go away.

Have you emailed support? Be sure to use the method outlined in the help file.

 

[digger11]

Have you emailed support? Be sure to use the method outlined in the help file.

I have. Ken is already looking at it.