 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Summary |
The quake 3 wav loader seems to be a bit limited in the data it can handle. Instead
of searching through chunks based on the lengths in the file, it just looks at every
4 bytes in turn looking for the chunk headers. This doesnt work if a chunk before
the DATA chunk is not a multiple of 4 bytes long - for example the fmt chunk on
newer WAV files. When loading music it seems even more restricted, in that it appears
to assume the DATA chunk will immediately follow the fmt chunk. This causes quake3 to report "No data chunk in <filename>" on the console when it tries to load the wav file. FixWAV is a small program which changes 26 byte fmt chunks to 24, thus fixing this problem. I've only tested it with wav files created by the version of Sound Recorder bundled with WindowsXP, but I understand other programs also generate similar files. As of version 1.1 It also strips FACT chunks which appear to cause a similar message when you are using the /music command.
|
| Download and Installation |
To install, simply unzip the FixWAV.exe to somewhere - in a Quake3\tools directory or similar may be appropriate, but its up to you.
|
| General |
 Simply select the "Load" button, and choose the wav file you want to fix. It will then load it into memory (so if its very big, I hope you have enough RAM), and obtain various bits of information about it. If the wav file needs fixing, the "Fix" button will be enabled. Selecting this button will then change the wav file in memory (updating the info displayed - double check the "DATA chunk off 4 byte boundary" - hopefully this should change to "No"). Having done this, then click Save As, and choose where you want to save it.
|
| Compatibility |
So far, this seems to fix the problems that people have been having - however it only
fixes the known problem of the fmt chunk being 2 bytes too long - if there are other
problems with different wav files then it will still report that data chunks are not
on a 4 byte boundary, but not offer the fix option. If this happens, then send me a small sample with this problem, and I can check what specifically is different about those wav files.
|