Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

pipewire: use the native gstreamer element in clients instead of alsasink

Description

Continuing from SPEC-2626

Pipewire should install the gstreamer elements that it comes with and the apps should use pwaudiosink instead of alsasink.
 
 
Originally I wanted to avoid that so that the apps don't have to use an agl-specific gstreamer element, but as it turns out there are a couple of limitations with alsasink:

  • it's not very easy to change the default latency in order to solve this issue

  • it has no way of reporting back to the application that there is another higher-priority app that has taken over the audio stream, making it impossible to implement policies (and it actually hangs if the session manager decides to unlink it from the device)

  • there is no way to specify the role of the stream without hacks

 

Environment

None

Activity

Show:

George Kiagiadakis 
September 2, 2019 at 3:51 PM

This was already merged in 8.0.0

Scott Murray 
July 24, 2019 at 10:25 PM

I've uploaded changes to convert the ondemandnavi and phone applications.  I'll rework the patch for the older navigation application tomorrow.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Priority

Created July 11, 2019 at 3:43 PM
Updated September 19, 2019 at 12:07 PM
Resolved September 2, 2019 at 3:51 PM

Flag notifications