Originally posted by OdessaCubbage
I run windows x64 bit and winamp works fine with the 32 bit version, a program like winamp does not need the full potential of 64 bit processor. Even if you run a 32 bit program in windows x64 it still gets a slight proformance gain anyway.
Also setting the compatability setting just tricks the program to thinking that it is running on a different operating system, it does not actually make the program function differently.
I need to throw my two pennies in here and contradict this statement. There is nowhere that I have seen (aside from processor intensive applications like video and audio encoding,) that 64bit has ever helped a 32bit application running under a 32bit emulated environment. In fact, the simple word 'emulate' thusly implies performance hit automatically. The only reason a 32bit application gets any performance boost is if the 64bit environment has Physical Address Extensions enabled, which is a 32bit feature to allow addressing of more memory with less hit to performance. (It causes a sort of doubled effect, since 64bit can address craploads more memory a lot faster, tie that in with a 32bit tech that does the same, whatever they do together works.)
Now, as far as a 64bit winamp? I would not go that far. 64bit NSV encoding tools, sure, 64bit mp3 encoding tools, sure. You're right, Winamp doesn't need all that extra power and memory addressing. Honestly, when does it ever need it? Answer is only when it's gotta do everything software. Winamp used less than 5% CPU time at any given polling on Task Manager, and now in my 64bit with winamp under the WOW64 32bit emulation service, it uses less than 2%, but just to be fair, the only time i see it is when it does spike up to 2% in the middle of a song (reading from HDD) or changing songs (also reading).