pipewire: set node.link-group on virtual and internal filter nodes - #5273
Merged
wwmm merged 1 commit intoAug 31, 2026
Merged
Conversation
Every node here already sets node.group, but never its sibling property node.link-group, which is what WirePlumber's Bluetooth autoswitch (and other filter-chain-aware linking scripts) use to see through an app's internal chain to the real device behind it. Without it, WirePlumber can't tell that a client capturing from Easy Effects Source is transitively using a Bluetooth headset's mic, and never switches the profile to HFP. PipeWire's own module-filter-chain.c sets both properties together automatically whenever either is missing, so this just brings Easy Effects' own node creation in line with that convention. Related to wwmm#4878 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Workflow failed, but the following artifacts are still available for this pull request: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ran into this chasing a bug where my Bluetooth AirPods mic never worked in Slack when routed through Easy Effects - WirePlumber's Bluetooth autoswitch (
bluetooth.autoswitch-to-headset-profile) never flipped the headset into HFP mode, so the mic stayed silent no matter what.Turned out to be a
node.link-groupgap. Easy Effects setsnode.groupon its virtual sink/source and internal filter nodes, but never sets the sibling propertynode.link-group. WirePlumber'sautoswitch-bluetooth-profile.luarelies onnode.link-groupto walk through a filter chain and find the real device behind it - since it's missing here, the script can never see past Easy Effects, and the profile switch never fires.PipeWire's own
module-filter-chain.csetsnode.groupandnode.link-grouptogether automatically whenever either is missing, so this just brings Easy Effects' own node creation in line with that existing convention.This alone isn't quite enough on the WirePlumber side either. Its filter-chain walk also expects
media.class == Stream/Input/Audioon internal nodes, which Easy Effects doesn't set, and its cycle guard needs a small fix too. Got a patch for that on the WirePlumber side as well, and tested both together: a Bluetooth mic captured through Easy Effects now correctly switches profile and reverts afterward.Related to #4878
Here's the wireplumber patch for reference.