Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 405
    • Issues 405
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • pipewirepipewire
  • Issues
  • #1973

Closed
Open
Created Jan 01, 2022 by platyple@platyple

routing issues with high channel counts

  • PipeWire version (pipewire --version): 0.3.42
  • Distribution and distribution version (PRETTY_NAME from /etc/os-release): Arco Linux
  • Desktop Environment: XFCE
  • Kernel version (uname -r): 5.15.12

Description of Problem:

I have a 16-channel mixing desk, and i want to split all 16 channels into separate devices. All loopbacks are created correctly but the routing is entirely wrong after channel 6

How Reproducible:

consistent

Steps to Reproduce:

  1. Buy a 16-channel mixing desk
  2. Insert this wall of text into your config: split_inputs
  3. Replace device name with that of your desk (optional)

Actual Results:

Channels 1-6 (FL to LFE) are routed correctly, 7 and 8 get their signal from 3 and 4 (RL and RR) respectively, and 9 through 16 get theirs from 1 and 2 (FL and FR). It's easiest to see in Helvum.

Expected Results:

A one-to-one patch of all channels

Additional Info (as attachments):

  • pw-dump > pw-dump.log: pw-dump.log
Edited Jan 01, 2022 by platyple
Assignee
Assign to
Time tracking