Rusty K said:
So you burned a data CD of the program and copied the email with the authentication codes as well?
Yup, that's what I did -- it worked well for my peace of mind. :>)
Cool edit pro isn't perfect - I've had little glitches now and then, but nothing compared to N-Track (I too am an N-Track refugee!).
Some of the things I particularly like about CEP --
Locking effects on tracks - what a great way to free up CPU!
The sound of the compressor -- very smooth and nice, imho
Premixing -- again, it really helps CEP to work well on lower end hardware, or even if you have bigger iron, it helps with letting you run cpu hungry effects and lots of tracks
Included effects - wow, what a package
Recovery file -- when CEP has had a problem, its always been able to recover for me when I loaded the file next time. Granted, that's been rare, but its nice to know it tries if things DO get dicey. For example, if I use an directx plugin from someone else that crashes (hardly CEP's fault) -- it is typically able to recover my work.
Superb editing
Some of the things I don't like as well --
Automation is clunky -- it works, but I prefer real-time recording of automated events
Directx effects only -- unless you use a wrapper
Having to "refresh" the effects for new ones to show up (no big thing once you know it, but frustrated me big time figuring it out)
For me, I've ended up with a three-program attack on the music -- Sonar2.1, CEP2, and Ozone2. I use Sonar for its multitrack mixing down and automation. (I'd rather use CEP2 for the reasons above, but drawing the automation just got too clunky for me) I use CEP2 for editing any files, and for mastering the final stereo mixdown. I use Ozone2 to help me with the final mastering, and occasionally as a killer plug on particular tracks. The combination of these three is working very well for me - they complement each other nicely.
Good luck - and good tracking!
-lee-