Troubleshooting your TeamSpeak Voice/Speakers Connections
First, check your headset, the little toggle switch should be set to on, that the one on bottom when looking at the word "Logitech" face on.
Next go log onto TS and go to settings, sound input/output settings.
In sound settings, use the settings in the picture to the left.
Sound Input/Output Settings
The output level (how loud you hear others talk) of the TeamSpeak client can be set with the Output Volume slider.
Sliding it to the right will make all sounds louder, to the left less loud.
In Teamspeak 2 there are 2 ways to communicate with your friends. The first choice is called push to talk. This means
that you have to press and hold a specified button if you want to talk to others. The other way is by voice activation.
This means that Teamspeak will automatically transmit to your friends when the program "hears" you talk. You
can choose between the 2 voice send methods. If you choose push to talk, select it and press the Set button to bind a
key.The key you have chosen will now appear onscreen. Whenever you want to transmit you have to press this button. If
you want to use a different button press clear and do it again.
Below that option is a bar with the Voice activation level which you have to configure for optimal sound. If you slide
the bar to the far left Teamspeak will transmit as soon as you make the slightest sound, even if you whisper, chances
are you will be transmitting to your friends all the time while you don’t even know it. If you slide the bar to the far
right you have to shout before Teamspeak will actually transmit.
You can do a local test to check your settings and codecs. Choose a codec from the menu and press Activate local test
mode. When transmitting the green light next to it will light up. The client will echo your spoken text. This function
is a good way to check your Voice Activation setting. You can finetune the setting in local loopback mode. If you find
that the Voice activation level is too sensitive in Windows (the difference between sending all the time and not
sending at all is just one stripe on the bar) set your Mic input level higher in your Windows mixer. When you are done
click the Close button to close the window.
You may want to check out and play around with the options menu also.
Tab Sound Devices
TeamSpeak automatically detects what recording devices your computer has. They are listed in the Settings --> Options
-->Sound Devices under Device. Here you can choose your preferred device. Try by trial and error what works best for
you (e.g. I found out that my headset and soundcard recording worked better than my usb webcam recording) Note that if
there are only 2 options there (one being the "primary driver...") it doesn't matter which one you choose.
In this dialogue-box you can also see what kind of recording you are using. There are two kinds of recording: Wave and
Direct Sound. The first one generally delivers the best sound quality and the latter the lowest latency (depening on the
quality of your soundcard). The default is set to Direct Sound. When switching between those two it is sometimes needed
to restart TeamSpeak (when you get an error message) in order to get it working properly.
DirectSound has a slider which controls the sampling buffer size. When it is to the utter left one has the lowest
latency (one can hear eachother with the least amount of timelag). When the slider is to the utter right you will have
the same quality and timelag as Wave recording. When people on your server complain you are just sending "noise"
but you can hear them fine, you are probably using DirectSound. Try sliding the slider to the middle or right position.
Most of the times this seems to solve this problem (this problem occurs because not all soundcards are capable of sampling
really short bits of sound, with the slider in the middle or right those samples are a bit bigger and hence solve the
problem). Note: Windows XP users are generally better off using wave recording. W98 users should use DirectSound. If you
have a onboard soundchip (a soundcard integrated on your motherboard) and people can't hear you on the server but you
can hear them just fine, it is probably because your soundcard isn't capable of recording in 16 bit (although your
manufacturer might claim it can). Of course we have a solution for you and you can try and check the box at compatibility
called "Force 8 bit recording".
First check that the recording mic setting in your sound software in windows is not muted before you try this test.
Start/Stop Recording
With this function you can record your current session in TeamSpeak. When you want to start your recording a window pops
up where you can choose a location and filename for your recording. When you click OK the recording will start and anything
said in the channel will be recorded. To see wether you are recording or not, have a look at the lower right section of the
client. If you are recording it will show over there. Behind your name there will be a "Rec" flag. When you are
done recording you can select Stop Recording in the menu.
Notes
The recording is done in wave format, PCM 22 khz mono in 16 bits. This practically means that recording uses 44 KiloBytes
per second or about 2.7 MegaByte per minute.The reason we haven’t included a compression method are twofold, legal and
technical. Legally we cannot implement mp3 encoding and technically encoding uses a lot of CPU power which could result in
serious slowdowns in applications running next to TeamSpeak. In future releases we might include a ogg vorbis encoding
solution and serverside recording. Please do not send us mails requesting these features. They will come or they won’t.
You can listen to test file by opening it in media player.
Check your Windows software sound device settings to make sure none of the mic settings are muted or the volume is off.
