I worked it out by installing an older version of 64-bit smartPss. As for moving to BI, I don't see that as a black-and-white issue. I'm saying that as a long-term NVR+smartPss user who ran the BI demo in parallel for about a week. The real killer for me was that about half of my cameras don't send out IVS events over ONVIF. If you got your cameras from Andy in the last few years, they "probably" send the IVS events. You can verify that with onvif device manager. That issue aside, I'm highly versed in operating the NVR and smartPss, and parts of the UI in BI are very different, so I have the obstacle of unlearning and relearning. On the surface and intuitively, I sense the BI's UI is easier to deal with. My bottom line advice is to do what I did, temporarily set up a clean win 10 box with BI and try it out in parallel. Another thing I learned is that an older core duo machine doesn't have enough oomph to run BI properly. I'm thinking it needs at least a gen 2 core i3, i5, or i7.
Another fairly big issue I just remembered is that with BI you don't see the green boxes and IVS trip lines in either real time or playback. This is a pretty big loss for me, might mean nothing for somebody else. Some BI users say that BI's built-in motion detection is equal to or more powerful than IVS. I don't have a conclusion if that's true or not, but what I found is in BI it takes a lot of fiddling and tuning to make the motion detection competitive with line crossing or intrusion, compared with super-simple IVS setup. Veteran BI users may have learned how to set up the motion detection quickly and easily. For a beginner, at least in my case, it was pretty time consuming.
