).So, with that in mind, understand my mild horror as I opened a T2 project last night and found that all the new Mackie plugs passed sound but the meters were blank. A quick check revealed that the plugs all still indicated being registered to me, but, paradoxically, had generated a new "machine ID code". I did nothing to bring this about, except possibly adding a couple plugs to my VST folder and rescanning. No hardware was changed and nothing was done to the Mackie folder.
I tried reinstalling. No luck. I then tried the original keyfile. Then things progressed further in to th s/w Twilight Zone as the plug first told me the keyfile was invalid, then reverted to "unregistered", but switched back to the original machine ID. I was then able to run the keyfile and the plugins were active again. End of story? You better believe it wasn't.
This morning I happily opened said T2 project again only to find the Mackie plugs inactive once more, reporting as registered in my name, but exhibiting the second machine ID again.
I'm hoping this is a fluke and I will obviously email tech support and tell them they owe me a new keyfile for the first machine. I don't intend to use up my second machine license for this (perhaps only to find that it happens again two more days into the future).
C/R is the devil. It wouldn't actually be Beelzebub incarnate if it would just work and not be hypersensitve to every little h/w change and even to out and out delusions like this Mackie c/r program has just done. Incidentally I'm about to have to ask for another response code for my Princeton reverb, which uses PACE c/r, because swapping out a h/d encouraged it to decide that I am in fact on a new machine. Second time in a month I've had to reacitvate the Princeton for no real reason at all, really.
