PasMix Version 0.2 (beta)
(C) 1994 John V. Schweinfurth

Program Description:

    This is a replacement for the MediaVision Promix/2 program.
You need one of the Pro AudioSpectrum16 series of sound cards
to use this program.

Requires:
  OS/2 2.1GA or higher with the MediaVision MVPRODD.SYS driver.
  (It might work with 2.0 + Latest Service Pack)


Improvements:

    The big enhancement is that this program remembers the mixer
settings whereas ProMix/2 doesn't.  This is the one you've been waiting
(and waiting and waiting) for.

Limitations:

1.  Only one set of mixer settings will be retained.  Whatever your
settings were when you closed the program is what you'll get the next
time.  I plan to add the ability to save multiple sets of settings
soon.

2.  One of my first beta testers pointed out the fact that this program
and the MMOS/2 volume controls do not get along - I do know why this is
happening and I am investigating possible solutions.  Part of the problem
is due to the multitasking design of OS/2 and MMOS/2.  It seems possible
to make everything get along but I can't promise anything here.  The best
workaround at the moment is to set both the MMOS/2 Master Volume and the
PasMixer master volume to the same settings.  I use 70% on my machine.  This
seems to minimize most of the volume jumping effects.  Also, with most
MMOS/2 apps, if you do not use (move) the app's volume control, the volume
will stay at the setting set by PasMixer.

3.  As you may have discovered,  you can not start a WinOS/2 session while
this program is running *if* you are using multimedia sound in Windows.
Likewise if you have a WinOS/2 session running and try to launch PasMixer,
PasMixer will not start.  This is due to Windows sound drivers grabbing the
sound card and not letting loose.  The solution is to install the Windows
version of "Promixer" and set it to "inherit DOS settings."  Start up
PasMixer.  Set the settings you desire then close PasMixer.  Start up your
WinOS/2 session.  The mixer settings should now be identical. 

Using the Program:

1.  Copy the files to any subdirectory of your chose. Run it from the command
line (PASMIX) or create a program object.  If you are installing over version
0.1 of this program you must delete the old "PASMIX.INI" file before you run
this version (0.2) - sorry about that but this was unavoidable.  The program
will automatically recreate the ini file when you exit.  Also the support file
BPMCC.DLL must be in a directory on your LIBPATH statement.  You can safely
copy this file to your \OS2\DLL directory if you wish.  This comes from
Borland not I.

NOTE:  I foresee the pasmix.ini file format changing at least one more time
in order to implement multiple sets of mixer states.  In the future it will
be wise to delete this file when installing a new version of the program.
 
2.  The controls should be self explanatory with one exception.  The balance
(pan) control is shared between the various channels. For example, to set the
balance control for Aux channel, first click on the Aux volume slider - then
adjust the balance.  Also, the Loudness and Enhancement channels are set to
0% or 100% with no in between.  I may add variable setting support later if
folks ask for this.

3.  You can place this program in you system startup folder to automatically
set your sound card at bootup time.  Currently this program supports one
commandline argument which is /so.  This means "set only." if you enter
pasmix /so at the commandline the program reads your saved state from
pasmix.ini, sets the mixer, then displays the program about box to let you know
all went well.  At this point click the OK button and the program will terminate.
This command was designed to be used in conjunction with the program object in
your startup folder - enter /so on the "parameters" line.  Once I decide the
details of saving multiple mixer state there will be more options with this
parameter.  

4.  The "Save Settings" and "Load Settings" on the system dropdown menu are not
implemented yet.  You can select them, but nothing will happen.

5.  For Pro Studio owners:
    I believe that I have enabled the "Input" master control but I have no way
to verify that this works.  My "D" series card does not support this feature.
I would appreciate some feedback (no pun intended) from anyone with a 'Studio
card.

Disclaimers:
  
   I am not connected to MediaVision in anyway.  I just happen to own one of
their PAS16 cards.  Currently this program (the executable) may be considered
freeware. If you think this program is useful, feel free to encourage me with
a small donation.  If you think the program is garbage, use the del command.
 
   If you share this with others please use the original, intact zip-file.
I do not plan to release the source - mostly because I don't want to be
embarrassed should you see my "design at keyboard" style.  Also because of
potential "Licensing" snags. - Really - says so right there in my Borland
compiler's "Licensing Agreement."  Can't do it even if I wanted to.

   This is my first attempt at OS/2 and PM programming, so far I think the
effort is going well.  If you disagree, please send all hate mail and jeers
to MediaVision - they are use to it<g>.

Bug reports, suggestions, comments and any kudos etc. will be taken by myself

John V. Schweinfurth

Compuserve: 73777,671
Internet  : 73777.671@compuserve.com 
         or rabidog@novalink.com

US Snail Mail:
    1211 Gold Coast Rd Apt 11
    Papillion, NE 68046

Also, you might find me on Pete Norloff's OS/2 Shareware BBS but Compuserve
is your best bet - I check mail there at least once a day.

Commentary:
    
    For the record, it took me exactly >>6<< lines of "C" code to implement
the save/restore mixer settings feature in this program.  Why MV could not
do this themselves is anyone guess.... good day....

Oh, yeah almost forgot...

ProAudioSpectrum 16, ProStudio 16, PAS16, ProMix and all derivatives are most
likely registered trademarks of MediaVision Inc.

OS/2, MMOS/2, WinOS/2, PM etc. are most likely registered trademarks of IBM Inc.

Windows is owned by you know who - that's right - MicroSoft Inc.

NO, NO, AAAAHHHH, Please anything but the "Trademark Police"