Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pipewire
pipewire
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 183
    • Issues 183
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • pipewirepipewire
  • Issues
  • #249

Closed
Open
Opened Jun 26, 2020 by Sergey Kondakov@fox

Achieve parity and/or surpass PulseAudio in Bluetooth audio support

There is great work going on by @pali for BT audio in PA and kernel. As PA replacement, PW must match it. See:

  • #136 (closed) - about A2DP
  • #45 - about HSP/HFP
  • pulseaudio/pulseaudio!288 (comment 499854) - about kernel API

There would need to be CLI and GUI to match pasystray / paman / pavucontrol / paprefs / pavumeter combo.

Ideally, any such interfaces should be developed with Wi-Fi Direct & Miracast in mind to accommodate for potential WiFi display and audio devices which would be technically superior to BT and would free us from its OSI non-compliant profile & modem nonsense.

Edited Jun 27, 2020 by Sergey Kondakov
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pipewire/pipewire#249