• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Linux Audio ALSA, Pulse, OSS4 or JACK?

What do you use for linux audio?

  • ALSA

    Votes: 4 66.7%
  • Pulse

    Votes: 1 16.7%
  • OSS3 (deprecated)

    Votes: 0 0.0%
  • OSS4

    Votes: 1 16.7%
  • JACK

    Votes: 0 0.0%

  • Total voters
    6

monte84

New Member
Joined
Jan 19, 2008
Messages
153 (0.02/day)
System Name HeadShot
Processor AMD Phenom II X6 1055T @ 3.71 1.45V (265*14) 41C load Prime95
Motherboard Gigabyte GA-890FXA-UD5
Cooling Corsair H60 Push/Pull config
Memory 2*4GB Crucial Ballistix Tactical 1866 @ 1766 (265*6.66)
Video Card(s) Gigabyte HD6950 2GB Unlocked Shaders 840 core/1300 mem
Storage 2*Seagate 500GB 7200.11
Display(s) Samsung 32in
Case Corsair 400R Carbide
Audio Device(s) Auzentech X-Plosion w/ OPA627AU OPAMP & AKG-K601
Power Supply TT 850watt TR2-TRX
Software Windows 7 Home Premium 64bit
Which do you use with what distro and why?

I switched to OSS4 because of issues with ALSA / Pulse. Getting digital out just wasnt working for some reason. OSS4 simeple checkbox in ossxmix. I also think OSS4 sounds a bit better as well. Using Auzentech X-Plosion w/ OPA627 opamp and AKG K-601 cans.
 
Pulse and Jack are sound servers. You would still need the actual drivers for you sound chip, which are alsa and oss3/4.

I never had issues with alsa drivers, so I don't see any reason to switch over to oss4. Used oss4 for a while to try it out, but it did nothing alsa was doing for me already.

I use Pulse on my Ubuntu machines and any other distro that integrates it. It's pretty neat, and once you configure it for your particular device it works very well. Some stuff still doesn't work with it, but that's mostly the fault of the software developers not wanting to adapt and change their code to accommodate Pulse. Pulse does have bugs, but the maintainers are doing a pretty good job at squashing them.

I do remove pulse if I find myself using anything that's not GNOME (KDE in my case). PA development is very much GNOME centric and most of the support is for that DE. As such, many older KDE and qt apps. don't really work with it. Furthermore, the graphical interfaces for PA are gtk (and said interfaces are very useful). I don't have a problem with running gtk on my KDE desktops, but these interfaces in particular are very buggy under KDE; they either crash or peg my quad at 100% usage every time I launch them.

So, in most cases I use pure alsa, since I'm mostly a KDE guy (unless the distro really buries PA into the DE, like Fedora tends to do) . When I switch over to GNOME then I use alsa + PA. When I'm running older machines and minimalistic distros (like Puppy) I just keep the bare essentials necessary for working sound (which usually means plain old alsa).
 
Last edited:
Backing up the post above, I always use the ALSA drivers, on Fedora there are simple control panels for the driver and I never have had trouble getting them to work correctly. I say just use your package manager should be simple as a breeze.
 
Pulse has severe quality issues when playing more than one stream on my box. I am not interested in debugging it, as the developer should have done this. I have used ALSA since the very early Redhat days and it has always 'just worked'. :respect:
 
Distro: Heavy modified Xubuntu 9.10
Why: I live in South Africa, international internet is expensive, Ubuntu has official local mirror. :)

I voted PA ^_^ but yeah sort of on top of ALSA so ... ALSA all the way! Unfortunately sometimes one is forced to use OSS like for Teamspeak2 or Enemy Territory Wolfenstein, but then I will try to use aoss. At the moment PA consumes too much of my old slow pc's resources, so I try my best to use ALSA natively.
 
Back
Top