0

On Fedora 17. Using a ct-xfi driver. I have my speakers configured, and everything works great.

Until I start up mumble, or Teamspeak, and either one hooks up to start recording audio. Then it's all over. All sound playback stops, and seems like it's in a huge buffer.

A few moments after quitting mumble, or Teamspeak, all sound catches back up, or is released.

I cannot find anything on the Google about this particular problem, and fiddling with various sound settings and input/output drivers within mumble or teamspeak has absolutely no effect.

Thanks for any help, I'll be around to provide more information of course.

EDIT: Fedora 17 KDE uses Pulseaudio, and so I'm using Pulseaudio.

Improve this question
1
  • What is your Audioserver? Pulsaudio? ALSA?
    – Christopher Perrin
    Aug 10, 2012 at 22:06

1 Answer 1

Reset to default
0

This sounds like mumble and TS are blocking the soundcard. You should check that mumble uses Pulsaudio as soundserver and not OSS. Look under Settings and make sure that Adveanced is ticked.

Improve this answer
3
  • Yeah, they're both using PulseAudio, I've gone through all the various audio backends to no luck.
    – BeepDog
    Sep 19, 2012 at 15:55
  • Of course, I fire it up again, and everything just works. Perhaps there was a horrible glitch in the packages :(
    – BeepDog
    Sep 19, 2012 at 15:59
  • This doesn't work again :( Seems to block all output.
    – BeepDog
    Nov 21, 2012 at 23:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.