So, I have been rather bored recently, and I decided to try and make some gun sound effects. But before I continue making them, I would like some feedback. Test tracks downloadable here
test pack includes the assault rifle (4 different distances), the magnum (3 different distances), and the sniper (also 3). Please let me know what you think.

You mean like this?
http://www.mediafire.com/?99jm3513meanclw
Sniper Variation x5

not spamming at all! Actually, the reason I didn't convert them to sound tags was that tool (and apparently, every variation of it) does not work in windows 8. I will do this once I get my old desktop back that has widows 7

Tool seems to work fine for me, althought I haven't tried compiling impulse sounds using the Xbox coding yet, I heard its got issues.

I has windows 8
Windows XP on my old PC. If I am desperate to compile a sound, I could probably dig it out.
Edited by Jesse on Apr 1, 2013 at 02:03 PM

32 or 64 bit?

Tool works just fine in Window 8. You are most likely having a permission issue in that you cannot write to protected folders such as C:\Program Files (x86) or C:\Program Files. This is the way it has been since Vista. Either run tool (or the command prompt) as administrator or login to your machine as the administrator and change the permissions of the C:\Program Files (x86)\Microsoft Games\Halo Custom Edition folder and tree to allow write permissions for users.

The strange thing is the different function levels of the different versions of tool for me. In the same folder, I have tool, tool++, and os_tool. Tool instantly closes upon opening, tool++ stays open but freezes upon trying to create sound tag, and os_tool stays open and does not seem to freeze. All three are located in the same folder, C:\Program Files (x86). I shall still try what you said.

Tool is a command line program and does not have a GUI interface. When you run tool you specify the commands on the command line like so:

tool.exe build-cache-file levels\d40\HCEC_engineroom

You can get a list of available commands by opening a command prompt in the folder that tool resides and typing:

tool help

64 bit with a must-have classicshell.

I HATE METRO

what I meant was that that I don't even get time to type in a command. After further research, I have discovered that tool insta-closes no mater what, tool++ opens but freezes, and os_tool only opens through the desktop shortcut.
video of what I mean

thank you sparky, this actually helped a lot. And I didn't show the problem with tool++ for the sake of time. It freezes after I have selected a command.

You misunderstand. You can't run tool by clicking on it, you have to open a command prompt then type (on the keyboard): Tool {command}