I'm not dead yet.
ImageSalsa/MovieSalsa are still being supported and sold to whomever wants to buy them, but as noted, no more development is occurring. Ed convinced me to productize ImageSalsa a decade ago based on his experience with VWS. I probably sunk about 6 solid months of evenings and weekends into making the first version of ImageSalsa. Well, let's just say the road to riches is not lined with weathercams
The most reliable email is usually firstname.lastname@example.org
. I've switch web providers a few times and I have to keep altering the support web page to circumvent spambots -- so some of the support and email methods go up and down periodically, but the support email gets my top priority.
I've also happy to say I've got a young family going now. As such, most of my time is dedicated to them. So, you won't find me perusing the boards much unless -- as in this instance -- someone like Don lets me know via email that there is a thread I should look into.
Now, with the issue that you are seeing, Don. I don't have a specific answer to give you because the error is coming from a third-party module that ImageSalsa uses to do its video capture. And they are notorious for providing very little useful information in their error codes back to ImageSalsa. I'd first make sure that your standard video feeds (under the old menu from 1.x days) are disabled for the same camera -- you can't (usually) connect to the same device using two different programs or the same program using two connections. If the old connection is still enabled, then trying to enable it with the 2.0 connection will fail. This may be what the error message is trying to convey.