Just to clarify, is it lost during playback or during recording? In other words is the missing info there and can be seen if you step through frame by frame or is it never recorded to begin with. In the example it just skips a few minutes with no delay, making it look like it's not a read problem(?)

5 is all I've ever used it with. Some those early update "opportunities" inspired me to look into it and install it and it's bailed me out on more than one occasion since. Lately it's been more of a security blanket but it does allow one to easily revert to the previous version to confirm ...

(And to revert to the slight thread hijack) Another tool to make it easier to revert to known good version of BI is BIUpdateHelper. It runs as a service and offers a few other nice solutions as listed here https://github.com/bp2008/biupdatehelper.

Ummmm - Am I the only one that gets the same thing in the help (? button in the Title Bar), only updated? For example, a search for "camset" will get you to page 175 of 191 in the UI current version and 155 of 169 in the downloaded version dated May 2019 (continuing the sorta hijacked thre...

My experience had everything to do with screen painting. Running BI with nine cameras as a service used ~25%. Opening the UI with only the onboard graphics bumped the CPU usage to around 45-60% with occasional 100% usage when multiple cameras triggered. If I increased the size of what I was looking ...

I'm guessing English is a second language here and making it a bit difficult for us to zero in on the issue. Have you tried exporting your current settings (presuming you've done enough to have some worth saving) and then uninstalling and reinstalling BI? Many of us are successfully running it on W1...

Just another perspective and possibly helpful tool: BI5 has been rock solid for me using it only locally. I load each update as soon as it comes in, relying on BIUpdateHelper to bail me out if things go wrong. The one time I reverted to a previous version I notified support and heard back that the o...

By now you should have seen 5.0.4.7 pop up which fixes the eval message glitch. Some are reporting a "VCRUNTIME140_dll was not found" error but I'm not seeing it on my W10 x64 install

And in the time in took me to figure out BI Update Helper to get the version before 5.0.4.6, 5.0.4.7 popped up and took away the evaluation warning. Still shows V4 key in settings but maybe it always did. Thanks Ken! (stuff happens)

Me three. License Key shows old code but attempting to enter current code gives a "This key has already been added to your license, you don't need to do it again." and dies there. I'll be anxiously awaiting the next update or seeing if BI Update Helper will bail me out