Search:

Same here. b23. What kind of information do you need to help fixing it ?

I am aware of this. I just wanted to point out that this is the same entity as a normal channel with max_users set to "0". So it's a redundant thing to implement.




OK, just to elaborate:
a)...

I asked myself the same question. It's basically a normal channel with max_clients set to 0.
So now I'm asking myself why I can join a spacer even as an admin. Joining, setting codec, topic etc...

I first mentioned the codec-issue in this forum more than 4 months ago. You do the math.

Working fine here since beta1 on Windows 7 x64.

They actually got implemented a few minutes ago.

"They" aren't even developing those codecs. They are just "using" an externally developed solution (speex) so all they have to do is (re-)implement it.

They're coming in TS4 :)

Yes, maybe there even will be some high-latency codecs in Teamspeak 4 ;)

I would disable ingame voip support to test if this is conflicting with teamspeak.

Yes, it's a pitty. All bugs that have been fixed so far just adress glitches in the code but don't REALLY improve user experience. Codecs, on the other hand, are essential for many people in order to...

Do you have a small bandwith internet connection ? There is a known problem with these connections, but the devs don't want to implement the TS2 codecs (which don't cause problems in these cases)......

I did this by directly entering my multiline welcome message into the sqlite database.

Where did you get beta9 ? I only find beta8.

I already requested this here. You are not alone :)

+1
(10 chars min)

You can run almost every 32-bit application in 64-bit Windows, including Teamspeak 2.

The high latency codecs actually are old stuff :p

You sound like a nazi. Even more than me, though I'm german.

An Admin has to add you to a group with rights you need. There is no user / password system in TS3 so registering isn't necessary to log in to the server.

I would like to see the two options "Echo reduction" and "Advanced Options" and as a result "Remove background noise" and "Automatic voice gain control" to be default settings in the "Capture" Menu...

If you got Windows 7 just open the Control Panel and enter "Speech" into the search box ;)

The TTS volume is a Windows-Setting, not a TeamSpeak setting. You can cofigure it via Windows Control Panel.

Try the beta2 client / beta3 server. I had a similar issue on beta1.

Reason for this is that ZoneAlarm sucks. Get rid of it if you can (In terms of "being able to remove it from your system at all").

Still no difference in the beta3 server.

As Peter announced in this post there will be codecs which use less Packets per Second than the current ones. Can you provide us with an estimate please ?

I got the same issue.

Thank you for helping me understand the functionality.

What's the purpose of the "App Scanner" Option ? I can't seem to do anything except open an .ini file in the App Scanner menu.

In Teamspeak 2 I could create a channel, assign a password to this channel and a user had to enter this password if he joined either this channel or one of its subchannels. Furthermore, once entered...

I haven't tested it with different soundpacks since the possibility of this being the reason for the faulty behaviour didn't occur to me.
I am however using the "Default Speech" pack since I want to...

I am using a headset which is registered as separate Soundcard for audio recording and playback in TeamSpeak 3 but the Sound notifications still are played back by my systems default audio device...

I got the same problem.

Workaround for me was to simply edit the sqlite db manually.