| Summary: | media-sound/pulseaudio-15.0-r1: bluez5-gstreamer option status | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ivo Šmerek <ivo97> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ivo Šmerek
2021-10-11 19:23:53 UTC
(In reply to Ivo Šmerek from comment #0) > I noticed that bluez5-gstreamer option is currently disabled with a note > that ldacenc/rtpldacpay gst elements are not packaged yet. What exactly does > it mean for functionality? I tried to compile pulseaudio with this option > enabled and it compiled fine. Does it cause runtime problems? > > Is there any thread in Gentoo, gstreamer or somewhere else where I can watch > a progress on this? > > I'm asking because I was trying to get pulseaudio bluetooth codecs working > and ended up stuck here. > > References: > > https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/440 > > https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blob/master/ > meson_options.txt > > https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blob/master/src/ > modules/bluetooth/meson.build > > https://github.com/GStreamer/gstreamer/blob/ > e6d83d8f96569a2964a84f55ea6d98302ff5aaf9/subprojects/gst-plugins-bad/ > meson_options.txt#L88 > > Thank you in advance for your answer. There is no downside to enable bluez5-gstreamer, but that would be useless without required gstreamer plugins which are soon to be released in upcoming gstreamer 1.20 soon. If you want to experiment with this stuff, you can try e.g. this https://github.com/gentoo/gentoo/pull/21470 which should backport gstreamer ldac encoder plugin to 1.18.4, and then check it out with bluez5-gstreamer enabled in ebuild. https://gitweb.gentoo.org/repo/gentoo.git/commit/media-sound/pulseaudio?id=85c82141ff000919dd316476959da94d699a5215 *** This bug has been marked as a duplicate of bug 814488 *** |