Prevent changing channel number (zero-indexing vs one-indexing)
- PipeWire version (
pipewire --version
): 0.3.71 - Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
): Fedora Linux 38 (Workstation Edition) - Desktop Environment: Sway
- Kernel version (
uname -r
): 6.2.15-300.fc38.x86_64
Description of Problem:
PipeWire re-numbers client ports to start at 1 even when the client numbers its own ports starting at 0. This is confusing, and doubly so when using with devices in "Pro Audio" profile, which numbers ports starting at AUX0.
It would be great if there were a way to turn this feature off or override it in some way.
How Reproducible: 100%
Steps to Reproduce:
- Start a client which uses zero-indexed channels (e.g. SuperCollider)
- Observe channel ports named out_1, out_2, etc...
Actual Results
"info": {
"direction": "input",
"change-mask": [ "props", "params" ],
"props": {
"format.dsp": "32 bit float mono audio",
"node.id": 108,
"object.id": 110,
"object.path": "SuperCollider:input_0",
"object.serial": 122,
"port.alias": "SuperCollider:in_1",
"port.direction": "in",
"port.id": 0,
"port.name": "in_1"
},
Expected Results:
"info": {
"direction": "input",
"change-mask": [ "props", "params" ],
"props": {
"format.dsp": "32 bit float mono audio",
"node.id": 108,
"object.id": 110,
"object.path": "SuperCollider:input_0",
"object.serial": 122,
"port.alias": "SuperCollider:in_0",
"port.direction": "in",
"port.id": 0,
"port.name": "in_0"
},
Additional Info (as attachments):
-
pw-dump > pw-dump.log
: pw-dump.log