I don't think it's a big deal today, but I suspect its importance will grow over time:
CPU-agnosticism is, in general, a good thing, if done properly. In the best cases, there is no CPU-specific code in the code base, which makes it easier to subsequently compile the code later for other architectures, such as RISC-V, or whatever comes down the pike 5-10 years from now.
As always, "It depends," but CPU-agnostic code often implies a more modern, thought-out approach to architecture and best-practices coding, because the duct-tape and baling-wire approach does NOT last long on multi-arch software projects. Making little CPU-specific fixes everywhere a CPU-specific bug rears its ugly head will soon collapse under its own weight. So if BI 6 is written in truly CPU-agnostic code, it probably means that the development team has refactored things to make the whole system more robust, modular, and maintainable. Yes, there will be shiny new bugs in 6.0.0, but I suspect the code base will be of higher quality than was 5.x, overall.
There aren't a lot of ARM-based PCs on the market today, but it will grow over time.
BI on ARM means that it should be possible to run in a VM on a Mac. This isn't going to be a huge segment of the user base, but it will be a nice option for some people, like my brother.
My seek/scrub/playback performance also went massively downhill with .99, although oddly enough, my reported CPU usage didn't go up. But this is in UI3, so maybe the CPU usage reporting isn't as accurate.
In any case I reverted back to .96, and now everything is good again.
I can connect using Android app a few times, then it gets in a can't connect state. If I restart the service then I can connect, for awhile
Running 5.9.9.99 r4
A lot of that is due to Ken changed the way it reads CPU usage. Look at your task manager and maybe adjust your CPU factor. I had to change mine to .750 to make it same as task managers.
A lot of that is due to Ken changed the way it reads CPU usage. Look at your task manager and maybe adjust your CPU factor. I had to change mine to .750 to make it same as task managers.
When I updated to .99, my actual performance suffered, not the reported CPU usage. In fact my reported CPU usage didn't change at all, but scrub/seek performance was unusable until I reverted back to .96.
A lot of that is due to Ken changed the way it reads CPU usage. Look at your task manager and maybe adjust your CPU factor. I had to change mine to .750 to make it same as task managers.
Anyone having issues streaming rtsp from blueiris. All of a sudden my streams dont work anymore with this 5.9.99 version
I rolled back to 5.9.98 and they work fine. I think im going to stay with this version for a while
5.9.9.99 builds are definitely broken in a number of ways. A lot of changes have been going into video encoder stuff in particular as they are trying to add a proper "CBR" (constant bit rate) encoding mode and for some reason this is breaking VBR in interesting ways. I'm not surprised if RTSP has gotten broken in the meantime because it is not used very often so there are far fewer people likely to report problems with it.