Answers to the Most Commonly
Asked Questions About the
Multisound Sound Board


We at Turtle Beach systems would like to thank you for purchasing the
Multisound board. We hope you enjoy the superior MIDI and hard disk
recording capabilities of your card. Below are listed the questions most
commonly asked of our technical support staff. If your question is not
answered below, please feel free to call our technical support line at
717-843-6916 or leave a message on our 24hr. Beachcomber BBS 717-845-4835.

**Note** The Multisound's 1.1 driver update is now available. You can get
this driver off of The Beachcomber BBS mentioned above, or off of
Compuserve. The file that you should down load is MSND11.zip. If
you do not have access to a modem and have not already received this
driver update, you should call Turtle Beach Systems at 717-843-6916
and we will be happy to send the new drivers to you.


SECTION 1: INSTALLATION QUESTIONS.

Question 1: When I go to install my drivers from the Control Panel, I get the
message "No OEMsetup.inf". How do I set up my drivers?
Answer: You probably have our Multisound 1.1 drivers disk which uses a
different install procedure. The version number of can be found at the
bottom of the label on the Multisound drivers and applets disk. To
install the 1.1 version, simply run setup.exe from Windows File
Manager.


Question 2: When I go to reinstall the 1.1 drivers or to install them over my
1.0 drivers, I get the message "EMMExclude not as expected." What
does this mean?
Answer: When the 1.1 driver installs, it puts an EMMExclude statement into
your Windows System.ini file. Because we don't want to interfere with
any of your Windows setup, we check the System.ini for other EMMExclude
statements. This message simply means that a statement has been
detected and that you may want to check your System.ini to make sure
that you are not installing the Multisound in a memory slot already
excluded by something else in Windows. What you may want to do before
you re-install a driver is to edit your c:\windows\System.ini file.
Check the [386enh] section for a statement like EMMExclude=D000-D7ff
(the default memory address of the Multisound). If you do find an
"EMMExclude=" statement, scroll down to the section labeled
[Multisnd.drv]. Check the statement "RamAddr=". If it has the same
address as the EMMExclude, you can erase the EMMExclude safely and
continue with re-installing your Multisound.


Question 3: When I run my install and reboot the computer to start the
Multisound, my computer locks up. What should I do.
Answer: In this situation, the most likely problem is that you have a port
address conflict. Our default Port address is 290. If your
computer is locking up, shut it down, open it and switch all four of
the dip switches on the little red box to the OFF position. If you
can enter Windows at this point, enter your Main window and double
click on the Control Panel. Within the Control Panel, double click on
the Drivers icon, highlight "Turtle Beach Multisound Wave form, MIDI,
and Aux, then press setup. In the setup's Port section choose address
3E0. At this time you will be prompted to restart Windows. After
re-entering Windows, enter the Multisound Window and double click on
Diags. This will run Multisound Diagnostics.

If you CAN'T enter windows after switching the dip switches, enter
your DOS editor. Edit your c:\windows\system.ini file, and erase the
[Multisnd.drv] section. Also erase references to the Multisnd.drv in
the [drivers] section. Scroll to the [386Enh] section and erase the
line EMMExclude=D000-D7FF. (Note: If you have changed the Memory
address of the Multisound during your first installation, this
statement will reflect the new Memory address and not the default
address of D000.) You should consult your computer's manual and the
manuals for any other cards or devices you are using with your
computer and make a list of their port, RAM, and IRQ addresses. With
this list in hand, you should be able to enter Windows and upon
installation of the Multisound's drivers and applications, change the
Multisound's addresses appropriately.


Question 4: When I run diagnostics everything fails!? What's going on!
Answer: You most likely have a port conflict. Refer to the Answer to
question 3.


Question 5: After I install the Multisound and open any MIDI device I get the
message, "Multisound MIDI driver not installed." Why is this?
Answer: In this case, there are a few possibilities. We want to edit your
System.ini. If you are unfamiliar with Windows SysEdit application
you will want to exit Windows, get to your C prompt and type the line

Edit c:\windows\system.ini

Once you are in your System.ini, scroll to the section labeled [MCI].
Here you want to make sure that you have the line "Sequencer=MCISeq".
If this statement is not there, you will want to load your MCI MIDI
sequencer driver from the Windows Control Panel/Drivers application.
If that driver is preset, scroll down to [drivers]. In this section
you should see the statement "MIDI=Multisnd.drv". If this statement
is not present, refer to question 7. If both of the above statements
are present and the Multisound is still not responding to MIDI, you
probably have a memory share error or a memory conflict. Refer
to the answer to question 7.


Question 6: Once I install the Multisound and I enter the Multisound drivers
setup, the "MIDI Demo" button is grayed out. What does this mean?
Answer: Refer to the answer to question 7.


Question 7: When I run Multisound's diagnostics I get a memory conflict or
a memory share error.
Answer: You need to either choose a new memory address or, in the case of a
memory share error, properly exclude the memory address you have
chosen. The Multisound's default address is D000. If this is not
good for you and you have no idea what other memory space you have or
even what memory addresses are, I can suggest a few that usually work
well. The three address' are E000, E800 and (If you don't have a
super, duper, mondo Video Board) B000. Note that these are ZEROS not
O's.

To Change your memory address:
1-Enter your Main Window
2-Open your Control Panel
3-Open the Drivers Icon
4-Select the Multisound Wave form, Midi, and Aux
5-Change the Memory address
6-Restart Windows

If you receive the message, "EMMExclude not as expected" edit your
System.ini [386enh] section. Simply put a ; (semicolon) in front of
the "EMMExclude=" statement, save this change, and repeat steps 1
through 6. The last aspect of the memory error is the Share error.
In order to avoid this error, your config.sys must be set up
correctly. If you are using a high memory manager like Quemm or
Emm386, you must put an exclude statement in your Config.sys file. It
would look something like this.

Device=C:\Windows\Emm386.exe NOEMS x=D000-D7FF

The excludes for the Multisound are as follows:
B000-B7FF
C800-C7Ff
D000-D7FF
D800-DFFF
E000-E7FF
E800-EFFF

Make sure that the first number in the exclude matches the
Multisound's memory address. Consult your Memory manager's manual for
the proper exclude statement for your memory manager. After making
this change the computer needs to be rebooted for it to take effect.


Question 8: When I run Multisound's diagnostics, I get an IRQ error.
Answer: Enter the Control Panel, double click on the drivers icon, select
Multisound Wave form, MIDI, and aux. Click on setup. In the window
labeled Interrupt, select another choice rather than the default of
10. We've found that in many machines IRQ 11 or IRQ 15 are good
choices.



SECTION 2: COMMONLY ASKED QUESTIONS ABOUT THE Multisound

Question 1: Does the Multisound work in the DOS environment?
Answer: No it does not. The Multisound was designed specifically for use
in the Windows 3.1 Multimedia P C environment. If you do desire
to use a Sound Blaster or Media Vision card with your DOS
applications, simply install it and do not install the Windows
drivers for that card. With this configuration you will be able to
play games in DOS and still have the best MPC card available for your
more serious Windows applications.



Question 2: Is the Multisound Adlib or Sound Blaster compatible?
Answer: No it is not. Again, the Multisound was designed specifically for
use with the Windows 3.1 Multimedia environment. The design of the
Multisound's hardware is very different from a Sound Blaster or Adlib
type card. These differences are precisely what let the Multisound
provide you with superior MIDI and hard disk recording capabilities.
As time moves on, more and more software developers will be using
the MPC spec. for their games and other software. These new programs
will allow you to further utilize the Multisound superior sound.


Question 3: When using the Multisound's multiple MIDI port capability with
my sequencing software, I hear the Proteus when I am recording while
sending data to my external MIDI port. Why is this?
Answer: This is a hardware limitation within the Multisound's design.
Your sequences will play back correctly, yet during recording, all
incoming data is routed through the Proteus first, then to the
sequencing software. There are several simple work arounds when this
occurs. One is to simply turn down the MIDI fader in the Multisound
Mixer applet when recording to external devices. Another is to record
all tracks routed to external MIDI gear first. The last is to create
all of your sequence using the Proteus, then routing the tracks to
your external MIDI gear.


Question 4: Sometimes, when I'm using a MIDI application, I get the message
MIDI device in use.
Answer: Check to see if you are using the Multisound 1.0 drivers. You can
check this by opening any of the Multisound applications and clicking
on the "About" box. If you are using the 1.0 drivers, you must be
sure to only have only one MIDI device open at a time. The usual
mistake is to open the Media player to play a MIDI file while the
Multisound Front Panel is open. If you do not have the 1.1 drivers,
you should either download the file MSND11.zip from our BBS or call
our Tech. Support line and request that we send you the new drivers.


Question 5: Why am I getting stuck MIDI notes?
Answer: There are many possibilities here. The first is that you have a MIDI
loop in the Multisound's MIDI patch bay. This application can be
found in the Multisound group. Many Windows sequencing applications
have the ability to access the Multisound's MIDI ports directly from
their MIDI setup. If this is the case, we suggest you avoid the patch
bay and use your software to set up your MIDI paths. In some cases,
the software will only refer to the "Windows MIDI driver" or something
of that nature. In this case, your Multisound MIDI patch bay should
be configured as in the diagram below. "X"=Selected. " "=Not checked.


|--------------------------------------------------------------|
||External Connector| |
|| | |
||-IN---------------| |
||| Proteus/1 In || |
||| X Windows In || |--Windows---------| |
||| X External Thru|| | | |----Proteus/1-----||
||------------------| |-IN---------------| | ||
||-Out--------------| || Proteus/1 Out|| |-In---------------||
||| Proteus/1 Out|| || X External In || || X Windows Out |||
||| X Windows Out || |------------------| || External In| |||
||------------------| |-Out--------------| |------------------||
||-Thru-------------| || X Proteus/1 In || |-Out--------------||
||| Windows Out || || X External Out || || Window In |||
||| X External In || || External Thru|| || External Out |||
||------------------| |------------------| |------------------||
||------------------| |------------------| |------------------||
|--------------------------------------------------------------|


If you still get stuck notes check these things. If you are running
through and external MIDI patch bay, make sure there are no MIDI
loops in your configuration. The easiest way to determine if this
is the culprit is to disconnect your external controlling device from
the patch bay and connect it directly to the Multisound. If the
stuck notes go away, you know that you have a loop set up in your
external patch bay.
If you are running the Multisound out or Thru to your external
controller, make sure that you are not echoing your incoming MIDI
data to the MIDI out of the controller. This will create a MIDI loop.
If your software DOES recognize multiple MIDI ports, make sure you only
have EXTERNAL IN selected as your record source.


Question 6: How can I access Proteus sounds above 128 when my sequencing
software only shows 128 presets.
Answer: MIDI specifications only allow any MPC sequencer access to 128
presets at a time. The only way to access the sounds above 128
is to remap them into the lower 128. Put simply, this means that
you will be substituting sounds from the upper presets for the
sounds in the lower presets. If you have the 1.1 Proteus drivers,
you will be able to program the Proteus using the Proteus front
panel and save these changes as user presets. The Proteus front
panel is found in the Multisound group as the Proteus icon. After
you open this application, perform the following steps.

1. Press the Master Button.
2. Press the right Data arrow until MIDI Prog->Preset with 000->000
appears in the Proteus' window.
3. Press the button that says cursor. This will position you under
the left set of zeros.

Question 7: How can I save my modified Proteus Presets?
Answer: Once you have edited all of the Proteus Presets that you want to
change, press "Presets" on the Proteus Front Panel. You will get
a dialogue titled "Proteus Preset File Load & Save". At this point
you would want to press the button labeled "Save User". This will
save your user presets. If you would like to use these presets as
your default sounds, simply press "Save" and this will save your
presets as your boot up presets for the Proteus.

Question 8: I can hear my record source (CD-ROM, tape deck, external CD
player, etc.) but it does not record. What's up?
Answer: Check your input. If you have an internal CD ROM and you want to
record with the Multisound, you should be connected to JP2 internally
(this is the four pin jumper between the IN and the AUX jack) or
externally to the IN input. The Multisound is designed to record
only from the IN and uses the AUX as an audio Thru jack. This
configuration has many uses when using the Multisound in complex
multimedia applications.

Question 9: Why cant' I hear my record source through the Multisound?
Answer: Check your mixer application and make sure your MASTER and your IN
are not muted and are turned up sufficiently.

Question 10: Why can't I get a good level with my microphone plugged into the
Multisound's IN input?
Answer: The Multisound is designed to work with a line level input. A mic
has an output significantly below this level. What you may do is run
your mic through a mixer with line level outputs, through a microphone
pre-amp, or even through a tape deck with microphone inputs and a
line level output.

Question 11: Why can't I audition my Proteus sounds with my external keyboard?
Answer: First off, make sure you are using the MIDI connector from Turtle
Beach designed specifically for the Multisound. Any other MIDI
connector may work incorrectly. Second, check that your Multisound
MIDI patch bay looks like the example below. X=selected.

|--------------------------------------------------------------|
||External Connector| |
|| | |
||-IN---------------| |
||| X Proteus/1 In || |
||| Windows In || |--Windows---------| |
||| External Thru|| | | |----Proteus/1-----||
||------------------| |-IN---------------| | ||
||-Out--------------| || Proteus/1 Out|| |-In---------------||
||| Proteus/1 Out|| || X External In || || Windows Out |||
||| X Windows Out || |------------------| || X External In| |||
||------------------| |-Out--------------| |------------------||
||-Thru-------------| || Proteus/1 In || |-Out--------------||
||| Windows Out || || X External Out || || Window In |||
||| X External In || || External Thru|| || External Out |||
||------------------| |------------------| |------------------||
||------------------| |------------------| |------------------||
|--------------------------------------------------------------|

Question 12: Why can't I hear any MIDI through my sequencer?
Answer: There are many possible answers to this question. First of all, make
sure that your sequencer is an MPC compliant Windows 3.1 application.
(If your MIDI setup only allows you to choose an MPU-401, your program
is not an MPC program.) Also check the Multisound Mixer to make sure
that your MIDI volume is not muted and is turned up. If your
sequencer has a Thru option, enable it. This will allow you to hear
notes triggered by your controller even when you are not recording
or playing. There are two basic styles of Windows MPC sequencers.

MULTI PORT SEQUENCERS AND THE Multisound
Many MPC compliant sequencers are now supporting a multiple MIDI port
format. This allows you to use the Multisound's MIDI out and Thru
as separate MIDI out ports for your external MIDI devices. You should
configure your software as follows.

1-Enter the MIDI setup of your sequencer.
2-Choose "Multisound External In" as your "MIDI IN" or "Record Port".
3-Choose Midimapper (for general MIDI) or Proteus as your A port.
Choose Multisound Out and/or Multisound Thru as your out ports to
your external gear.

SINGLE PORT MPC SEQUENCERS AND Multisound
Some Windows sequencers only access one port in and one port out. In
the MIDI Setup for these programs you should choose "Multimedia
drivers for Windows 3.1" also choose "Extended Level Setup (Channels
1 through 10)" as your synth setup. There are a few quirks with this
kind of sequencer and the Multisound 1.1 drivers.

1-Because you have only one selection for your MIDI port, you must use
the Multisound's MIDI patch bay (found in the Multisound group) to
configure your Midi In and Midi out. Configure the patch bay as in
the figure in Question 5.
2-If you cannot record with your external keyboard or play MIDI files,
even when your configured correctly, here is what you do.
-minimize your sequencer
-enter the MIDI patch bay and click on "External IN" in the
Windows in section.
-You will get a dialogue saying, "Requested settings may conflict
with current application setting. Do you wish to activate the
new settings?"
-Choose "Yes".
-Enter your sequencer again and you will be able to function
normally.
The reason this is a problem is due to the fact that the Multisound
has multiple MIDI ports. One of these ports will have priority
when your software boots up. Due to a Windows convention, we
cannot assure that the Patch bay will be the Priority port. By
following the steps above, you will be initializing the Multisound
Patch bay as the Primary MIDI port for you Sequencer during this
session.

At Turtle Beach, we're committed to giving you the best customer support.
If your questions have not been addressed in this document, feel free to call
Turtle Beach Tech. Support at 717-843-6916 From 9 AM to 6 PM (EST) Monday
through Friday. If you would like to leave a message on Our BBS (also great
for getting the latest updates, information on new products, etc.). We thank
you for choosing Turtle Beach! Take care.