quakesounds | Audio processing pipeline for Quake sound samples

quakesounds is very configurable, but you can ignore a lot of the details for starters. In this quickstart section we’ll create some sound files as quickly as possible; the next sections will describe what is happening in more detail. Victory! But now let’s take a closer look at what is going on there. If you want a different sound selection, or you want the sounds to be louder, or softer, or in a different format, or with different names, or changed in any other way…​ hang in there and keep reading.
If you’re using a quakesounds distribution that has internally-bundled utilities, skip ahead to step 2. Otherwise, if you’re using your own external versions of sox and ffmpeg, then make sure that those utilities are installed and ready to go. For the purposes of this quickstart, sox and ffmpeg (or on Windows, sox.exe and ffmpeg.exe) need to be placed in your executables path — i.e. running them should not require typing their entire path.
If you’re going to run quakesounds from a command prompt, make sure that the working directory for that command prompt is the directory where the "quakesounds.py" file is located.
Now run quakesounds once, using "quakesounds.py" (as described in LAUNCHING.md).
You should see a "quakesounds.cfg" file appear in that directory.
Now make sure that that directory also contains the file "quakesounds.targets" that came with the quakesounds distribution.
Copy your "pak0.pak" and "pak1.pak" files into that same directory.
Run quakesounds again. (You may see a warning or two about "clipping"; this is expected. If you see a lot of warnings, your version of the SoX utility may be old.)
You should see a "quakesounds_out" subdirectory appear. "quakesounds_out" should contain several files with the m4r extension; these are gain-normalized, iOS-alert-sound-ready versions of a few selected Quake sounds.