Client Mac OSX 3.0.0 Speakers/Headphones disabled

[Kuplasven]

Read this, before you open a post with your problem
You can test our fixed version 3.0.1 through the beta channel

How to:
- Download the update.zip and unzip it.
- Now take the file called update.ini and put it in your client folder
Example for Windows users

C:\Program Files\TeamSpeak 3 Client

- Start the client and update your client per Help > Check for Update


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


... and cannot be re-enabled. Running OSX 10.6.8, have Bose Companion 5 speakers, and have no fancy peripherals. Nothing can be enabled in the way of playback. Not Default. Not Built-In Output. And not the fancy Bose speakers. The thing says "Error opening playback device: could not open playback device." I know the things are set up as I'm currently listening to them, and went so far as to set them up two and three times despite the fact that they work (the TS issue notwithstanding). How do I fix this wonderful new problem with the ever-problematic TS3?

[babytnt27]

Since yesterdays update I have been having issues. First my husband and I couldn't log in. We had to delete the server address and re-enter it in order to get in. Then I started getting this error opening playback device: could not open playback device. Im using the same device as before and i tried the other devices and get the same response over and over again. The mic is working fine but cannot get sound. What do I do?

[babytnt27]

I too am having the same issue and got it to work once but now today its doing the same thing. If you find the answer, please let me know. This all started since I accepted the update... never had these issues before the update.

[lupin77]

i have found one of 2 ways to get around the problem which are: either try to get the teamspeak rc2 version and dont update (previous version) or you can download soundflower for free and route teamspeak output through soundflower and soundflower output through your headset

[babytnt27]

So, I see I still have NO Help here! TY ts3 employee's for your help!

[dante696]

You should give us more informations about your operation system, your client version and your playback and capture setings in your client.
What settings have you tried.

[Kuplasven]

You see, that's the genius bit! I can't actually find the old, unpatched program. And why the hell would I download another mysterious program to make the first work now that I've downloaded a patch? It's utter BS that this should happen every single time I do anything that TS tells me to do! Seriously, here we are, 9 days after the problem has started, and absolutely nothing is forthcoming from the legendarily indifferent TeamSpeak! I guess I shouldn't be surprised as it took me a full six months to get a push-to-talk button. I hope they can improve on that. But seriously, get it right the first time! That's something your entire family structure should have ground into your head as a child, TeamSpeak!

[MrMikeMGM]

I'm on MacOS 10.7.1 running TS 3.0.0 [Build: 14954]

I've been using a Netcom GN9350E without issue with TS3 until the most recent update. Since the update I have to push the output through the built in line-out on my iMac because when I try to use the GN9350 I get "Error opening playback device" errors.

For what it's worth, the capture/mic works fine. This issue is only affecting playback.

Further, when I launch TS3 it gives me an error saying "The configured playback device was not found."

I've attached screen shots of details.

[Nasrudin]

Soundflower actually broke for me last patch.

[dante696]

Can you offer any client log for us?

[MrMikeMGM]

Absolutely. Here you go.

[nwerensteijn]

What kind of speaker setup do you have? 2 channels (headset / normal speakers) or surround sound? (like quadraphonic/5.1/7.1)

[MrMikeMGM]

When I use my built in output jack on the iMac it goes to a Bose 3 speaker (2 + sub) set. That works just fine.

When I use the GN 9350 E as my output, it should go to the headset, but it throws those errors instead.

Does that answer your question?

[nwerensteijn]

This should be fixed in our next beta release (hopefully today)

[MrMikeMGM]

Do I need to access anything special to get the new Beta when it's released or does Beta code get pushed out during standard update checks?