1. GIPC111.ZIP Driver
2. Readme File Contents

Readme Driver File Contents (GIPC111.ZIP)

===========================================================================

                  Advanced Gravis Computer Technology Ltd.

          GIPC (GUS Interwave patch Converter) Version 1.0 (Gipc1.zip)

        Copyright (C) 1996 by Advanced Gravis Computer Technology Ltd.
                           All Rights Reserved

===========================================================================

GIPC(GUS InterWave Patch Converter), Version 1.0
Written by Curtis Patzer, Advanced Gravis Computer Technology, 1995

1.0.0 Introduction
GIPC is a DOS utility for converting groups of UltraSound patch files (.PAT)
to an InterWave patch file (.FFF) and data file (.DAT).  ULTRASND.INI or a
user-specified .INI file contains the names of the UltraSound patches to
convert.  Patch numbers are specified for each patch, and patches can be
arranged into Melodic and Drum banks during conversion.  Also, patches can be
put into exclusion groups to control polyphony.


2.0.0 GIPC Operation
GIPC should be run from the directory containing ULTRASND.INI or the .INI file
you want to use.

2.1.0 GIPC Command Line Options
The command options are as follows:

GIPC d:path i:name.ini n:name.fff

        d specifies the drive and directory where the InterWave patch files
          will be built.  The UltraSound patch directory is specified in the
          .INI file (see Section 1.2.0).

        i specifies the name of the .INI file to use for conversion.  The file
          name must end in .INI.  If this option is not specified, GIPC tries
          to use ULTRASND.INI.  If ULTRASND.INI or the specified .INI file
          does not exist in the current directory, GIPC exits.

        n specifies the name of the InterWave patch bank file.  The file name
          must end in .FFF.  If this option is not specified, GIPC will
          create DEFAULT.FFF (and the associated data file DEFAULT.DAT).

        Any other command line option will cause GIPC to display a usage line
        listing the above options.


3.0.0 INI File Information
Look at a copy of ULTRASND.INI.  This is a good place to start before creating
your own custom conversion file.

3.1.0 Melodic Bands
The number inside the square brackets indicates the bank number.  You may
specify as many melodic banks as you wish, as long as each bank has a
different bank number.  Make sure each bank has its own PatchDir line to tell
GIPC where to look for UltraSound patch files.  The PatchDir line must be
before the first patch line in the bank.

The number preceding the patch name will become the program number for that
patch in the InterWave patch bank.  

3.2.0 Drum Bands
The number inside the square brackets indicates the patch number (each
collection of drum sounds or 'kit' is accessed by patch number) for the kit.
You may specify as many drum kits as you wish, as long as each kit has a
different patch number.  Make sure each bank has its own PatchDir line to tell
GIPC where to look for UltraSound patch files.  The PatchDir line must be
before the first patch line in the bank.

The number preceding the patch name indicates the MIDI note number for that
patch in the particular InterWave drum kit.

3.3.0 Exclusion Groups
Sometimes it is desirable to stop one drum sound when another starts.  For
example, if a closed hi-hat sound follows an open hi-hat sound, the open
hi-hat sound should stop when the closed hi-hat sound starts.  Assigning both
the closed and open hi-hat patches to the same exclusion group will do this.

To assign an instrument to an exclusion group, add the following line before
the instrument:

        #exclude:n

where n is a number greater than zero.  Note that each instrument in the
group must have this line before it.

3.4.0 Other Issues
Older versions of ULTRASND.INI have sections called [Melodic Patches] and
[Drum Patches].  These must be after all patches to be converted, because
conversion will stop if one of these sections is encountered.  These sections
are not used by the conversion process, and are not necessary.

You may add comments on lines starting with #, as long as the first word of
the comment is not "exclude".


4.0.0 Things You Need to Know About IW.INI
You will need to change IW.INI to hear your new patches (until Bank Manager
software is available).  Say you have created a patch file called "mine.fff".
To hear sound from this bank, do the following:

Find the [vendors] section and add a new line with your patch file name and a
configuration name (say you chose "mypats").  For example:

[vendors]
rom_amd_1m=ROM_AMD_1_1_ << default patch name. Leave it alone.
mypats=mine.fff         << add this line with your patch file & config names
default=mypats          << change this line to equal your configuration name

Alternatively, you can mix the default patch set with your patches. If you
put your patch file name after the default name, your patches will replace
only default patches which have the same patch number as one of your patches.
Put your patch file name at the end of the line, separated by a comma like
this:

[vendors]
rom_amd_1m=ROM_AMD_1_1_         << default patch name. Leave it alone.
mypats=ROM_AMD_1_1_, mine.fff   << add this line with your patch file name
                                        at the end
default=mypats                  << change this line to equal your config name

Next, you must add a vendor section to indicate where your patch file is
located.  For the above example, add:

[vendor mypats]                 << replace mypats with your defined name
mine.fff=c:\iw\patches\new      << use your patch file name and the path to
                                        your patch file

You will need to reboot (or run iwinit.exe) before you can hear your patches.

[End of File]