Package Details: pipewire-common-jack-git 0.3.30.r143.ga19ab4a2-1

Git Clone URL: (read-only, click to copy)
Package Base: pipewire-common-git
Description: Low-latency audio/video router and processor - JACK support
Upstream URL:
Licenses: GPL2, MIT
Conflicts: pipewire-jack
Provides: pipewire-jack
Submitter: eh5
Maintainer: eh5
Last Packager: eh5
Votes: 4
Popularity: 0.198336
First Submitted: 2021-01-10 08:40
Last Updated: 2021-06-20 15:28

Pinned Comments

PedroHLC commented on 2021-01-11 22:53

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

Latest Comments

1 2 3 4 Next › Last »

eh5 commented on 2021-06-08 12:05

@jintseng Seems like a pacman database problem of some mirrors or the upstream. Maybe switching mirrors helps?

I could rollback it to depends on webrtc-audio-processing instead, if you want.

jintseng commented on 2021-06-08 11:53

@eh5 experiencing that error as well (unable to resolve the libwebrtc dep) - I was able to install pipewire by updating my webrtc-audio-processing to version 0.3.1-3 which yay/pacman wasn't updating.

Use yay --getpkgbuild webrtc-audio-processing and build it yourself makepkg then install.

eh5 commented on 2021-06-06 18:43

@Dude803 I guess you would need to update your packages repo, the is provided by webrtc-audio-processing.

But somehow AUR web also can not recognize

Dude803 commented on 2021-06-06 18:35

Starting yesterday (June 5) I am experiencing a weird error on package upgrade: cannot resolve "", 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

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

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

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

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

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

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 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