RC1 Client Mac CPU Usage

[Johanna]

Since the last update to Build 14345 TeamSpeak takes ~30-40% of my CPU.

I have a MacBook Pro with:
Mac OS X 10.6.7
2.8 GHz Intel Core 2 Duo
4 GB 1067 MHz DDR3 Ram

[dante696]

Can you try to deactivate echo filtering?
Open Settings > Options > Capture > Now uncheck both Echo options

What device you use for talking USB/Onboard??
I send it to a developer for next morning.

[Johanna]

Can you try to deactivate echo filtering?
Open Settings > Options > Capture > Now uncheck both Echo options

One option was unchecked and I unchecked the other one to but it dose not change anything.

What device you use for talking USB/Onboard??

I use the iPhone Headset on the built in sound device.

I send it to a developer for next morning.

Thank you.

[Johanna]

Is there a Link or can you send me an earlyer build? I had no problem befor the update.

[Johanna]

I just realised, the CPU Usage goes up eaven if I'm not conected to a Server.

btw, that heats my Mac up to +80°C

[copper]

I have no problem with built-in capture and built-in playback. What happens if you choose them instead of iPhone's?

[nwerensteijn]

I just realised, the CPU Usage goes up eaven if I'm not conected to a Server.

btw, that heats my Mac up to +80°C

Can you check the cpu usage when you just started Teamspeak and before you do anything else, like connecting to a server?

[lgda_]

Hello,

I just noticed I had the same problem (TS3 rc2 build: 14642).
It uses more than 95% cpu (on a 2.93 GHz Quad-Core Mac Pro from 2009) as soon as I launch it (without connecting to any server) and the usage increase by some percents when I join a server.

I don't think I had this problem on the previous build but I'm not sure.

Thanks for this great application and continue the good work !

[Johanna]

The problem is still there, now I'm on Mac OSX Lion.

But I found a hint where the problem can be found:
When I open TS cpu usage raises instad to 40%, then I connect to the server, cpu is still at 40%. When I click now on the red x in the title bar the TS Client will not be displeyed anymore. Now the cpu usage goes down to 2% and I still can talk to the ppl.

So I think the problem has nothing to do with capture or playback, I think the problem has to do with the rendering of the skin.

I allso found out that if I switch to an other skin I cant switch back, I had to delete the entry in the .conf file to get back to standard.

I hope this informations help you.

[Johanna]

Can you check the cpu usage when you just started Teamspeak and before you do anything else, like connecting to a server?

CPU usage goes up right when I start Teamspeak and before I did anything else.

[nwerensteijn]

There is one more thing to test if you are up for it.
I don't have a mac while i am typing this, so this is from memory:
Inside the ts3client.app (or whatever it is called) there is somewhere a directory called soundbackends . In that folder there is/are one or several files like coreaudio_*.dynlib.

The test is to temporary rename them, so the are not .dynlibs any more. For example append ".temp" to the end of the file name
now restart ts3 again. It cant load sound backends now, so you can't hear any sound. The point is to see if you cpu usage is still high. If it is not, the problem is probably in the sound backend. Else the problem is in the GUI.

Don't forget to rename the files back to their original name.
Let me know how it goes