Package Details: pipewire-common-pulse-git 1.0.0.r591.gaf310523-1

Git Clone URL: https://aur.archlinux.org/pipewire-common-git.git (read-only, click to copy)
Package Base: pipewire-common-git
Description: Low-latency audio/video router and processor - PulseAudio replacement
Upstream URL: https://pipewire.org
Licenses: MIT
Conflicts: pipewire-pulse, pulseaudio, pulseaudio-bluetooth
Provides: pipewire-pulse, pulse-native-provider, pulseaudio, pulseaudio-bluetooth
Submitter: eh5
Maintainer: eh5
Last Packager: eh5
Votes: 5
Popularity: 0.000000
First Submitted: 2021-01-10 08:40 (UTC)
Last Updated: 2024-03-29 06:17 (UTC)

Required by (443)

Sources (1)

Pinned Comments

PedroHLC commented on 2021-01-11 22:53 (UTC)

If someone needs any of these packages pre-built, chaotic-aur builds them hourly...

eh5 commented on 2021-01-10 12:03 (UTC) (edited on 2021-01-16 20:46 (UTC) by eh5)

@FabioLolix This one has gstreamer support (provides gst-plugin-pipewire) and hsphfpd support enabled.

(All below is edit message for anyone who interests.)

Be aware that https://aur.archlinux.org/packages/gst-plugin-pipewire-git/ depend by pipewire-git is not part of pipewire-git package base.

Many people request[1-2] the maintainer(https://aur.archlinux.org/account/sl1pkn07) of pipewire-git to enable gstreamer support but seems he refuse to do that. Despite gstreamer support is enabled by default in upstream (also in Arch repo) and gstreamer plugin is a dynamic loadable library which is capable to be split into separate package.

And some request to orphan or delete pipewire-git but all has been rejected by TU[3].

There was a VCS package solved gstreamer problem named pipewire-nightly, but a TU decides to delete it for the reason that the suffix "-nightly" in package name imply that it has to be a snapshot package[4].

Those are reasons why I create this package base.

[1] https://aur.archlinux.org/pkgbase/pipewire-git/?O=20&PP=10#comment-775875

[2] https://aur.archlinux.org/pkgbase/pipewire-git/?O=10&PP=10#comment-777463

[3] https://lists.archlinux.org/pipermail/aur-requests/2020-December/thread.html (search keyword "pipewire")

[4] https://lists.archlinux.org/pipermail/aur-requests/2020-December/047836.html

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Dude803 commented on 2021-06-06 18:35 (UTC)

Starting yesterday (June 5) I am experiencing a weird error on package upgrade: cannot resolve "libwebrtc_audio_processing.so=1-64", a dependency of "pipewire-common-git". Is this something wrong on my end or is this something wrong with the package?

eh5 commented on 2021-05-19 01:51 (UTC) (edited on 2021-05-20 00:31 (UTC) by eh5)

edit: Following "extra/pipewire", I have removed all /usr/share/pipewire/**/*.conf entries from backup=() array. From now on all files under /usr/share/pipewire would be overwritten during upgrading.

@Netboy3 It's OK as long as pacdiff is used and the diffs are properly handled after every pipewire upgrading.

pipewire currently don't merge config from multiple files, it search config name from ~/.config/pipewire, /etc/pipewire, /usr/share/pipewire and only accept the first one found.

For someone (like me) who has custom property values in configs and still want other properties to be in sync with upstream, /usr/share/pipewire + pacdiff might be an easier way to go. Otherwise, one might need to write a custom script to sync changes from /usr/share/pipewire to /etc/pipewire on every upgrading, or do it manually.

Netboy3 commented on 2021-05-19 00:59 (UTC)

Thanks for updating the package promptly. Your part (3) advice is not recommended. Normally /usr/share is reserved for package content, not user managed configs. Advising users to modify /usr/share configs is not recommended and most packages will warn you that any changes to /usr/share will be overwritten during package updates. This is especially concerning when the developers provide the users with two locations for overriding/modifying the configs (/etc/pipewire and ~/.config/pipewire).

eh5 commented on 2021-05-18 23:52 (UTC) (edited on 2021-05-20 00:26 (UTC) by eh5)

Config files are now installed to /usr/share/pipewire, all previously installed configs in /etc/pipewire would be renamed to *.pacsave. You have several options to migrate those files.

  1. If you have never modified any config property in /etc/pipewire, you can safely delete all those *.pacsave. (e.g. rm /etc/pipewire/**/*.pacsave or rm -rf /etc/pipewire)

  2. Remove .pacsave postfix from config files you have modified, pipewire would still read config from /etc/pipewire and it has higher priority than /usr/share/pipewire.

Netboy3 commented on 2021-05-18 14:34 (UTC) (edited on 2021-05-18 14:35 (UTC) by Netboy3)

In the latest master, pipewire changed the package-delivered config directory from /etc/pipewire to /usr/share/pipewire. The /etc/pipewire is still being scanned for systemwide config changes, but is optional for the system admin to modify. This requires a few _pick and install invocations to be adjusted.

eh5 commented on 2021-03-05 00:15 (UTC)

Dropped JACK SPA plugin following "extra/pipewire", if your setup needs pipewire to perform a JACK device role, please switch to pipewire-full-git, pipewire-full-jack-client-git.

eh5 commented on 2021-02-25 07:46 (UTC) (edited on 2021-02-25 08:49 (UTC) by eh5)

Check which version you upgraded from in /var/log/pacman.log (e.g. cat /var/log/pacman.log | grep pipewire-common-git -C 10 | tail -n 20).

The service enabling command should be executed if you upgrade pipewire-common-git from a version less than 0.3.22.r46.ge340a44a-2. (see https://aur.archlinux.org/cgit/aur.git/tree/pipewire.install?h=pipewire-common-git&id=1ec9f9db66eb2faf4b286877c0e5be0f429d7461#n12) If you have already manually enabled the service, the install script would not outputs any hint message even if it re-runs the service enabling command.

edit: Updated with https://aur.archlinux.org/cgit/aur.git/commit/?h=pipewire-common-git&id=c33c0c09b7450bac58e6d0046dc84cc1ff43d3f3.

amoka commented on 2021-02-25 02:04 (UTC)

For some reason the install script is not enabling pipewire-media-session.service for me.

eh5 commented on 2021-02-24 09:33 (UTC) (edited on 2021-02-24 15:03 (UTC) by eh5)

The execution for pipewire's media session is now split out into pipewire-media-session.service. Enable the service manually with systemctl --user enable --now pipewire-media-session.service, or (force) rebuild the pacakge base and then install script will do it for you.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »