From: mayhair <mayhair@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Use only libfreeaptx for Bluetooth audio
Date: Sat, 16 Sep 2023 08:18:21 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46080@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
New issue by mayhair on void-packages repository
https://github.com/void-linux/void-packages/issues/46080
Description:
<!--
if you are creating a bug report or package request, please fill out one of the forms here:
https://github.com/void-linux/void-packages/issues/new/choose
Don't request an update of a package, We have a script for that:
https://repo-default.voidlinux.org/void-updates/void-updates.txt
However, a quality pull request may help.
-->
There are two packages: `libopenaptx` and `libfreeaptx`, which allow the usage of the AptX audio codec for Bluetooth earbuds. The state of affairs is that `bluez-alsa` requires `libopenaptx`, while `libspa-bluetooth` (a part of the PipeWire project) requires `libfreeaptx`. However, both projects are virtually the same, so they can act as drop-in replacements for each other (presumably). `libfreeaptx` is a fork of `libopenaptx` which was made because `libopenaptx`'s author disallowed organisations such as FreeDesktop to contribute, believing them to violate the GPL licence. `libfreeaptx` is now preferred by the PipeWire project due to these lesser restrictions.
Is it possible that `bluez-alsa` can be configured to use `libfreeaptx` too, thus obsoleting the `libopenaptx` package?
next reply other threads:[~2023-09-16 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 6:18 mayhair [this message]
2023-09-16 8:13 ` [ISSUE] [CLOSED] Use only libfreeaptx for the AptX codec (common in Bluetooth audio) mayhair
2023-09-16 8:13 ` mayhair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46080@inbox.vuxu.org \
--to=mayhair@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).