20 stdenv.mkDerivation (finalAttrs: {
24 src = fetchFromGitHub {
27 rev = "v${finalAttrs.version}";
28 hash = "sha256-oGaYiSkOhqfjUl+mHTs3gqFcxli3cgkRtT6tbjy3ht0=";
47 ++ lib.optionals aacSupport [
52 (lib.enableFeature aacSupport "aac")
53 (lib.enableFeature true "hcitop")
54 (lib.enableFeature true "rfcomm")
55 (lib.withFeatureAs true "alsaplugindir" "${placeholder "out"}/lib/alsa-lib")
56 (lib.withFeatureAs true "dbusconfdir" "${placeholder "out"}/share/dbus-1/system.d")
59 passthru.updateScript = gitUpdater { };
62 homepage = "https://github.com/Arkq/bluez-alsa";
63 description = "Bluez 5 Bluetooth Audio ALSA Backend";
65 Bluez-ALSA (BlueALSA) is an ALSA backend for Bluez 5 audio interface.
66 Bluez-ALSA registers all Bluetooth devices with audio profiles in Bluez
67 under a virtual ALSA PCM device called `bluealsa` that supports both
70 Some backstory: Bluez 5 removed built-in support for ALSA in favor of a
71 generic interface for 3rd party appliations. Thereafter, PulseAudio
72 implemented a backend for that interface and became the only way to get
73 Bluetooth audio with Bluez 5. Users prefering ALSA stayed on Bluez 4.
74 However, Bluez 4 eventually became deprecated.
76 This package is a rebirth of a direct interface between ALSA and Bluez 5,
77 that, unlike PulseAudio, provides KISS near-metal-like experience. It is
78 not possible to run BluezALSA and PulseAudio Bluetooth at the same time
79 due to limitations in Bluez, but it is possible to run PulseAudio over
80 BluezALSA if you disable `bluetooth-discover` and `bluez5-discover`
81 modules in PA and configure it to play/capture sound over `bluealsa` PCM.
83 license = with lib.licenses; [ mit ];
84 mainProgram = "bluealsa";
85 maintainers = with lib.maintainers; [ oxij ];
86 platforms = lib.platforms.linux;