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

bluez5-device: use correct RTP payload type

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Tanu Kaskinen requested to merge tanuk/pulseaudio:a2dp-payload-type into master Jan 17, 2019
  • Overview 2
  • Commits 1
  • Pipelines 1
  • Changes 1

THIS IS UNTESTED! If that's a problem, someone needs to test this, but given the nature of the change, what could possibly go wrong? :)

If one device tries to use PulseAudio to send audio over A2DP to another device with bluez-alsa, that doesn't work because PulseAudio uses an incorrect RTP payload type and bluez-alsa checks that the RTP payload type is correct. According to the A2DP spec, the payload type should be set to a number between 96 and 127.

Fixes: #591 (closed)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: a2dp-payload-type