Registry backups are still 100% fine, and done far better than Blue Iris's own registry backups in my opinion. Those .reg files are huuuge due to Blue Iris's extremely inefficient encoding of motion zones. My tool compresses 30+ MB reg files down to a couple KB using 7zip.So, it's best to not depend on the current version for Reg backups in V5, I assume.
It would definitely be possible to glean information from camera short names, as with anything the user typed themselves. So I wouldn't include that.That's the hard part!! Would people object to the camera short name do you think?
Windows version and BI version are there if you click a row to see the full record. GPU utilization, that is harder to measure, so I'm not sure. There's more than one relevant part of the GPU to measure too, which is half the trouble. Not everything is likely to be available to measure on all systems with different GPUs and drivers and Windows versions.on the stat page for the CPU usage, can you add the windows version, BI version and the GPU utilization . I like the stats it is a good indicator of what CPU to use, also how well a configuration is compared to others.
Heh, that would be neat if BI did its own data collection. It could know so many more things, like which cameras are clones of each other, what video codec they use, how many actual frames get decoded per second (limit decoding royally screws with this!) whether hardware acceleration is working or not...I would really like it if it was automatically installed with BI so there was more data points. Maybe with an OPT OUT.
That OS is old enough it might not come with .NET framework 4.5. Make sure that is installed.BIUpdateHelper failed to run in Windows Server 2008R2 VM in ESXi 6.7.