1) *This is not what I've found to be the case. Only when attempting to open the program with the wireless connection disabled do I find there is a problem. I can do this as many times in succession as is possible and always get the same results.rydan wrote:*As soon as you disable or enable a network card, and then start Live, it will want to re-authorize. This is absolutely horrible, and a BIG BIG pain! So, well, as soon as there is a cracked version of Live8, the pirate community will have a much better working product than us paying for it (as usual with copy protected software...). Great news, eh? =/
Up until now, the Ableton copy protection has been pretty OK, hasn't caused that much trouble, but this is really bad.
What I do to maintain as low a latency as is possible is to merely disable the connection once the program is open.
2) I am not certain by any means that this is a form of copy protection. That is merely a deductive suspicion & GUESS on my part because of my ignorance to the program's internal architecture. It may be that Live merely "crosses this bridge" schematically at the wrong time with respect to microsoft runtime and crashes due to conflict as manifest via the authorization window.
3) This is another hypothetical possibility and is just as likely to be an indirect culprit. Because of all the malicious junk going around, Microsoft has released a TON of OS version nonspecific modifications to it's internet connection protocols in the last 6 months to a year. Can you imagine being a software designer/developer and having to keep up with these things? Compatibility and program conflict has got to be at an absolute all time high. The worms, bots and viruses are so intensely dynamic and unpredictable because of all the bigbux money being thrown at them by serious internet criminals, it's not going to get better anytime soon. I know that I have had similar problems with Adobe Audition 3.0 and runtime as well.
