OS/2 Shareware BBS: Multimed/Multimed.zip/mxcs2_13.zip/readme

Text File | 1998-02-09 | 6KB | 142 lines

README for mx3DXG, mxOPL, and mxCS2 Mixers

----------
9-Feb-1998
Changes made to version 1.3 of the mx2 Mixers

The Paradise.sys driver has been updated to 1.90.  See readme.sb for more.

Note: If you have changed your 4232-based soundcard to a 4235 or later,
you may find that the volume levels are distorted.  Delete the mx*.ini
and restart the mixer.

A mode-3 mixer is available:  mxCS3.  See http://40th.com for more.

The wacker.sys driver for OPL3SA2/SA3-WinOS2 support has been removed
from the general distribution.

-----------
27-Nov-1997
Changes made to version 1.1 of the mx2 Mixers

1. Option to assign control names

   There are several possible connections that the OEM can use
   when hooking up the hardware.  For example, many CS-based
   soundcards hook the MIDI output level to the "Line In" hardware
   control, and the external line input to the "Aux 1" control.
   These switches let you name the control as it appears in the
   mixer, so you could use -lin=MIDI.  If a space is needed,
   include the switch in double-quotes, for example:

      [C:\]mxCS2 -lin=MIDI "-aux1=Line In" -aux2=CD

   Once assigned the names are stored in the mixer's ini file so
   you don't need to include them on the command line again.

      -lin=<text>    Name to give "Line In" control
      -aux1=<text>   Name to give "Aux 1" control
      -aux2=<text>   Name to give "Aux 2" control
      -lout=<text>   Name to give "Line Out" control (CS4232 only, mxCS2)
      -ad=<text>     Name to give "A/D" control (mx3DXG only)
      -mstr=<text>   Name to give "Master" out control (mx3DXG only)

      -resetnames    Restore default names to controls


2.  Main window can have a solid- or mixed-color palette color dropped
    and that color will be used until a new color is dropped on.  The
    color is stored in the mixer's ini file.

      -resetbg       Restore window color to system default

    Restart the mixer to set all the controls to the new color.


3. C/P boxes in ADC box are now updated only when they change states, rather
   than each VU/OR/SyncLock update.


Note:  The OS/2 Crystal driver runs CS423x chipset-based cards in
mode 2.  This means the mode 3 mixer features cannot be used.  mxCS2
works with any Crystal CS4248,4231,4232,4236,4237B,4238-based
soundcard in mode 1 or mode 2.  More detail is in mx2.doc and below.


Note: While Paradise apps do not require MMPM2, if you have a PnP
soundcard you will need some method to activate it.  This usually
means that you have to use the OS/2 driver.  If you get a 9053
error, EPS_MIXER_BAD_PORT, it either means you have not activated
the PnP of your soundcard or that you have entered the wrong base
port.  If in doubt, you can check either the output of

        [C:\]rmview /io

or by looking at the DEVICE=driver.sys line in config.sys.  PnP
may ignore settings used on the DEVICE= line so you should use
rmview if possible.  As always, installation support is available
to all so email [e-mail] if you have -run out- of ideas.

Paradise apps can co-exist just fine with MMPM software, even
from Win-OS2.

-----------
16-Aug-1997
Verion 1.0

 - See mx2.doc for complete installation instructions

 - The MX2 line of mixers are for the following hardware:

   mx3DXG:  Mediatrix Audiotrix 3D-XG
   mxOPL :  Yamaha OPL3-SA, OPL3-SA2, OPL3-SA3 (YMF701/711/715)
   mxCS2 :  AD1848/CS4248, CS4231, CS4232, WSS and compatibles (mode 1/2)

 - mx3DXG and mxOPL require that the base port be entered +4 over the
   DEVICE= base port (for example: "534" and not 530).  See mx2.doc,
   Basic Setup, Stage 2, for more.

 - mx3DXG requires the MIDI base port to be entered directly after OPL3-SA3
   base port (for example: "534,310").  See mx2.doc, Basic Setup, Stage 2, for
   more.

 - mx3DXG and mxOPL (for OPL3-SA2/3) require the control port, as specified
   on the DEVICE= config.sys line.  mxCS2 (for CS4232+) requires this for
   karaoke mode.  See mx2.doc, Basic Setup, Stage 2, for more.

 - Each mixer application is tuned for its applicable hardware, with all
   mixer functions fully supported.  Each mixer is a separate application:
   use/order the version specific for your hardware, as listed above.

 - The documentation provided includes common information to all the MX2
   mixers, with specific features isolated on a per-mixer basis.  You can
   ignore that which does not apply to the mixer you are using.

 - The application workspace color (the mixer client area) is displayed in
   the current WPS settings.  By default OS/2 uses white for the application
   workspace, which will look a bit odd with the dialog-colored controls.
   To change this scheme start the OS/2 Scheme Palette object and modify
   any of the available schemes so that the "Application Workspace" is the
   color you want (use the "Dialog Background" values as a starting point).
   Once done (only takes a few seconds to change) drag the object onto the
   desktop (you must hold down the Alt key to affect the entire system).
   The Scheme Palette is found in the System Setup folder.

 - The included program is a fully-functional working demo.  This software
   is provided for evaluation use only.  See _order.* to obtain your
   personalized registration code to unlock the non-demo version of the
   software (one registration is required for each computer using the
   software).  Read the license agreement, in mx2.doc, before use and
   before ordering.

 - Registration is valid for all in-version releases (1.x) of the software,
   and free technical support is included for 120 days from the date of
   purchase.

 - Support is limited to basic installation until you have registered.

 - Specifications, price, and availability are subject to change.

 - Use _order.cc to order by credit card through BMT, otherwise _order.frm.