Last night I spent 5 hours trying to figure out why my Intel NUC was showing constant reload errors for web sites, and also, why I couldn't update Windows. As to the NUC, I went to Intel's web site and ran the automatic driver updater. One of those updates was to the BIOS, so I did the update. For the next 30 minutes after doing the update, "Intel NUC" would flash on the screen, turn off, turn on, etc. I thought I had bricked the computer, so I turned it off. When I turned it back on, there was a "Your BIOS has been updated" message. Then I did the update for the wireless, and the web reload errors eventually stopped.
I still haven't figured out why Windows won't update. (And don't tell me how wonderful the Mac is...these days, I cross my fingers and pray whenever there's an update for my MacBook Pro. There was one update, can't remember which one, where the wi-fi was hosed...and there were other problems as well.)
All these Intel/Windows issues happened without my even touching SONAR, and I'm relatively savvy with computers. Y
et the computer is the foundation upon which programs like SONAR must run. I could detail other issues I've had with software from other companies (the grass is not always greener on the other side), and a lot of them deal with interactions with Windows components as well.
It is unreasonable to expect ANY company to know how to get their software to work with all permutations and combinations of hardware, which is especially bad for Windows. This isn't to excuse any legitimate bugs that may or may not exist in SONAR that cause incompatibilities, but there's a reason why I think many times when people experience "SONAR bugs," they're experiencing bugs with software that interacts with SONAR.
Several years ago in one of my Pro Sound News columns I said that in the future, keeping a computer-based recording system running reliably was only going to get worse. There are times when I would absolutely
love to be wrong, but I don't think this was one of them.