From mailserv@gaia.ucs.orst.edu Tue Apr 26 21:15:17 1994
Precedence: Bulk
Date: Tue Apr 26 14:58:16 PDT 1994
From: gus-music-request@gaia.ucs.orst.edu (GUS Musician's Server)
Reply-To: gus-music@gaia.ucs.orst.edu (GUS Musician's Digest)
Subject: GUS Musician's Digest V6 #25

GUS Musician's Digest       Tue, 26 Apr 94 14:58 PST     Volume 6: Issue  25  

Today's Topics:
               Alternate patch banks (was MIDI Mapper)
                     GUS Musician's Digest V6 #24
                     GUS Musician's Digest V6 #6
             Help - FAQ + fax num for DiskCount please :)
               patch banks GUS Musician's Digest V6 #23

Standard Info:
	- Meta-info about the GUS can be found at the end of the Digest.
	- Before you ask a question, please READ THE FAQ.

----------------------------------------------------------------------

Date: Mon, 25 Apr 1994 18:18:33 -0400 (EDT)
From: Phat H Tran <ptran@sciborg.uwaterloo.ca>
Subject: Re: Alternate patch banks (was MIDI Mapper)

On Mon, 25 Apr 1994, Burns Fisher, VMS Engineering 25-Apr-1994 0847 wrote:

> >The reason you can only work with bank 0 is that virtually all
> >apps that support patch caching always pass 0 for the bank number
> >to the patch caching functions.  To be able to use the other
> >banks, we have to ask makers of CakeWalk, Recording Session, etc.
> >to support multiple banks in their patch caching.  Gravis can't
> >do anything at the driver level.  The only app I know of that
> >takes advantage of multiple banks on the GUS is PowerChords 
> >Pro 2.03.
> 
> So Phat, are you saying that the normal bank changing commands to the drivers 
> would work if only the patch in the alternate bank was loaded?  Also, it would 
> be nice if AG would set up the patch manager to be able to deal with it.

Patch caching in most apps, as I understand it, involves the following 
steps:

1.  The app scans the MIDI file for program changes, making a list of
    what patches the file will need.
2.  The app then calls the patch caching function, usually passing a
    0 for the bank number.  This step might also clear out any old
    patches lying in memory.
3.  The app starts playing the MIDI file.  

Unless you can tell the app not to perform step 2, whatever custom
patches you preload might not be around when the MIDI file is played.
Also, there's the issue of whether or not the GUS MIDI driver categorizes
loaded patches according to their banks.  For example, can both patch 0
from bank 0 and patch 0 from bank 1 be loaded at once and be distinguished
by the driver?  Will the driver keep track of the bank switching
controller so that it know which patch 0 is needed when it encounters
a program change 0?  Right now, I think we can only use patches from
one bank at a time.

Phat.

------------------------------

Date: Tue, 26 Apr 94 9:45:12 EDT
From: rmcclint@tmac.com (Rick Mcclinton)
Subject: Re: GUS Musician's Digest V6 #24

Hello,
 does anyone know of an app. I can get that would allow the creation of a 
waveform from scratch, i.e. with no sampling involved?
Thanks,
rmcclint@tmac.com

------------------------------

Date: Tue, 26 Apr 1994 06:39:39 -0700 (PDT)
From: Seth Delackner <dax@crl.com>
Subject: Re: GUS Musician's Digest V6 #6

Change my E-mail address to dax@netcom.com please
Thanks!

------------------------------

Date: Tue, 26 Apr 94 13:48:00 PDT
From: "Ford, Richard            x2056" <rford@infocomp.csir.co.za>
Subject: Help - FAQ + fax num for DiskCount please :)

Hi all

Does anyone know the location of the soundcard FAQ?

Also, does anyone know what has happened to an outlet called DiskCount 
Software?  I have contacted them in the past but now the fax number seems to 
have been disconnected...any help appreciated!

Thanks a lot - Richard

------------------------------

Date: Tue, 26 Apr 94 10:59:48 EDT
From: echen@verdi.sra.com (Eugene Chen)
Subject: Re: patch banks GUS Musician's Digest V6 #23

Date: Sat, 23 Apr 1994 22:16:27 -0400 (EDT)
>From: Phat H Tran <ptran@sciborg.uwaterloo.ca>
Subject: Using custom patches

: To actually put custom
:patches into bank 0, you must edit the bank 0 as well as the
:[Melodic Patches] and [Drum Patches] sections in ultrasnd.ini
:([Melodic Bank 0] and [Melodic Patches] must agree, and [Drum
:Bank 0] and [Drum Patches] must agree).  Also, only patches in
:the /ultrasnd/midi directory are accessible.  
:

The way i'm set up is, i have my custom patches in [Melodic Bank 0]
using directory f:/mypat. [Melodic Patches] *differs* from [Melodic Bank 0]
and contains the original GM set in ultrasnd.ini 
(using patches from directory e:/ultrasnd/midi).  This seems to allow
me to access my patches inside Cakewalk (which is what I want since I 
have better GM patches on other midi devices, the GUS i just use as
a sampler).  But applications like playmidi, and doom (does doom use midi
or mod?) seem to find the GM set fine.

Does this setup make sense? it seems to work so far. eugene

------------------------------

End of GUS Musician's Digest V6 #25
***********************************

To post to tomorrow's digest:                        <gus-music@mail.orst.edu>
To (un)subscribe or get help:                <gus-music-request@mail.orst.edu>
To contact a human (last resort):              <gus-music-owner@mail.orst.edu>

FTP Sites              Archive                       Directories
---------              -------                       -----------
Main N.American Site:  archive.orst.edu              pub/packages/gravis
                       wuarchive.wustl.edu           systems/ibmpc/ultrasound
Main Asian Site:       nctuccca.edu.tw               PC/ultrasound
European Callers ONLY: theoris.rz.uni-konstanz.de    pub/sound/gus
Submissions:           archive.epas.utoronto.ca      pub/pc/ultrasound/submit
Newly Validated Files: archive.epas.utoronto.ca      pub/pc/ultrasound
Mirrors:               garbo.uwasa.fi                mirror/ultrasound
 
MailServer For Archive Access: Email to <mail-server@nike.rz.uni-konstanz.de>

Hints:
      - Get the FAQ from the FTP sites or the request server.
      - Mail to <gus-music-request@mail.orst.edu> for info about other
	GUS related mailing lists (general use, programmers, etc.).


