Skip to content
GitLab
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 581
    • Issues 581
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #715
Closed
Open
Issue created Feb 12, 2021 by Chris Robinson@chriskcat

Audio recording does not pick playback monitor devices

OS: Debian Testing

PipeWire v0.3.19

When recording audio (using pw-record from PipeWire, parecord from PulseAudio, arecord from ALSA using either the pipewire or pulse devices, or my own apps using the PulseAudio API), it connects directly to the output of a specific playback stream in a specific app rather than the monitor device that's a mix of all streams playing out through the device. See this screenshot for how PipeWire automatically connected the recording app, with Pale Moon playing two streams, as seen in QjackCtl:

Screenshot_20210212_003242

With my own apps that use the PulseAudio API, it reports being connected to "Monitor of Starship/Matisse HD Audio Controller Analog Stereo" (the correct/expected device, which is "HD-Audio Generic" in JACK), but is not actually connected to it. With QjackCtl, I can manually reconnect the recording app's input to the monitor outputs and it then correctly records the device mix, but the next time the app runs, it connects to one of the app's output streams again.

My system has no other recording device, if that may be relevant. The (hardware) recording device that's there has nothing plugged in, so is unavailable/not present and disabled with the selected profile.

Assignee
Assign to
Time tracking