Team Speak?

[VixDraken]

What are the chances we may be using head sets to communicated with each other with the program called team speak?

it would eliminate the time it takes to type messages.

[Vigow Milla]

Hey Vix,

It's true that great minds do think alike. I brought this up a couple of days ago in the military forum. I do think that it would come in very handy in regards to the military aspect of the game.

[Shadow]

yup it would make communicating much easyier and like i said in vigow's post i think its a good idea

just my 2 cents

[Mochareshk]

It all comes down to cost and bandwidth however, how feasable is it in this regard?

[Janel Kast]

I've never used any kind of speaking programs for my computer. Is a headset the only thing I need to buy?

Sorry I dont have that much computer knowledge.

-Janel-

[Vigow Milla]

Actually Janel if your pc has a built in mic, or if a mic came with it, that's all you need.

[Droider]

Mochareshk, I'm not sure whether you mean bandwidth on the server or client, so I'll cover both.

Client: i.e. locally, your computer. If you have a modem then it might take up a little extra bandwidth on it, but teamspeak was designed for gaming, with low bandwidth in mind. It seems to trade higher latency for lower bandwidth when necessary, so it might take a few seconds after you say something for us to hear it. The lowest bandwidth (and lowest quality) codec is a Speex codec which limits itself to 3.4 Kb/s, or about 10% of your total bandwidth on a 56Kb/s modem (most do well to acheive a 33.6Kb/s connection). However, this is where we kind of have to make a judgement call. Whatever codec is set for the channel is the one that the whole channel uses, and that 3.4 Kb/s codec is rather low quality. So we may choose to use a better codec for quality purposes if most or all have a broadband connection that are using it.

Server: I have the teamspeak server running on a shared hosting server in North Carolina. It has multiple OC12 connections to several Internet backbones, so bandwidth there is no problem at all. Latency may be a tad bit high if most of the PA is living on the west coast, but it should only show up as a fraction of a second delay between when you speak and when others hear you. The codec is going to cause more of a delay than that. Ping csworkbench.com to check latency from your area if you're interested.

Cost: It's free, as long as I don't charge you to use my server, I don't have to pay for the server. Sounds like a great deal to me

Janel: A built-in mic will work, but headsets are generally higher quality (easier for the rest of us to understand what you're saying). I plan to buy a headset if/when we actually start using teamspeak, even though I have an open air mic already.

[saiber]

i have a question how do u tell if u have a built in mic in ur comp?
;D sorry stupid question but plz respond

[Droider]

The easiest way is to see if anything is plugged into your mic out port on your sound card, usually colored yellow. If there is, follow it to the other end. It may lead to your monitor cable, which would mean there are a few holes in your monitor that have a mic behind them.

[Agoln]

MULTIPLE OC12 CONNECTIONS!!!! !!! that would MORE than cover the bandwith for a 3.6 kb/s bandwith, or even if we wanted 36mb/s!!!

[Droider]

Well, multiple OC12 connections to the data center, which undoubtedly has a large number of servers running off that connection (I'm not even going to guess how many). But hey, I routinely download from that server at ~350 KBps, and I think that's what my cable modem is capped at, so I'm more than sure that it will handle whatever load teamspeak can think of putting on it.

David