Did you do anything to get bluetooth working?
Nope, as soon as I installed pipewire-pulse and rebooted my Bluetooth all just worked. Although all 3 machines have basically teh same Bluetooth device as well, Intel AX200 w/ Bluetooth 5.0, although the one is AX201, the hardwareâs the same, just where the actual processing is taking place is different (on AX200 itâs on the card, on the AX201 itâs in the CPU).
My bluetooth is also working on the HP laptop.
I donât see why pipewire wouldnât be included as default to the next major endeavouros release. It looks pretty promising and so far I donât have issues with it.
Iâm such a trend setter ahahhahaha
Just as @tlmiller76 stated, when I installed pipewire-pulse you are forced to uninstall pulseaudio and pulseaudio-bluetooth.
Normal playback seems to work fine. I reinstalled blueberry for my XFCE system, but donât have anything to test it with.
pulseeffects version 5 also includes Pipewire support, and with lower latency than with Pulseaudio, so the reasons for keeping Pulseaudio around are rapidly diminishing.
I got bluetooth working by⌠Not using DeadBeef. DeadBeef was the problem.
I always hear about things I havenât known before. While itâs also true that I havenât been following the changes in Gnome development for a long time.
Thatâs okay then, the fact that it breaks mine isnât an issue as long as it works for TurkeyJohn.
Iâm happy to see progress, however, because I agree that pipewire should take over as soon as possible.
Jesus do I really want to get into thisâŚok I came from JACK to ALSA to Pulseaudio. I have done (no longer do) audio post production using a real time kernel, some custom A/D hardware yadayadaâŚI have sort of a critical ear and have a reasonably happy music system with Pulseaudio, Pulseeffects (which seems to have gotten better as it has aged) and still have a lot of LSP plugins installed. I have not run JACKD in probably 6 months. I find Linux dealing with audio is the most unmitigated bunch of complex garbage many times although JACK can be a save allâŚas can Pulse EffectsâŚwhere you dont have to rebuild the audio stack each time you start the machine (yeah scripting it can be done too). SoâŚwhats going to happen to those of us that do a fair amount of post processing to our music libraries âŚrock gets one set of presets, classic another, jazz another some to make up for living in a concrete box and trying to fill a room with near-field speakers (Pulseeffects can accomplish this)âŚI still occasionally dink around with post production so when the slathering herdâs foaming at the mouth finally results in the deprecation of Pulseaudio then what is someone like me âŚor for that matter those of you ranging from music production guys with a rack of $100 K A/D banks to recordâŚto those of us who want a little more punch on the lower end in the earbuds on the laptop -most music player EQâs are garbage, enough bass to sound good then its no longer tight and everything below 1 K is only 2 sliders with no way to change filter characteristics⌠Another desktop here with another similar but different distro (its not Arch and not EndavourâŚ) had a major update recently and it installed Pipewire. Also installed another version of Pulseefects with what was supposedly Pipewire Source and Sink pluginsâŚandâŚthere wasâŚnoâŚwayâŚto get Pipewire audio routed through Pulseeffects . I went to the Pipewire homepage, didnt find anything about routing assistance so I screwed around with things for a couple of hoursâŚI reinstalled the earlier version of Pulseeffects (which surprisingly uninstalled Pipewire ) and things are back to the way they wereâŚI am all about a change for the better in what passes for the audio stack in Linux to get rid of layer after layer after layer of obfuscation, enough to make a rock cryâŚquestion isâŚhow does one do routing with PipewireâŚthe" other which shall remain nameless distro would play audio straight from Audacious and from Fireweasel no problem but nothing I could do would cause the audio to go through the brand new custom version of Pulseeffects with the pipewire source and sink⌠Any assistance or recommendations would be very much appreciatedâŚ
Iâd recommend you start a thread with details about the problem youâre trying to solve. ![]()
Hey Jonathon
I can do that⌠thanks very much. Will doâŚ
Short answer I gave is pipe wire isnât better. Long answer you gave is pipe wire isnât better.
Hi LizziAS
Would appear that way wouldnt it. Another layer of obfuscation âŚanother brick in the wallâŚ
edit:-------well one then must ask tha questionâŚâwhy is it thereââŚâwhy is there PipewireââŚbut I wontâŚand even your cat agreesâŚ
I would add a âyetâ to the end of your sentence to really be accurate. If development continues, it most definitely WILL be betterâŚitâs just not there yet.
Hi tlmiller
âI would add a âyetâ to the end of your sentence to really be accurate.â
Completely agree.
What thought comes to my mind is I hope it doesnt become another sometimes needed half finished layer over all thats there already⌠Someone will need to write a decent routing program as well as compatibility for special effects, Audacity (and others), bluetooth, containers⌠Would be nice if Pipewire turns into a unified, somewhat monolithic audio server for Linux with lower latency than all of the layers we already contend with.
I guess you could apply this theory to Wayland too, itâs obviously not managing a lot of features that X takes for granted, right?
Some might argue that leaving spaces in text, and throwing in ellipses here and there to confuse people who might assume there has been an omission of one or more words that are obviously understood but that must be supplied to make a construction grammatically complete⌠is a more efficient approach to fitting a bunch of text into a small box.
Some things are based on great ideas, but need more work to be more competent than the things theyâre designed to replace.
My verdict - pipewire isnât there yet, for me.
Canât wait to use Pipewire and Wayland on GNU Hurd, to play Half-Life 3.
My answer is hopefully it gets better. 