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 575
    • Issues 575
    • 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
  • #415
Closed
Open
Issue created Nov 25, 2020 by Carlos Augusto@silvaesilva

Create Pulse Input/Outputs connected to Jack Inputs/Outputs

Currently in a Pulse + Jack setup it is possible to leverage the jack pulse module that shows up as a device in pulse and a connection in Jack.

This allows us to create two different endpoints:

  • a pulse Input, that can be defined as default and show up as an Output on the Jack Side
  • a pulse Output, which can also be defined as default and show up as an Input on the Jack Side

I am not sure if we are only missing documenting how to achieve that or if the capability is not yet there. As an interim solution, directly mapping some Input/Output currently existing in Jack to the Pulse side as Source/Sink could work for some of these scenarios.

Assignee
Assign to
Time tracking