• Helix 🧬@feddit.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Yeah it’s basically Pulseaudio, but better. The devs have done a great job on iterating upon the already pretty good pulseaudio!

      • Auzy@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        I’d have to disagree with that. It wasn’t perfect and there were issues for many people at the beginning, but it united everything properly.

        Before then (in xmms days), don’t forget that audio in apps constantly didn’t work, and the sound servers often conflicted. It was far from a seamless experience.

        But, pipewire I agree doesn’t seem to have any downsides and finally fixes from what I felt was the last major issue (low latency)

        • wewbull@feddit.uk
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Pipewire replaces the need for jack, which was low latency audio routing between audio components. Pipewire even has jack compatible interfaces so you can use jack based apps with it.

          Then there’s the bit most people skip over. Pipewire does the same thing for video!

        • gens@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Didn’t work on my last two sound cards, and always had latency problems for many people.

          JACK is for profesionals. If you need to take an input from an instrument, run it through a software filter, and output it immediately. Or if you need to output from one program to another to another. Etc. Usually that means small buffers and a lot of cpu usage. Not really for normal desktop users. Grab a specialized distro like ubuntu studio and try it, if you want.