client update 2.0.20.20

[N. Werensteijn]

Ok I introduced a BIG sound bug in 19 :) Sorry about that.

So here is 20.
Its got a new sound update model for direct sound. This should mean TS works ok for CS now, and should also work with the sb audigy. (With the old drivers that make it choppy). Can somone test this please?

Also, I fixed 2 bugs that possibly could hang the ts client on disconnect and close.


Get it here: http://www.teamspeak.org/files/TeamSpeak_patch20.zip
Instructions are the same as always, just unzip over the previous exe :)

[FloorPie]

Niels, do you object if I put the patches and rc1 (2.0.17.17) on my clan's public download page? Over the past week, I've had most of the clan test out a whole bunch of things. It's a little easier for them to download the zip from the page they visit almost every day.

Today, in asking them to upgrade, I realize I should ask you if it's ok for me to put the .zip files on the download page like I do.

I will (and did with the last patch) give you feedback if the new patch fixes any existing problems, or creates new ones. :)

[N. Werensteijn]

Sure go ahead.
Just make clear its not the RC1 version.

[Code]

Ok, I've installed the new patch and created every situation I can think of that made mine choppy. It seems to be working great but I will keep monitoring it and will post any problems I have.
I am running XP, SB Audigy gamer, 256 Mem AMD 1.3 Radeon 8500 128Mb

[QUINT]

http://forum.teamspeak.org/showthread.php?threadid=1475

Do you think this PATCH will fix my STATIC problem???

~QUINT~

[FloorPie]

QUINT, try it and tell us if it fixes it.
You mentioned the size of your hard drive, type and speed of memory, speed but not OS. Are you on WinXP with your SBLive?
Edit: Added the name QUINT to the start ;)

[Code]

Yes WinXP Pro, right after the word running in my other post I just put XP.

No worries...lol

[FloorPie]

That's great, but my answer was to QUINT ;)

[Prophecy]

Hey I ll be the first to admit, that I bitched and moaned about RC1. But with this patch and some tweaking everyone seems to be working fine. The choppyness was an issue but not anymore. I had an issue with black hawk down and ts 2.0 but i switch from wave to direct sound and it seems to fix it. I am running xp btw.

However all is working well.

Everyone is clear.

Good job.


Prophecy

[Code]

I've ran every situation that produced the choppiness and I did not have any problems. Looks like the patch is a winner!

[airborg]

ran this update but getting the following error:

14-09-02 20:27,WARNING,All,TMainForm.FormCreate,Exception EProtocol: Error loading Hawlvoice library (hvdi.dll) Maybe not installed?

SB Audigy Platinum installed and updated.

Any clues?

[FloorPie]

ran this update but getting the following error:
You need to extract the .exe to the teamspeak folder that your current TeamSpeak.exe is located, overwriting it.
(The same folder 'hvdi.dll' is in :))

You might want to copy/back-up your existing TeamSpeak.exe before you overwrite it though.

[Lorphos]

Niels, the connect window is still too high ... please squeeze it a bit.

[kfsone]

If I switch to High priority mode, I can't enable the gamevoice hardware option. Is this intentional?

[N. Werensteijn]

nope..

And here is also works.. Are you sure?

How about enabling gv first, then priority high?

[FloorPie]

Hmm, priority makes no difference.

1) Check the option to enable gv, click apply.
  (If already checked, skip to step #2)
2) Uncheck the option to enable gv, click apply.

3) Now try #1 again. When you click apply, the option unchecks itself.

Or:
Enable gv, click apply/ok, close teamspeak.
Re-open teamspeak, go back to the option for gv... it's unchecked, and if you check it and click apply, it unchecks itself.

[Doritos&Vodka]

One thing I've found is if I turn on GV before connecting. It saves. If I open the Option while connected, the setting unchecks itself when saved..

[FloorPie]

One thing I've found is if I turn on GV before connecting. It saves. If I open the Option while connected, the setting unchecks itself when saved..
I think it's more of a 'works first time you toggle it', then the rest it doesn't. Being connected or not doesn't change anything (in other words, you can connect and THEN set it), but the NEXT time you try to enable it, doesn't work (unless you close and re-open teamspeak.)

[N. Werensteijn]

Do you have a gamevoice puck?

[kfsone]

Actually, it doesn't seem to be purely the High process priority that does it, but for me this is reproducable:

a. Configure TeamSpeak 2 to "Normal" mode.
b. Launch TeamSpeak 2
c. Enable GameVoice hardware support
d. Click Apply, OK
e. Click (./) High
f. Click Apply
- Enable GameVoice hardware support becomes unchecked
g. Click Enable GameVoice hardware support
h. Click Apply
- Enable GameVoice hardware support becomes unchecked again

I can check the EGVhws button and it stays checked. If I change any other radio or checkbox buttons on the same tab, EGVhws will become unchecked when I click apply or after I click OK.



Regards,


Oliver

[Broder]

Just some feedback...

had 2 Users having probs with stutter during and lag especially during onlinegaming with Mohaa and when the maps changed.

With .20 these problems vanished...

Thanks for that one ! Saved me some time troubleshooting :D

Broder

[FloorPie]

Do you have a gamevoice puck?
No, lol. But if I plugged one in, is gamevoice going to re-check the option to enabled?

[N. Werensteijn]

If you have a gv puck, this will work correctly.

If a gavevoice puck is not found, this is the behaviour you get

[SirEd]

several options are possible:

1:in BF1942 (demo) i checked sound quality options in game settings to full , i had a weird sound like a snowsled was moving in front and back...

2:the mic-boost of windows in sound/audio options is giving also probs so unmark 'V' it ...

3: when u have onboard sound be sure it isnt working disable it ..
u can get that weird flushing/static sound from it...

4:gv enable is workin here also

these were troubles our team came up with and some solutions .....

[kfsone]

It could be the lack of hardware detection or something. But basically things don't quite "stick" properly when clicking apply - as though something is clobbering the gamevoice option setting.

We're also experiencing some kind of creeping volume problem with 20.20 where you gradually start clipping and distorting as though you are shouting your lungs out into the microphone.

I've been trying to get you something more useful than that but we've not managed to intentionally replicate it as yet. It has the feel of some sort of leak or accidental increment.

[[LOL]Fullback]

With the latest patch me and a couple of friends have a problem with low volume. It is really low U can hardly hear what the person with the patch installed is saying. We have checked and increast the microphone volume on the Windows control panel volume applet to the max but that doesen´t do it.
When we changed back to the original version of TS2 then the volume was OK again but then the stuttering and choppines is back.

Any ideas ??

[Micro®]

Originally posted by kfsone
It could be the lack of hardware detection or something. But basically things don't quite "stick" properly when clicking apply - as though something is clobbering the gamevoice option setting.

We're also experiencing some kind of creeping volume problem with 20.20 where you gradually start clipping and distorting as though you are shouting your lungs out into the microphone.

I've been trying to get you something more useful than that but we've not managed to intentionally replicate it as yet. It has the feel of some sort of leak or accidental increment.



Try Going Into The Teamspeak 2 -> Settings -> Sound Input/Output Settings.

[kfsone]

Originally posted by Micro®


Try Going Into The Teamspeak 2 -> Settings -> Sound Input/Output Settings.

... and doing what? =)

--------------------------

Four of us using 20.20, using GSM 14.8, find that over a period of time we will gradually start to sound like we are yelling/shouting into a microphone that has slipped into our throats.

You can sometimes fix the problem by switching between Wave and DirectSound a few times. But normally you have to restart teamspeak, and immediately upon restart, the sound quality is normal. After about 15 minutes you are back to sounding clipped/crackly and distorted.

[N. Werensteijn]

the 2.0.20.20 patch was build (by accident) with an experimental new voice normaliser, which still has some flaws, as you have noticed

[[HJ]-Petz]

Niels Werensteijn, thanx for releasing these updates to the public. I know they are beta's and that there may be a problems with them such as this volume problem im reading about in here.

But for me this patch is a god send.

RC1 was unusable for me(Sound blaster live and windows XP pro). atm Im running this patch with a developer server patched host and everything is running ok. As long as I switch the sound driver to WAVE(direct sound is working better but still blasts other users with static sometimes).

So many thanx Niels and all the developer team for not making me wait until RC2. Which im sure will be daStuff after using these patchs.

[kfsone]

Thanks :) I was going to check back and see if there was any additional info I could produce for you (whether server version we are running against mattered, for instance).

In the spirit of the above poster, I just want to say...

Several years ago I came across a very basic little program for voice comms, called "BattleCom". I'm a systems software developer myself, but the first version of BC I saw looked like something I might write. I was playing WarBirds at the time and I knew voice comms was what we needed.

Keen to see it develop in a useful direction, I started throwing some serious ideas (occasionally specs, sample code or even mini-executables =) for changes and feature adds - for instance the channel and whisper system. I even remember early emails with Rod Toll kicking around some of the ideas we later saw manifested as the GameVoice puck ("an external keypad you can keep near your joystick to do push to talk and channel swapping") and GameVoice software ("keyword triggered voice activation, nothing complex like some of the old amiga voice-rec programs").

BattleCom - and GameVoice/DirectVoiceAPI - have a networking issue whereby they never recover from backing off after packet loss or large delivery-time spikes. Other than that, we nearly had the voice comms software we wanted.

Since the demise of BattleCom, I haven't even bothered looking at other voice software, nothing could live up to my expectations.

Recently as an active WW2 Online player, I was desperate to get my squad to use ANYTHING other than Roger Wilco. Even wrote my own small voice app using DirectVoiceAPI - but that suffered from the net-stutter, of course.

So I grabbed a few. Having looked thru them, I was about to give up. Instead of deleting TeamSpeak's installer, I accidentally installed it. So I thought, hell, one more, and fired it up.

I am very, very fussy (and critical) about my software; both as a user and as a peer-developer.

TeamSpeak 2 bowled me over. It's very rare I find a piece of software I use for more than 15 minutes a day and don't have a dozen suggestions for. The GameVoice-hardware compatability is awesome.

You've done things with TeamSpeak I'd never have bothered suggesting to other developers, because I'd never have imagined they'd pull them off. The multiple codecs per server; the instant "live" effect of settings changes so you don't have to restart the app.

Even these "developers releases" have proven incredibly stable for me.

You guys have pulled off a rare achievement in software development. Hats off to you as both a user and a professional developer.

[N. Werensteijn]

Thanks! :)

All the features in TeamSpeak1 come from our own requirements when gaming. A lot of the other feature enhancements in TS2 come from people on this forum, requesting it.

So you see,
your say here, does make a difference :)