Hey all, I'm currently in the process of trying to get Tool to compile a bunch of sounds I've made into tags, but I'm having an incredibly difficult time in doing so. I've made every care to avoid a bunch of common pitfalls when getting everything set up for importing, but none of it has helped.

All my sounds are set to 22khz mono uncompressed wav
I have a suitable directory structure in which the sounds are listed (i.e. data\sounds\weap\(x).wav)
I have PolarBear's updated vorbis codecs installed
HEK is correctly installed, Guerilla and Sapien function normally
I am not running Guerilla whilst running Tool

When I go to use tool to import I use the command 'tool sounds data\sounds ogg 1.0'. This returns a message of 'importing data\sounds', and nothing else. When I look in my tags folder, all I have is a blank .sound tag named whatever the upper parent directory is, i.e. sounds.sound, that is 1kb in size.

If I go one level deeper in the directory (data/sounds/weap), Tool gives me an additional message of 'fixed corrupt tag enum field (sample rate*), the sound tag data/sounds/weap may be corrupt', but still bears the same end result.

I'm genuinely stuck. I've followed every instruction and tutorial I can find to the letter, but I simply cannot get Tool to import my sounds regardless of format, directory, target encoding or any other possible variable. Any help as to where I'm going wrong would be deeply appreciated.

You don't need to include the data directory in tool commands.

Sound compiling is probably one of the most bipolar things I go through in halo modding. I honestly have this same problem constantly. Each normally had its own way of being solved. I would try converting the sound, converting it then converting back, changing the sample rate, re-ripping if it is a rip, slightly editing it just to save it again, installing or uninstalling or reinstalling the xbox codec, use something else other than audacity. Sound compiling is very frustrating for me.



Quadruple check directory.

One thing I should probably also mention is that I am running Windows 7, but I had the same results on a Windows XP virtual machine. Does Halo's installation directory matter?

I've never had a single issue compiling sounds. Lets see how your setup is.

What program are you using to compile you sounds and what is EVERYTHING in those settings?

Did you update your OGG files? http://hce.halomaps.org/index.cfm?fid=1632 (Backup originals because people who don't compile sounds with these (higuy), these may make those maps exception)

Also:

Edited by MatthewDratt on Oct 8, 2014 at 09:24 PM

I use Reaper to edit and render. I render everything at 16 bit, 22khz, mono, as an uncompressed PCM wave file with the .wav extension.

And yeah, I do have the updated ogg vorbis codec DLLs installed.

EDIT: Saw the part about not including 'data' in the command all to late. I feel like a complete idiot. Thanks a ton for pointing that out!
Edited by beaucephal on Oct 8, 2014 at 09:59 PM

Maybe I should rephrase this to make it more obvious.

You should NEVER include the "tags" or "data" directory in tool commands. It's not a suggestion, simply just don't do it.

It would appear that I am a bit dense because that solved it. I feel like a complete idiot now. Thanks a whole ton!

Mistakes happen. :)

My advice for compilign sounds for halo is using windows xp (virtual machine is good enough), and compilign it in there without any of the new ogg codecs installed.

And if you feel like being 100% sure the sounds wont make you exeption:
http://www.mediafire.com/download/y61e2x2be92xugq/xb_adpcm_codec+%28Windows+XP+Only%29.rar
The Xbox ADPCM codec