Sexbomb
27-08-2002, 17:35
I really like TS 2.0, but I've found a problem that I haven't seen in any other post.
The first & last bits of a word/sentence, especially when I'm using PTT, are simply cut out, let's say it's something like 1/2 second.
It ain't big deal, but it's a little annoying. For example, if I try to count 1>5 with short strokes for each number, it is virtually impossible to make up more than 2 or 3 words. Also, when I press the key to speak again the last bit of the last word that was cut out before is played now before the new one (seems like buffering is messed up?).
I've tried different codecs, wave<>directsound, latency slider, no difference at all. I haven't tried changing between normal priority and real time (silly me :D ) but that shouldn't make any difference, more so because it was the only app running.
BTW, I was using Teamsound until now, and even if I hated it for many reasons (mostly for high latency/terrible stability), I didn't have this problem with teamsound.
Is this a bug in Teamspeak 2.0, or does this only happen to me?
The first & last bits of a word/sentence, especially when I'm using PTT, are simply cut out, let's say it's something like 1/2 second.
It ain't big deal, but it's a little annoying. For example, if I try to count 1>5 with short strokes for each number, it is virtually impossible to make up more than 2 or 3 words. Also, when I press the key to speak again the last bit of the last word that was cut out before is played now before the new one (seems like buffering is messed up?).
I've tried different codecs, wave<>directsound, latency slider, no difference at all. I haven't tried changing between normal priority and real time (silly me :D ) but that shouldn't make any difference, more so because it was the only app running.
BTW, I was using Teamsound until now, and even if I hated it for many reasons (mostly for high latency/terrible stability), I didn't have this problem with teamsound.
Is this a bug in Teamspeak 2.0, or does this only happen to me?