home *** CD-ROM | disk | FTP | other *** search
- WM DFT2WAV
- ──────────
-
- WM DFT2WAV converts compressed DFT files created by WM WAVtoDFT {WAVtoDFT}
- to playable WAV files.
-
- IMPORTANT: WM WAV2DFT is a 32 bit program running in protected mode and
- requiring a 386 or higher. If you have a 286, use WM DFTtoWAV
- {DFTtoWAV} instead.
-
- If you do not have a Floating Point Unit (386 without 387 coprocessor, 486SX)
- you must provide a protected mode 387 emulator. Don't worry: there is one in
- the EXE\ subdirectory (EMU387). For WM WAV2DFT to find it, you must SET the
- DOS environment variable GO32 as follows (if you do not know about DOS
- environment variables, see your DOS manual):
-
- SET GO32=EMU <full EXE\ path>EMU387
-
- If WAVmaker's home directory is C:\WM\, the actual command will therefore be
-
- SET GO32=EMU C:\WM\EXE\EMU387
-
- It can be issued either from the DOS prompt or in a BAT file, and should be
- included in WM.BAT {WMstart}.
-
- Note that using an emulator is MUCH slower than having the real thing!
-
- It is also advisable to add the word "NODPMI" to the GO32 variable, as in
-
- SET GO32=NODPMI
-
- if you do have a FPU, or as in
-
- SET GO32=EMU <full EXE\ path>EMU387 NODPMI
-
- if you don't. This prevents WM WAV2DFT from using DPMI even if a DPMI server
- is found on your system. Otherwise, the program may crash due to limitations
- imposed by DPMI stack management.
-
- If DOS reports insufficient environment space when you try to SET GO32, you
- should increase the environment size reserved with the SHELL directive in
- CONFIG.SYS. See your DOS manual for details. Note that some shell programs
- do not use the COMSPEC variable in order to locate the command processor.
- Such programs will not be affected by the SHELL directive. If you are using
- such a program and are experiencing environment size problems, you'll have
- to shut it down before starting up WAVmaker. This will allow DOS to use the
- environment size specified in the SHELL directive.
-
- Unfortunately, the algorithm employed by WM DFT2WAV is not suitable for the
- disk-based approach used by most other WAVmaker applications. The full WAV
- file must fit in (extended) memory. Needless to say, larger sample files
- require more memory. With 3 MB of extended memory, you should be able to
- handle 3 seconds' worth of sound data at the highest allowed sampling rate
- (44.1 kHz). Stereo channels are handled separately, so that's actually 3
- seconds' worth per sound channel. The word size employed in the WAV file
- makes no difference as far as memory requirements are concerned, but it is
- reflected by the size of the compressed file.
-
- Usage: DFT2WAV <source> [<destination>]
-
- If no <destination> is given, the <source> filename is used. The
- default extensions are DFT and WAV, respectively. The default
- directories are DFT\ and WAV\; you can override these choices with
- the /DFT and /WAV options.
-
- Options: /DFT <source directory>
- /WAV <destination directory>
- /q (quiet mode: no screen output)
-
- The following title:value pairs are written to WAVmaker's public Function key
- file {FnKeys} upon successful termination:
-
- File #1 : <source>
- File #2 : <destination>
- DFT file : <source>
- WAV file : <destination>
-
- WM DFT2WAV was compiled with DJ Delorie's ** free ** DOS port of GNU C++,
- DJGPP {DJGPP}. Check it out! The FPU emulator EMU387 {EMU387} is distributed
- together with DJGPP, and is subject to the standard GNU General Public
- License {GNU}.