Announcement

Collapse
No announcement yet.

PipeWire Is In Increasingly Great Shape - Ready For More User Testing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Gps4l
    replied
    I will have to do some more investigation. I am on tumbleweed and it seems pipe wire is already installed.

    Man pipewire gives me this:

    Code:
    pipewire(1) General Commands Manual pipewire(1)
    
    NAME
    pipewire - The PipeWire media server
    
    SYNOPSIS
    pipewire [options]
    
    DESCRIPTION
    PipeWire is a service that facilitates sharing of multimedia content between devices and applications.
    
    The pipewire daemon reads a config file that is further documented in pipewire.conf(5)
    
    OPTIONS
    -h | --help
    Show help.
    
    --version
    Show version information.
    
    -n | --name=NAME
    Set the daemon name (Default pipewire-0).
    
    AUTHORS
    The PipeWire Developers <https://gitlab.freedesktop.org/pipewire/pipewire/issues>; PipeWire is available from http://pipewire.org
    
    SEE ALSO
    pw-mon(1), pw-cat(1), pw-cli(1),

    Leave a comment:


  • kode54
    replied
    Originally posted by pkunk View Post


    Something like:
    • systemctl --global mask pulseaudio.service
    • pacman -S pipewire-pulse
    • create /etc/ld.so.conf.d/pw-pulse.conf with /usr/lib/pipewire-0.3/pulse
    • add NoExtract = usr/lib/libpulse* to pacman.conf
    • pacman -S libpulse
    • reboot

    Don't use wireplumber it currently doesn't work with the latest pipepewire.
    Multilib and flatpaks will not support this setup.
    It would be surprising if Bluetooth works.
    I can't really recommend the ld.so.conf.d and delete libpulse method over tricking ldconfig with .0.999.0 symlinks, as the latter will still allow you to build and link libpulse-based applications on the system. Deleting the libpulse libraries from their normal location will break things, including linking copies of pipewire and the AUR lib32-pipewire package.

    Leave a comment:


  • kode54
    replied
    Hey? Guess who just packaged libpipewire and its associated modules, and the pulse and jack libraries, for Arch multilib? Meeeeee, that's who! Packaged in the AUR for now, since several of the dependencies are in the AUR as well.

    lib32-pipewire
    lib32-pipewire-jack
    lib32-pipewire-pulse

    Verified working with a Wine 32 bit application, specifically, foobar2000. I almost flubbed it up a bit first, missing packaging the libpipewire-module-*.so and spa-0.2 directories in the main pipewire package, which resulted in some spectacular crashes the instant I attempted to use audio output.

    Leave a comment:


  • nabero
    replied
    Originally posted by thxcv View Post

    I think you're right and Pulseaudio has improved. But honestly i.e. the BT support just sucks and anyone who tried to fix it just was thanked by giant headaches and throwing the code back to the garbage.
    Well, I'm kind of impressed that my bluetooth headset works without any issue out of the box, and I can stream audio from my android phone the same way. Couldn't get any of them in windows 10 (at least without installing anything - work laptop). To me, it's not that broken.

    Leave a comment:


  • thxcv
    replied
    Originally posted by finalzone View Post

    Without pulseaudio doing the heavy lifting, ALSA would be in a terrible mess circa 2000 and none of users would access functions like Bluetooth support, audio USB and more in a modern environment. Too bad you missed a lot as pulseaudio drastically improved since then.
    Pipewire got a solid start now that pulseaudio served its purpose exposing and fix ALSA drivers bugs which were overdue.
    I think you're right and Pulseaudio has improved. But honestly i.e. the BT support just sucks and anyone who tried to fix it just was thanked by giant headaches and throwing the code back to the garbage.

    Leave a comment:


  • lyamc
    replied
    Here's how to get it installed on Ubuntu 20.04

    Code:
    sudo apt install git build-essential meson cmake libsystemd-dev valgrind libdbus-1-dev libsdl2-dev libsndfile1-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libbluetooth-dev libsbc-dev libjack-jackd2-dev libvulkan-dev xmltoman
    git clone https://gitlab.freedesktop.org/pipewire/pipewire.git
    cd pipewire
    ./autogen --prefix=/usr
    make
    make install
    launch an app like mpv with

    Code:
    pw-jack mpv
    or
    Code:
    pw-pulse mpv


    To install wireplumber

    Code:
    sudo apt install git gobject-introspection libxml2-dev libglib2.0-dev libjson-glib-dev libgirepository1.0-dev
    git clone https://gitlab.freedesktop.org/pipewire/wireplumber
    cd wireplumber
    meson build . --prefix=/usr
    ninja -C build install
    For some reason the shared library isn't being created.

    Code:
    Checking if "audiofade" with dependency libpipewire-0.3 compiles: NO (cached)
    Last edited by lyamc; 05 September 2020, 03:12 PM.

    Leave a comment:


  • Mez'
    replied
    Thanks Nocifer and pal666 for your answers.
    I don't have the low-latency use and I couldn't care less about flatpaks.
    If it's going to help with wayland's shortcomings, it's probably a good thing... I'll use both in 2-5 years when they're mature then.
    I just hope Pipewire won't break what PA has been striving for in the last 10+ years. My main desktop is a HTPC and I have a good setup for audio/video. Wouldn't want to regress to a less confortable state.
    If, on the other hand, it makes things even better/easier and I'm somehow excited by some capabilities I could take advantage of, I will of course gladly embrace it.

    Leave a comment:


  • pal666
    replied
    Originally posted by Mez' View Post
    But, if I'm not using JACK, what is Pipewire going to bring for me that I would need it over PulseAudio?
    video and flatpak
    Originally posted by Mez' View Post
    If it's just something on top of PA, can't I just keep PA only and be happy like that?
    you can continue using pa-only apps, they'll work with pw without changes

    Leave a comment:


  • DiDiDi
    replied
    Really looking forward to getting rid of PulseAudio. The development has slowed down to a crawl - even getting a pull request adding functionality that should have been there 5 years ago reviewed/approved is hard. I mean, COME ON: https://gitlab.freedesktop.org/pulse...e_requests/227
    Last edited by DiDiDi; 05 September 2020, 11:34 AM.

    Leave a comment:


  • Nocifer
    replied
    Originally posted by Mez' View Post
    I was immediately convinced by the PulseAudio project, way before it was finalized.
    I liked what it wanted to bring to the table and as soon as it was usable I went for it, even with its initial issues.
    I've been playing with it since the beginning for 5.1 audio and it's been working fantasti. These days, it's well integrated and it doesn't get in the way at all.
    I'm not sure I understand fully what PipeWire does and might miss the point.
    But, if I'm not using JACK, what is Pipewire going to bring for me that I would need it over PulseAudio? If it's just something on top of PA, can't I just keep PA only and be happy like that?
    Basically, it will allow for unifying the various Linux multimedia stacks into one multi-purpose API capable of dealing with both low-latency and who-cares-about-latency audio, as well as video. And AFAIU it will also allow for various things impossible to do on Wayland that we take for granted on X, like screen recording, media casting, remote desktop and such.

    From the blog article linked in the OP:

    For those still unaware PipeWire is our effort to bring together audio, video and pro-audio under Linux, creating a smooth and modern experience. Before PipeWire there was PulseAudio for consumer audio, Jack for Pro-audio and just unending pain and frustration for video.
    So in other words it's Pulseaudio+Jack+GStreamer on steroids, but built from the ground up to play nicely together and with Wayland's capabilities and limitations in mind.

    Also, it's a given that Pulseaudio will eventually be deprecated in favor of Pipewire, and we will only be using a compatibility layer (pipewire-pulse, i.e. like we currently use pulseaudio-alsa to do the same thing between ALSA and Pulseaudio). So yeah, you can keep using Pulseaudio if you want, but a few years down the road there won't really be any reason for you to do so - not to mention that distros will be coming with it preinstalled instead of Pulseaudio, so there won't be any hassle on your part to set it up.

    (If I'm mistaken in anything, please feel free to correct me!)

    Leave a comment:

Working...
X