Developer Blog
New Development Updates
by Bastian Schaar on Apr 13, 2007
Hello everyone!

First off we are sorry this developer blog entry took so long. Although we are making excellent progress, we have been extremely wrapped up with TeamSpeak 3 coding all this year, and more recently we have also been occupied with moving our office to a new location in Bavaria... but now we are settled into our new office and have time to write up this entry.

The main programming goal we had set for ourselves and accomplished since our last blog entry was to completely rewrite the protocol structure deep down in the TeamSpeak 3 core. The change in the protocol now allows us to handle many things far more effectively within the code, reduces overall bandwidth usage, and should also cut down the required CPU cycles to parse packets.

In addition, regular blog readers may remember that a while ago we stated that we still had an outstanding TODO task which negatively affected the latency of voice playback. We've put some effort into this area and the latency has been lowered even more, while not only maintaining playback quality but actually improving it slightly. We are also currently in the process of putting a tool together which allows us to measure the latency of just about any VoIP solution out there, so we might soon be able to provide you with numbers showcasing the differences between TeamSpeak 2 and TeamSpeak 3 with regard to the time it takes from saying "two foes at the castle" and your mate actually hearing what you said. That being said, even without this tool it is already very obvious that TeamSpeak 3 is much faster than it's predecessor!

One other thing we've recently allocated time for is implementing per server capture and playback devices. So you can now do some really cool things like hook up two USB headsets to your computer, fire up TeamSpeak 3 and join two different servers (remember the tabbed voicecom feature we hinted at from one of our previous blogs?), hand one headset to your mate and be able to talk as if you were running two entirely separate clients. Hence, your mate will only hear what people on "his" server are saying, and will only be able to speak to those users and vice versa. The flexibility this feature provides should make for some really cool setups that were either impossible or cumbersome to realize with TeamSpeak 2.

As the last feature we want to showcase within this blog entry, we have now created TeamSpeak 3 sound packs! The idea here is to allow all the sounds that are played when some action occurs (e.g. in TeamSpeak 2 when you mute your microphone you hear "Microphone Muted") to be packaged in a sound packs, and distributed easily. So when TeamSpeak 3 is released and some of you feel creative, you can whip up your very own sound pack that anyone can download to their TeamSpeak 3 sounds folder and voila, it will appear in the options dialogue as a new sound pack.

That's it for now, please stay tuned to our website for more updates!
« Read all Developer Blogs