This program allows you to store any information in any .WAV file. The .WAV can be 8 or 16 bit. The information is stored in such a way that it does not affect the sound of the .WAV in any way. An 8 bit file will contain a detectable 'hiss'.
There is really no reason you would want to hide something in a .WAV, unless you wanted to keep something hidden in plain sight. This is kinda like Steganography where you hide stuff in pictures. You can choose how many bits of each sample are overwritten in the sound file. 'None' means just the lower bit is written. Two or Three redundant bits can be added to make the sound a bit more persistant in the .WAV file. The more bits you choose to write into the .WAV, the louder the hiss is, however on a 16-bit 44.1khz stereo .WAV I can't hear anything even with three redundant (4 total) bits per sample.
Its pretty straight forward to use. There are a lot of bugs. Don't try to open a .WAV you just created with this program. The file dialog says 'OPEN' even when it means 'SAVE'. No big deal.
** Update (5/9/00)**
Two things: First, hideit will automatically attempt a 1, 3, or 4 bitper sample (averaged) load of any file, and will set the correct radio button coresponding to what it finds.
(not shown in picture)
Second, you can select the "magic number" hideit uses to embed something in the .WAV file. This allows you to 'sort of' password protect your hidden stuff.. please keep it at 8 characters, since its a HEX DWORD and the program probably will have mega problems if you type something like "SECRET" into the window. The default is 0xDEADBEEF. Anyways. Try it out.
** Update # 2 (5/11/00)**
Alright.. Well, you can now SUCCESSFULLY rip a Redbook CD-audio track, embed your file, and then reburn it into a new CD-audio track, then rip it at a later date and recover your data!! Yes!.. I am able to do this even with only 1 bit of data per sample (so its completely undetectable!). The reason it didn't work before was that the ripped cd-audio sample would have some random number of samples on the front end (52 in all cases I've seen). This came about either because of the burner program padding some '0' samples at the beginning, or the ripper grabbing some junk at the begining. Either way, its fixed now, as the program will slide a 'window' over all the bits in the sound stream looking for the magic ID. This was necessary because when this offset occurs, the data BYTES are no longer aligned to every 8 samples. Since PC's are little endian, and I encode all the bits backwards, this was a serious headache. I would like to share my headache with you by showing you the code that does this.
So go ahead and download it, and start hiding stuff!
Send me any comments
Download it HERE