This is a vicious cycle. I launch N6.0.6, then I load my project, then I turn on the controller. 7 out of 10 times I’ll just start working on my project. But the other 3 times sets off a catostrphic chain of events.
In this chain, I launch N6.0.6, then I load my project, then I turn on the controller. The controller has dropped it’s connection with Nuendo. So I close Nuendo and go check the Eucontrol to see what’s going on. The first couple of times, I would add HUI protocol. I’m not using it. I just want to “wake Eucontrol up.” The goal is just to make the apply button activate, which means that I’ve awakedned Eucontrol. Sometimes I cancel, other times I might hit apply and go to close Eucontrol. When I hit close, I get the “blue screen of death!” I run down the hall to the machine room to physically turn the PC off. I reboot the PC.
When I get back into the studio, the PC is booting and asks if I want to start windows normally. I say yes, as its the ONLY option offered. It reboots and my desktop comes up, IF I’M LUCKY. If I’m not, my desktop comes up with all of my icons scrambled and one of my monitors has switched to the lowest resoution possible. Now I’ll lose another 8 - 10 minutes getting my screen resolution back and putting all of my icons back in their “normal” positions.
Then I start Nuendo. Then I open my project. Now the project stalls on opening because the crash ALWAYS drops the connection with my VSL dongle and thus claims I have no license for the VSTi’s. I go back to the machine room and reset the dongle. I tell it to try again and the project opens. Then I turn on the MC Control and, with the connection restored, it works like it’s supposed to. Total loss of time? 6 to 10 minutes, if the desktop “holds” and 20 to 30 minutes if it doesn’t!
So the obvious question is:
- Why is Eucontrol dropping the connection?
- Why on earth does it make my PC crash when it does drop the connection?
3) How can I get it to STOP doing this?!!?