dwdonehoo
09-05-2003, 09:09 PM
I have been installing and giving Absynth 2 a run, and found a few annoying things so far:
1) Registration (i.e.: copy protection) is a real pain in the rear end. You have to enter the serial number, enter it a second time during on-line registration, get a generated machine specific code, send it, get authorization, enter it, then run. But there is a catch. During the online registration, there was no \"Absynth 2\" in the drop-down list, my SN did not work for just \"Absynth\", so basically I am screwed until I work this out directly with them. I will be able to use it for 30 days meanwhile and put up with the nag dialog. So I email them, and now 8 hours later, no reply. I called them, but a message said they were closed (is today some kind of German holiday?) and to call during business hours (it was 10 AM, so it WAS during business hours). So far, no call back, and I cannot get through. Stupid CP. I don\'t like this at all. Suppose I come to depend on this product and NI goes under? Then the next time I change anything in the system and need to go through this registration tap-dance, well, I am screwed (and I will have to look for a crack). The SN should be enough. Another case of messing with the customer for a false sense of security. Bah!
2) Most disturbing, is the program is CPed to the machine it is on, and will only grudgingly allow a total of two installs before you have to call and dance with their customer service. This was not the original goal of CP: it was to keep more than one person from using the product. Now, you can only use it on one or maybe two machines (and they say not simultaneously), which is plain stupid. I probably may not have any use for more than one or maybe two instances running at once, but the problem is that I need to distribute the CPU load. It may be just too darned crowed on my main DAW, so I would like to have another CPU pick up the load and have that songs part played on THAT computer instead on my main DAW. But they only want you using it on ONE CPU. How silly is that when you can open multiple instances within your sequencer or on a multi-instance host like VStack? Too many lawyers and not enough thinking. Yet another case of messing with the customer for a false sense of security. I hate stuff that has usage problems like this...
On the plus side, Absynth 2 sounds fantastic, and I find nothing wrong with the product itself. Now if I could just get through this ridiculous time-consuming pointless registration process...
1) Registration (i.e.: copy protection) is a real pain in the rear end. You have to enter the serial number, enter it a second time during on-line registration, get a generated machine specific code, send it, get authorization, enter it, then run. But there is a catch. During the online registration, there was no \"Absynth 2\" in the drop-down list, my SN did not work for just \"Absynth\", so basically I am screwed until I work this out directly with them. I will be able to use it for 30 days meanwhile and put up with the nag dialog. So I email them, and now 8 hours later, no reply. I called them, but a message said they were closed (is today some kind of German holiday?) and to call during business hours (it was 10 AM, so it WAS during business hours). So far, no call back, and I cannot get through. Stupid CP. I don\'t like this at all. Suppose I come to depend on this product and NI goes under? Then the next time I change anything in the system and need to go through this registration tap-dance, well, I am screwed (and I will have to look for a crack). The SN should be enough. Another case of messing with the customer for a false sense of security. Bah!
2) Most disturbing, is the program is CPed to the machine it is on, and will only grudgingly allow a total of two installs before you have to call and dance with their customer service. This was not the original goal of CP: it was to keep more than one person from using the product. Now, you can only use it on one or maybe two machines (and they say not simultaneously), which is plain stupid. I probably may not have any use for more than one or maybe two instances running at once, but the problem is that I need to distribute the CPU load. It may be just too darned crowed on my main DAW, so I would like to have another CPU pick up the load and have that songs part played on THAT computer instead on my main DAW. But they only want you using it on ONE CPU. How silly is that when you can open multiple instances within your sequencer or on a multi-instance host like VStack? Too many lawyers and not enough thinking. Yet another case of messing with the customer for a false sense of security. I hate stuff that has usage problems like this...
On the plus side, Absynth 2 sounds fantastic, and I find nothing wrong with the product itself. Now if I could just get through this ridiculous time-consuming pointless registration process...