bitflipperI'm perfectly happy with AA3, which does everything I can imagine ever needing from an audio editor. Yes, it's old, but it's not like it'll just stop working anytime soon.
I did just try invoking audacity (from a DOS command line, not from SONAR) with a wave file pathname as an argument, and it worked (it's the only command line argument Audacity supports). That, AFAIK, is the only prerequisite for compatibility with SONAR.
SixfingerSo what is it you would do in an audio editor that you couldn't do in Sonar, or prefer to do in an editor?
jbranerSixfingerSo what is it you would do in an audio editor that you couldn't do in Sonar, or prefer to do in an editor? I like to call it from within SONAR to mess around with clips. Also - for finished songs - I use it to trim, run through Ozone 5 for "mastering", and convert to 16 bit for burning to CD. It's just easier with a WAV editor. (but not worth >£200) ;-) For finished songs, you can just export a wave file in 24 bit and process with Audacity for trimming and 16-bit conversion. I use Audacity for all kinds of things, including just simple stereo recording...e.g. converting LPs. Similarly, you can export clips to wave (although that is a bigger hassle to go out and in). I can't imagine what i would do with a clip that I can't do in SONAR...particularly now with Melodyne Editor so neatly integrated.
CakeAlexSAudacity (latest version) backs the file up and then works off that backup file. I think there is an option to turn this off so it works directly on the file.