What causes this blur or ghosting?
- Thread starter Walrus
- Start date
looney2ns
IPCT Contributor
Recording with what? Make sure you have smart codec turned off in the cams setup.
looney2ns
IPCT Contributor
Have you excluded everything from any Antivirus as outlined in the BI help file?
Performed a clean OS install using Windows Media Creator?
Not using pc for anything else?
Hmmm.. don't think I've done the exclusion in windows defender. I'll check that.. I'll exclude the BI program, and the folders, including the recording drive.
It's not a clean install, and I use the computer for my everyday browsing when I'm home. This ghosting occurred when I was at work, and my wife was leaving the house, so nobody was using the computer. Hopefully it's defender scanning the processes causing this.
It's not a clean install, and I use the computer for my everyday browsing when I'm home. This ghosting occurred when I was at work, and my wife was leaving the house, so nobody was using the computer. Hopefully it's defender scanning the processes causing this.
I have the iframe interval at twice the FPS (50 since FPS is 25), that's what it defaults to when you change the FPS.
I have 3D NR set at 15 (default was 50)
I only have 2 cams so far, both 2231, both with the exact same settings. This effect occurs on both of them.
I have 3D NR set at 15 (default was 50)
I only have 2 cams so far, both 2231, both with the exact same settings. This effect occurs on both of them.
Q™
IPCT Contributor
Q™
IPCT Contributor
I always set my receive buffers to 20.
It's a weird phenomenon. If I watch the live stream (or recorded), over the entire 11-12s, the detail is getting finer and finer, and then bam.. blurry/blocky.. then it repeats. There is a dusting of snow on my driveway, and if I zoom in on my tire tracks, they get more and more detailed, then all of a sudden it resets back and is blocky.
Here is a picture of the two extremes. On the left is immediately after it goes.. you can see the large blocks in the snow, and the center of the tracks is blurry. On the right, the snow has finer pixels, and the middle of the tracks can be seen.
My 3D NR is actually set at 25, not 15.
Here is a picture of the two extremes. On the left is immediately after it goes.. you can see the large blocks in the snow, and the center of the tracks is blurry. On the right, the snow has finer pixels, and the middle of the tracks can be seen.
My 3D NR is actually set at 25, not 15.
fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,901
- Reaction score
- 21,269
The webserver uses large keyframe intervals to save bandwidth. The default is 300.
@Walrus
Usually when that kind of corruption appears (as seen in your first post) it is because Blue Iris dropped a frame. This can sometimes be helped by finding the "Max rate" setting in BI camera properties > Video and setting it a few FPS higher than the camera actually sends.
The quality difference you have noticed in UI3 every 11-12 seconds is caused by keyframes in the stream which Blue Iris sends to UI3. Normally in H.264 video, keyframes are very large so they don't cause a visible difference in quality. But for the purposes of webcasting with as little delay as possible, Blue Iris makes the keyframes relatively small and low quality so they don't cause the video to jerk or pause. This can cause a noticeable temporary drop in image quality whenever a keyframe gets rendered. To work around it, you can increase the streaming bit rate and/or decrease the frame rate. Try higher resolution streaming quality options in UI3 first, as each higher quality choice roughly doubles the bit rate limit even if it can't increase the resolution of your stream any further. The 2160p (4K) option has a limit of 8192 Kbps which is the highest Blue Iris will allow. Then if necessary you should be able to improve the situation further by reducing the streaming frame rate to 15 FPS (do this in UI3's streaming profile configuration). By reducing the frame rate, you increase the amount of data which can be allocated to all the remaining frames, making them better quality at the same bit rate.
Usually when that kind of corruption appears (as seen in your first post) it is because Blue Iris dropped a frame. This can sometimes be helped by finding the "Max rate" setting in BI camera properties > Video and setting it a few FPS higher than the camera actually sends.
The quality difference you have noticed in UI3 every 11-12 seconds is caused by keyframes in the stream which Blue Iris sends to UI3. Normally in H.264 video, keyframes are very large so they don't cause a visible difference in quality. But for the purposes of webcasting with as little delay as possible, Blue Iris makes the keyframes relatively small and low quality so they don't cause the video to jerk or pause. This can cause a noticeable temporary drop in image quality whenever a keyframe gets rendered. To work around it, you can increase the streaming bit rate and/or decrease the frame rate. Try higher resolution streaming quality options in UI3 first, as each higher quality choice roughly doubles the bit rate limit even if it can't increase the resolution of your stream any further. The 2160p (4K) option has a limit of 8192 Kbps which is the highest Blue Iris will allow. Then if necessary you should be able to improve the situation further by reducing the streaming frame rate to 15 FPS (do this in UI3's streaming profile configuration). By reducing the frame rate, you increase the amount of data which can be allocated to all the remaining frames, making them better quality at the same bit rate.
@bp2008
I have the max rate in BI for each camera set to the max (30fps), higher than the camera setting (25fps).
Thanks for the suggestion of looking at the UI3's streaming profile, as the limit bit rate for 1080p (2MP) was set to yes instead of inherit, with the max bit rate set to 2048. I changed it to inherit. In BI under web server - advanced - steaming profile, I had limit bitrate unchecked. This has now gotten rid of the 11-12s quality change.
I have the max rate in BI for each camera set to the max (30fps), higher than the camera setting (25fps).
Thanks for the suggestion of looking at the UI3's streaming profile, as the limit bit rate for 1080p (2MP) was set to yes instead of inherit, with the max bit rate set to 2048. I changed it to inherit. In BI under web server - advanced - steaming profile, I had limit bitrate unchecked. This has now gotten rid of the 11-12s quality change.
Just be aware this means there is no bit rate limit at all, so in the right circumstances the bit rate could get extremely high. Possibly too high for your network connection or in some cases even too high for the decoder to handle, which could cause the stream to fail. Not too likely if you've at least left the quality % at 50 which is the default.