Results 1 to 2 of 2
02-06-2010, 21:49 #1-= TeamSpeak User =-
- Join Date
- Apr 2010
- Texas, USA
Beta21 (and prior) linux sound issues
I'm on Arch Linux, and I updated to beta21 for the pulseaudio support. I had these same results on Linux Mint 9 Isadora [based on Ubuntu 10.04 Lucid Lynx]. My sound card is whatever the onboard hda sound is on the ASUS M4A78 PLUS motherboard ("hardinfo" tells me Audio Adapter is "HDA-Intel - HDA ATI SB" and newegg says the audio chipset is "Realtek ALC887" (8 channel), if that's of any use.. apologies, I'm not great with hardware) . Other apps using pulse have no trouble with either input or output, and my voice bar lights up properly in the input section of gnome-volume-control.
Bug 1? ) The selected capture device (in my case, ALSA=>plughw) doesn't get removed from the capture devices list when switching audio capture modes/engines (in my case, to Pulse), resulting in the device showing up where it shouldn't with "invalid" next to it. This can be worked around user-side by selecting a valid capture device for that mode/engine and reloading ts3. A proper solution would probably be for teamspeak to switch to the corresponding default capture device when the mode/engine is changed.
Bug 2? ) Switching from Pulse=>Default-Input back to ALSA=>plughw (working mic setting in beta20) gives an error about the capture device being invalid even though it works on reloading ts3 / copying over a good old config file with identical settings and worked seconds prior to changing it in the first place.
Bug 3? ) The default capture devices in ALSA and PulseAudio don't work at all (and never have) on either Arch Linux or Linux Mint 9 even though I'm pretty sure they do on other apps' default settings. Instead, it makes an odd, increasingly loud cymbal/tearing-paper/loud-patting sound. None of the valid input devices at all work on the Pulse plugin, but plughw input does work on ALSA through pulse.
Bug 4? ) Pulseaudio output works fine, but the information sent to pulseaudio about the pulse stream in teamspeak is bad/non-existent. I'm not sure if this is a bug, configuration problem, or what have you, but "<unknown>"/"Mixer Stream" is pretty useless and shows up in both OS's.
EDIT: It seems bug 2 is possibly related to bug 1. I swear last time I restarted teamspeak after changing audio I still had problems.. but trying to re-create that "bad config" folder/files several times, it gives "invalid audio device" until reloading ts3, at which point it works fine, so I am probably mistaken. Perhaps a message to reload the client is in order?
EDIT2: Re-wrote this post to be easier to read.
Last edited by FrozenFox; 02-06-2010 at 22:46.
04-06-2010, 05:19 #2-= TeamSpeak User =-
- Join Date
- Jun 2010
Im using arch64 and on update to beta21 i have this error:
"Failed to open playback device" and "Failed to open capture device"
In logs appear this:
|CapFMOD | 1| Error! You are using an old version of FMOD 274689. This program requires 274690
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)