diff options
| author |   George Kiagiadakis <george.kiagiadakis@collabora.com> | 2019-10-04 23:07:46 +0300 |
|---|---|---|
| committer | George Kiagiadakis <george.kiagiadakis@collabora.com> | 2019-10-05 09:44:58 +0300 |
| commit | 48e10ccbf966b091de28ad60f3a5983f30a8a956 (patch) | |
| tree | db729936e866c3d96054688b4afd0f23fd27b58e /ATTIC/meta-audio-4a-framework/recipes-multimedia/4a-hal-device-config/4a-hal-vendor-config.bbexample | |
| parent | 2a069d5124121336a77573e95dde9c8c34b872ec (diff) | |
meta-pipewire: add recipe to build the bluez-alsa-pipewire gstreamer helperhalibut_8.0.2halibut/8.0.28.0.2
Unfortunately, the bluez-alsa PCM plugin does not work correctly
when it is used through pipewire (or gstreamer, or anywhere really...).
For this reason I have built a helper client that uses GStreamer
to glue together the bluez-alsa sockets with pipewire.
This helper is implemented as a patch to bluez-alsa so that it can
use its internal private API. In the future this needs some re-thinking
The helper is meant to run in the background as a service and it will
create the appropriate streams in pipewire when it detects a new
device on the bluealsa d-bus interface. Currently it only supports
a2dp-sink and hfp modes (i.e. media player from a phone + calls).
Bluetooth speakers need further policy work in wireplumber that is
too complex to support on the current halibut version of
pipewire/wireplumber.
Bug-AGL: SPEC-2792
Change-Id: Ia0a0c4741dc6f28958e911436edde17ebde1a434
Signed-off-by: George Kiagiadakis <george.kiagiadakis@collabora.com>
Diffstat (limited to 'ATTIC/meta-audio-4a-framework/recipes-multimedia/4a-hal-device-config/4a-hal-vendor-config.bbexample')
0 files changed, 0 insertions, 0 deletions