Match application.process.binary

[codefaux]

I would very much appreciate also having support for application.process.binary matching.

Justification: Many simple "webapps" can't be detected properly otherwise.

Discord (Flatpak) is "Chromium"
Youtube Music (AUR app) is "Chromium"
Emby Theater (Extra repo) is "mpv"

application.process.binary is the only way to tell the two apart.

[codefaux]

I have created two branches which addresses this and #10

One branch is basic, matches node.name OR node.desc, application.name OR application.binary

https://github.com/codefaux/pipeswitch/tree/add_description_and_binary_match

One branch is configurable, adds bools for each match potential, default true.

https://github.com/codefaux/pipeswitch/tree/add_rule_match_booleans

Are you open to PR? Which would you prefer to see?

EDIT: I should note that these are WIP repos as of now, and I'm still working on testing/fixes on my end.

[codefaux]

I'm having difficulty getting application.process.binary to read. I get either

2025-09-24T12:17:05-07:00 - WARN - property 'application.process.binary' not found in object 133 of type PipeWire:Interface:Node: {"client.api": "pipewire-pulse", "application.name": "Chromium", "node.name": "Chromium", "media.class": "Stream/Output/Audio", "factory.id": "7", "client.id": "132", "object.serial": "282"}

or

2025-09-24T12:09:35-07:00 - WARN - property 'application.process.binary' not found in object 132 of type PipeWire:Interface:Client: {"pipewire.protocol": "protocol-native", "pipewire.sec.pid": "1002", "pipewire.sec.gid": "1001", "module.id": "2", "pipewire.sec.socket": "pipewire-0", "pipewire.sec.uid": "1000", "obje
ct.serial": "264", "pipewire.access": "unrestricted", "application.name": "Chromium"}

...BUT, the value IS populated; I know for sure because I was looking explicitly for a simple routing daemon to modify AFTER finding that application.process.binary WAS POPULATED and could thus be used to differentiate Chromium-based clients!

[target/debug]$ wpctl inspect 132
id 132, type PipeWire:Interface:Client
    application.language = "en_US.UTF-8"
  * application.name = "Chromium"
    application.process.binary = "youtube-music"

The commit adding application.process.binary to a Client is here;
52ec977

I haven't committed/pushed the application.process.binary change to a Node instead of a Client, but it's implemented similarly. Both state that there is no application.process.binary, but repeatedly, every single time, it IS there. Any input would be greatly appreciated, this is a significant issue for me and I'm not seeing a way forward.