Package Details: pipewire-audio-git 1.2.0.123.g89bf8b856-1

Git Clone URL: https://aur.archlinux.org/pipewire-git.git (read-only, click to copy)
Package Base: pipewire-git
Description: Low-latency audio/video router and processor (GIT version) - Audio support
Upstream URL: https://pipewire.org
Licenses: MIT
Conflicts: pipewire-audio, pipewire-ffmpeg-git
Provides: pipewire-audio
Submitter: sl1pkn07
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 15
Popularity: 0.000586
First Submitted: 2017-09-19 15:57 (UTC)
Last Updated: 2024-08-09 09:31 (UTC)

Dependencies (85)

Sources (1)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 16 Next › Last »

brknrobot commented on 2021-03-11 20:15 (UTC)

These options fix the build.

    -D udevrulesdir=/usr/lib/udev/rules.d \
    -D docs=enabled \
    -D jack=disabled \
    -D gstreamer=disabled \
    -D gstreamer-device-provider=disabled \
    -D ffmpeg=enabled \
    -D libcamera=disabled \

tinywrkb commented on 2021-03-11 15:54 (UTC)

@sl1pkn07 I won't post here anymore about changes. I switched my systems to the stable release.
For testing I'm using my own packaging now that is more in sync with extra/pipewire and it's easier for me to keep it updated this way.

@GraysonPeddie that's due to a recent update in the build system. You need to change true->enabled and false->disabled for the meson config. You also need to explicitly set the vulkan option as disabled due to a regression introduced by this update.

Also, you should consider building in a chroot, I highly recommend using aurutils.
There are automatic build options that will be caught if you have a specific lib installed in your host system.
You wouldn't hit that conflict if you had built in a clean chroot.
But it doesn't change the fact that this is due to outdated packaging.

GraysonPeddie commented on 2021-03-11 14:28 (UTC)

I'm not able to proceed with building pipewire-git as I've had to update the PKGBUILD file every time I try to rebuild it.

../pipewire/meson.build:1:0: ERROR: Value "true" (of type "string") for combo option "Build documentation" is not one of the choices. Possible choices are (as string): "enabled", "disabled", "auto".

Also, I've ran into this problem:

Packages (6) pipewire-1:0.3.23-1 [removal]  pipewire-jack-1:0.3.23-1 [removal]
             pipewire-pulse-1:0.3.23-1 [removal]
             pipewire-git-0.3.23.57.gbdea557f-1
             pipewire-jack-git-0.3.23.57.gbdea557f-1
             pipewire-pulse-git-0.3.23.57.gbdea557f-1

Total Installed Size:  6.22 MiB
Net Upgrade Size:      0.53 MiB

:: Proceed with installation? [Y/n] 
(3/3) checking keys in keyring                     [######################] 100%
(3/3) checking package integrity                   [######################] 100%
(3/3) loading package files                        [######################] 100%
(3/3) checking for file conflicts                  [######################] 100%
error: failed to commit transaction (conflicting files)
pipewire-git: /usr/lib/gstreamer-1.0/libgstpipewire.so exists in filesystem (owned by gst-plugin-pipewire)
Errors occurred, no packages were upgraded.

bin commented on 2021-03-10 13:11 (UTC)

Please add provides=("pipewire-alsa" "pipewire-jack" "pipewire-media-session" "pipewire-pulse").

sl1pkn07 commented on 2021-03-04 22:44 (UTC)

later

greetings

tinywrkb commented on 2021-03-04 22:05 (UTC)

@sl1pkn07 please update the packaging. Here's again a patch following the latest changes to extra/pipewire.
I just went through this fast so it needs another set of eyes to confirm nothing is broken.

https://gist.github.com/tinywrkb/3e340f21bf5c5178b4ef6bab9eb89702

tinywrkb commented on 2021-02-25 11:50 (UTC)

The official recommendation now is to use the systemd service so let's keep it this way unless the extra/pipewire maintainers decide otherwise.

tinywrkb commented on 2021-02-25 04:43 (UTC)

p.s. with regards to enabling the pipewire-media-session.service there's a discussion here.
I'm not entirely convinced that enabling the service is the right approach.

tinywrkb commented on 2021-02-25 04:22 (UTC)

@all, there's a new service that you might need to enable if you updating before my suggested changes will be applied. So something like the following.

# systemctl enable --global pipewire-media-session.service
$ systemctl start --user pipewire-media-session.service

@sl1pkn07. a bit large update here https://gist.github.com/tinywrkb/6db1b588f673d5c941071996a394463c

Changes:

  • Sync with extra/pipewire, including some of the cosmetics. The main difference I kept is not moving the jack.conf to the split package, I tend to not agree with this, let's just keep the configs with the pipewire-media-session daemon, and this is how it's package in Fedora.
  • Drop ffmpeg spa plugin, iiuc it's supposed to be internally used but it doesn't seem to be useful and it's not enabled by default or in the Fedora builds packaged by wtaymans.
  • Globally enable the new pipewire-media-session systemd user service. I set the version in the vercmp call as the most recent one, 0.3.22.60.geacda22a-1, feel free to revise this.
  • I hope I haven't missed anything, it's working on my system correctly.

tinywrkb commented on 2021-02-24 20:53 (UTC)

@blackout pulseaudio-alsa is a compat config to make ALSA apps work through PulseAudio.

pipewire-alsa serves a different purpose, it lets ALSA apps work through PipeWire, so it's not the same.

I believe that there's nothing that stops you from using pulseaudio-alsa with PipeWire and then ALSA apps go through the Pulse server of PipeWire though I haven't tried.