Blue Iris Updates (64 bit)

Blue Iris Updates - Official Thread 6.0.9.2

Go to download
Overview Updates (739) History Discussion
I have two BI 6.x setups in completely different locations (and separate host computers) which have worked fine for ages. Both have up to date annual updates with auto-renew. Recently both were updated and they both reverted to evaluation mode seemingly forgetting the registration codes. I managed to get one of them up and running again with the code which I purchased 2 years ago but is in fact the code for the other system which is of less importance. On the other I have emailed support twice but so far no answer as need the original code seeing as it was some 11 years ago and not sure where the email has gone. On one of them I also noticed the camera groups setup had mostly been deleted so I had to recreate them and reassign to the users. I did assume the registry backup and restore would restore the keys and fix the groups but apparently not.

I am hoping support will answer soon as been several days. But has anyone else seen this?

Thanks - John
 
6.0.8.6

Undocumented under-the-hood change

Starting with v6.0.8.6 (6/30/2026), Blue Iris now uses a rolling 3-second average when calculating the bitrate macros %k and %007. Ken has also confirmed that the FPS macros %f and %006 were similarly updated. He noted that the changes were suggested by AI.

Previously, the calculation was based on 10 one-second buckets of frame data.

Users graphing these macros should expect smoother values than in previous releases, even though the underlying camera behavior is unchanged.

It's worth noting that these macros represent values measured and averaged by Blue Iris from the received video stream, not values reported directly by the camera.
 
Last edited:
  • Like
Reactions: Techie007L and David L
jaydeel said:
Starting with v6.0.8.6 (6/30/2026), Blue Iris now uses a rolling 3-second average when calculating the bitrate macros %k and %007. Ken has also confirmed that the FPS macros %f and %006 were similarly updated. He noted that the changes were suggested by AI.

Previously, the calculation was based on 10 one-second buckets of frame data.

Users graphing these macros should expect smoother values than in previous releases, even though the underlying camera behavior is unchanged.
Click to expand...
Quoting myself to provide an update.

After collecting data for a week, I reported back to Ken that the change DID NOT provide the expected improvement. In fact, it made the data more unsteady.

Ken's reply on 7/10:

"The older versions essentially used a 10 second smoothing buffer. The new one is only 3 seconds. Maybe I can​
adjust this up to 5 before today's release, as the new unsteady display does seem troublesome"​

As far as I've been been able to determine, the change has not yet been implemented (as of 6.0.9.2).
 
Techie007L said:
@jaydeel Well yeah, he went from a 10 second average to a 3 second average—of course the number is going to be more jumpy!
Click to expand...
Indeed, I was thinking the same and it proved correct.

However, it is a bit more complicated than that. I did not provide the full details. Pre Ken, the original method was the average of 10 buckets of 1 second of frames. The new one is a 3-second rolling average.

So I'm not holding my breath for the proposed 5 second smoothing buffer (if it's also a simple rolling average). ChatGPT predicts it will provide about 20–25% calmer data than 3-seconds, and still be worse than the original.
 
You must log in or register to reply here.
Top Bottom