Audacity Forum

Hey all-

I've been compiling my own Audacity (as I need ASIO support). It works great, but I'm curious about one thing. (I'm an old *nix geek but have never before even tried to compile anything on any flavor of windows). I'm using M$ Visual Studio 2008 Express, and even with every possible optimization set, the Audacity benchmark's edit portion is a little slower on my .exe than the non-ASIO one I downloaded from y'all. (The data check is a bit faster on my compiled version, which is compiled from a CVS checkout that I updated today.)

Of course, this doesn't matter even a tiny bit, as I don't need to play 200 audio tracks at once, but I'm just curious what compiler was used for the distribution .exe, and what flags were set. (I've heard that they make gcc for windows, so that may be the answer... and gcc would understand me when I say '-march=amdfam10', too!)

Anyway, useless question, but I'm compelled to ask it. It's an obsessive-compulsive geek thing. :p

speef wrote: I've been compiling my own Audacity (as I need ASIO support). It works great, but I'm curious about one thing. (I'm an old *nix geek but have never before even tried to compile anything on any flavor of windows). I'm using M$ Visual Studio 2008 Express, and even with every possible optimization set, the Audacity benchmark's edit portion is a little slower on my .exe than the non-ASIO one I downloaded from y'all. (The data check is a bit faster on my compiled version, which is compiled from a CVS checkout that I updated today.)

Of course, this doesn't matter even a tiny bit, as I don't need to play 200 audio tracks at once, but I'm just curious what compiler was used for the distribution .exe, and what flags were set. (I've heard that they make gcc for windows, so that may be the answer... and gcc would understand me when I say '-march=amdfam10', too!)

We use VS 2008 Express and you can see the optimisation for audacity.sln if you check out a fresh copy and look in VS at Project > Properties then under Configuration Properties > C/C++. If you build Debug it will be slower than Release, other things being equal.

I would not set too much store on the Benchmark (a bit faster/slower is likely to be within margin of error).


Gale