Pipewire is one of the best pieces of software I used. It has a cool ass patchbay and unlike PulseAudio I've never had it crash on me. It is the best thing that happened to Linux audio
I was blown away when I connected my phone to my PC through Bluetooth and phone audio started playing through my PC. It just worked without me touching anything
I also really like how "Linux Studio Plugins" are standalone apps that you can run. I don't produce music or anything but I still use stuff like equalizers and spectrum analyzers. It is insane how flexible the "each app has inputs and outputs you can hook together" architecture is.
PulseAudio probably also had some of these features but I never used those because pulse would fall apart every time I touched it. Pipewire doesn't
Pipewire has some neat tricks that i use on a daily basis but i can also make it crash on demand so idk :p.
I have a restart script in my home directory for that exact reason.
It just does not like audio going out my gpu, together with video, through my receiver and into my tv.
Receiver not on while linux was booting? Guess what, pipewire reboot.
Tv goes off because of "inactivity"? Thats a pipewire reboot
... And yet i love pipewire haha. But ye, audio issues are still a thing
I also really like how "Linux Studio Plugins" are standalone apps that you can run. I don't produce music or anything but I still use stuff like equalizers and spectrum analyzers. It is insane how flexible the "each app has inputs and outputs you can hook together" architecture is.
It's weird that parts of this approach have been around for a long time, but barely anyone can make them all work together out of the box.
Mac has AU Lab that can host AU apps, i.e. Apple's analog of VST, and feed system audio through them. Plugging any app into another is a bit more involved, though: there was the open-source Sunflower made like fifteen years ago, but bit rot gotten it, and another open-source clone doesn't work for some reason either — so paid apps are the best recourse, just like on Windows iirc.
Mac also has a feature where one can combine multiple audio inputs into one virtual input. A funny application of this is, if you put the mic into a virtual input and call it ‘Rocksmith Something Something Controller’, you can play guitar with Rocksmith without their special usb device.
Next stop: iOS has an audio bus for connecting apps together just like VST/AU on the desktop (actually I think it's very same Audio Unit stuff). Android has jackshit, and if you feel that audio latency could be lower, it'll spit in your face.
Yes. The only times I've had any problem with pipewire were when pulse decided to run for some reason and disrupted everything.
Also, I can open a pipewire device, write data there, and not run into C assert faults. I can do this with oss and alsa too, of course, but AFAIK, it's impossible with pulse and all the Linux DEs ran on pure magic for a decade.
It has a tendency to break my USB audio after updating the kernel. I just have to remember the incantation to restart it though and it seems to fix it.
It's ironic how, just like people make jokes of Linux audio even though it's been stable for years, people stil joke about Windows throwing BSODs or requiring reinstalls non-stop, even though the last BSOD I had that wasn't caused by faulty hardware or a weird one-of-a-kind driver issue was... 12 years ago? Something like that.
"Latest" as in "Insider"? I'm on the first Patch Ring at work, so I'm one of the five people who get the latest patches, but we're not Insiders. We had 3 BSODs last week when MediaTek fucked up their WiFi drivers and the devices crashed if connected to WiFi 7.
The previous BSOD I saw at work was 3 years ago. The tech came in, replaced the MOBO and the issue was solved.
A colleague of mine had a BSOD while we were doing our stand-up, and I have had a few over the last few years.
Also, you don't get to tell us that BSODs don't count if the driver is written by someone else, that's not how it works. Otherwise Linux has no audio problem, only alsa does. Completely different thing.
I have a strange Dual Screen Asus on Intel with mobile arc. About 10% of the time, waking from sleep will crash the taskbar, something about the video driver not being ready yet.
I just wrote a daemon to kick plasmashell in the ass if it notices the bar isn't there.
Systemd haters when you use systemd instead of UltraXinitializer made in 2005 by John Init in C-- that requires you to manually write init scripts and has 894 critical severity CVEs
I 'member having to use a script to do software mixing of multiple audio streams in alsa, so I could listen to a music CD while playing WOW. Otherwise whichever thing started first would grab the audio device and the other thing couldn't use it. This would've been back in like 2006-7.
You must have been blessed by the hardware gods. I had several scripts bound to hotkeys to fix various issues that would occur regularly and this was only 5 or so years ago. Volume would reset, wrong sink would get selected, it would crash, it would crackle, it had bad latency but most of the time it was fine.
My first experience with switching to Linux a few years ago was on an outdated, at the time, ~$400 HP laptop. Switching from Windows 10 to EndeavourOS, and everything just worked, including audio.
In fact, it still works great whenever I turn it on like a few times a year.
hp victus16 is working fine with wireplumber. never buy hp because the anti customer practices, terrible build quality and supporting israel with hardware.
Driver support is non-existent. Audio via the speakers worked but no volume control, Bluetooth, thunderbolt, mic etc didn't work. Even the headphone socket didn't work.
Shit even the gpu (AMD) didn't work properly. Despite being a 5k panel resolution is stuck at 4k.
Sigh. Would have been a great Linux box if I could have gotten it to work
Many hardware companies have the same problem, they can output some decent hardware, but some other series are true lemons (especially for Linux/Unix, but for a lesser extent, for that other system as well). And beforehand, it's not always easy to know which is which. It's a common issue with laptop makers where the hardware is often more esoteric.
the bluetooth pipewire pulseaudio mix could be a bit better.
It's gotten to the point that my bluetooth headphones will not connect to my laptop because I don't currently have any media playing.
Load up a youtube video, the audio device springs into life, offers it up as pulseaudio source, who signals to bluez that there is a valid audio profile and suddenly everything connects.
From an efficiency standpoint, yes I get it. From a UX standpoint... please just let my earphones connect when I enable bluetooth from the get go
Gotta be real here for a moment, the last time I had any sort of trouble with audio on Linux was back in the day when I was still fiddling about with Gentoo. But that was, what, fifteen, twenty years ago?
I have a terrible confession: i have loads of audio issues im dealing with atm. My desktop setup basically gets confused and stops working whenever i try to switch fom headphones to speaker, and my two laptops just do not want to pair with my bluetooth headphones unless i futz with bluetoothctl every time
Anyway, tangent aside. my terrible confession is that i go to linuxmemes for tech support, someone pls help
I have been using Arch daily for 13+ years and I still don't have a proper grasp on audio and Bluetooth..
Used raw ALSA, JACK, PulseAudio, and now Pipewire. I had major issues with all of them except ALSA.
I managed to disable devices like my webcam mic and PS5 mic, and even added a noise reduction filter to my real mic that shows up as it's own device, but..
Only because the Arch wiki told me specifically how to do those things. Audio just luckily seems to work fine for the most part, currently. I used qpwgraph to play with wireplumber and it's obviously very powerful, but I have no idea how it works :D
Bluetooth is a different story, it seems to work differently on every single device I've worked on..
I've had a bunch of audio issues crop up for me as well, after upgrading to Pop 24.04 and the new cosmic DE. I used to have keyboard shortcuts that would reliabily switch from headphones to speakers, but those are hit or miss now. And when they miss, I have to go all the way into into alsamixer and unmute things until it works again. Which begs the question, why can't the normal audio settings UI do everything alsamixer can? Alsamixer isn't complicated, by any stretch. Literally just lets you adjust the volume of all the things on a particular audio card, and mute/unmute.
I have linux issues every time I have a "new" machine, and it makes sense. Linux is a volunteer/ opensource project. It isn't getting chipsets before, and building drivers in advance of hardware releases (at least it mostly isn't; I understand that some times it does).
Because of that, the newer your harder, the crappier it works. The longer your hardware has been around, in-general, my experience is that Linux becomes an "it just works experience".
I built a new 9950x3d + x870e system last year. trying to use the motherboard's wifi would kernel panic things. couldnt turn bluetooth on and off. couldn't control the RGB.
Now, WiFi works great. Bluetooth works great. OpenRGB supports the RGB. Things are great. Took time to get here, but we got here.
The strong irony is that when high core count and asymmetrical multi-CCD chips started rolling out, they were having CCD pinning issues in windows. But since Linux has a scheduler that has been NUMA awareness for ages... Linux was actually just fine with these things.
Linux was actually better for bleeding edge hardware for once.
I use ethernet for everything, so even now I don't use WiFi. I only figured out it worked because my internet was out a few months later and needed to connect to a hotspot, and was pleasantly surprised that it was not crashing. I also don't really mess with RGB or bluetooth, so I cant really comment on those either. The motherboard itself always worked, it was just the integrated chips (it was new wifi 7 chip) that I wasn't actually using anyway. It may have been fixed in days, weeks... who knows, I wasnt testing it.
tl;dr - sorry, I don't have a good answer. The board always "worked" for my use case.
Nah. I'm just gonna hope distros once the paper I'm submitting is accepted and I don't need this machine again. I think I'm going to go fedora so I can stay closer to bleeding edge on the kernel.
I definitely remember having to futz with audio a looooong time ago, but honestly getting xf86config to work with my video card and monitor was much more difficult.
I think I managed to skip the ndiswrapper era. I was using Ethernet on desktops and my laptops were Macs. Nowadays my desktop has both wifi and Ethernet, and my laptops run Linux but nmtui just works.
Ive not been using Linux for long, maybe only 5 years or so. But I've never had any audio issues.
My audio needs are not as straightforward as the average user. I play drums over midi into reaper. I have used guitars and mics through my audio interface. My midi controllers work without any issues.
Im using pipewire and running reaper with pipewire-jack. I've used mint for years with no issues, and now running debian Trixie with no issues.
It's mostly an old notion that just won't die. Especially in the years after its initial release (2004) it was just a disastrous experience sometimes with cracking noises, misconfigured sinks (or outright missing), crashes and - if I still remember one of my first Linux experiences with Ubuntu 8.04 right - the sudden decision to repeat the current audio buffer at maximum volume.
Ever since I came back to Linux on Desktop around 2017 I didn't had any bigger issues with Pulse either. Ever since Pipewire became the default stuff just works, no issues whatsoever.
Linux user for 20 years: in my days I has to compile X by hand if I wanted a graphic interface.
Linux users for 10 years: kinda worked, sometimes you had to install the same a couple of times with different configurations until one worked for you.
Linux user for 5 years: lmao, this easier than windows.
You know, I don't get this joke. I have been using Linux and BSD since 2019, and the only incident I ever had was with sndio(7), and that was because I decided to switch to the -current branch of OpenBSD without heeding the warnings.
Apart from that, whether I was using ALSA, PulseAudio, PipeWire, JACK, or OSS (on FreeBSD), I always had a perfect experience.
Oh. To be fair, the PulseAudio days started off REALLY shit and JACK/ALSA had the limitations of "locking" an audio device to a specific process/application, so it used to be much rougher.
Ever since pipewire came along, it's been really solid.
Apart from the occasional 100% VOLUME Noise Bang that I get into my Headphones (disregarding the volume I have set), pipewire works pretty well, consistently.
Just had a random occurance of pipewire not allowing me to switch my audio back to my headphones (played some music through speakers before) through the settings. Had to switch it using the terminal but then it worked. Took about 10 minutes to figure out
Yeah, this and a bunch of nearsighted VST developers are the only things keeping me from switching to Linux entirely anymore. Things have definitely gotten better on the Linux side of things, and definitely gotten worse with Windows, so I feel like it's only a matter of time.
After a pipewire update I can half-reliably trigger a segfault of wireplumber with opening or closing lid of my laptop in specific way. I presume it's hardware issue, though
I've been using "Linux audio", namely jack, Ardour, freewheeling, hydrogen e.a. for more than a decade. But you can take your shiny pipewire and shove it where the sun doesn't shine.
Pipewire is awesome, I can't believe they did it, they implemented all the old APIs for the other system and brought it into great harmony. But hey I'm a wayland user too
A decade ago, all distributions switched to a new sound stack that is better by all metrics. He is saying he is old and knows the name of the old stuff, therefore new stuff bad
The pipewire switch happened far more recently than a decade ago, you may be thinking of pulseaudio, which had far more valid criticisms than pipewire does now.
You're an idiot who doesn't know what you're talking about. Pipewire isn't really up for production (and by far not a decade old) and whoever decided to activate it by default might have had easy desktop use and switching to BT or mobile audio trash in mind. If it comes to latency, low complexity or reliability, pipewire is terrible. It also doesn't add anything useful that jack could not do, it only adds complexity where it's not needed.
PW is nice, if you're a newbie and want all your crappy BT shit to connect from the desktop so you can watch five tik-tok vids at the same time using you shiny "soundbar" (and have your voice comm blasting the neighbourhood), but it's a mess if you want to use realtime audio with more than two ports, MIDI and a device chain for recording or playback.
Don't matter replying, "Qwel", I put you in my special place for trolling, abusive children who do not contibute to civilization - the killfile.
seems to me like you're the troll. people who are advanced enough to want to use MIDI controllers and whatnot are advanced enough to just silently use the tools that work for them
Not strictly an issue in that sense, but I am a musician that heavily uses software monitoring for guitars and vocals, meaning I rely on the lowest latency possible to play back the input.
Pipewire just isn't quite there on the performance level of jack, but I also use realtime kernels and CPU governors to further reduce latency issues, so this is an extreme use case.
While the guy you replied to seens a bit unhinged, I have to agree that pipewire isn't the holy grail some people make it out to be, but I guess it's a better solution than pulse audio for 99% of general users.
I don't know much about "bluetooth instruments", the question is what's meant by that, exactly. There are wireless units for mics and guitars, but they are usually connected to an amp directly, so there is only one way transmission, which may be fine with a bit of latency.
When you use your computer as a digital amp/effects processor, you get a roundtip latency, e.g. from the input into a AD converter, to digital processing and back through a DA into the speakers.
That means you basically have doubled the internal latency and the more effects you use in parallel, the tighter the timings have to be.
With jack on an optimised system, I get anything between 4-8ms of total latency. Anything below 20ms is generally considered "fine", but you can hear it, depending on your subjective brain and ears. I would say I notice anything above 10ms already, but I've played with 16+ when I started and it worked for pracitsing.
119 Comments
yogurtwrong@lemmy.world · 160 pts · 166d
okay here me out:
Pipewire is one of the best pieces of software I used. It has a cool ass patchbay and unlike PulseAudio I've never had it crash on me. It is the best thing that happened to Linux audio
I was blown away when I connected my phone to my PC through Bluetooth and phone audio started playing through my PC. It just worked without me touching anything
I also really like how "Linux Studio Plugins" are standalone apps that you can run. I don't produce music or anything but I still use stuff like equalizers and spectrum analyzers. It is insane how flexible the "each app has inputs and outputs you can hook together" architecture is.
PulseAudio probably also had some of these features but I never used those because pulse would fall apart every time I touched it. Pipewire doesn't
Broken Linux audio is about to become old news
creed10@lemmy.world · 72 pts · 166d
i don't know about you but broken Linux audio has BEEN old news ever since i started using pipewire
DacoTaco@lemmy.world · 20 pts · 166d
Pipewire has some neat tricks that i use on a daily basis but i can also make it crash on demand so idk :p. I have a restart script in my home directory for that exact reason.
It just does not like audio going out my gpu, together with video, through my receiver and into my tv.
Receiver not on while linux was booting? Guess what, pipewire reboot. Tv goes off because of "inactivity"? Thats a pipewire reboot
... And yet i love pipewire haha. But ye, audio issues are still a thing
DaTingGoBrrr@lemmy.ml · 6 pts · 166d
Have you reported the crashing issue to the developers of pipewire?
DacoTaco@lemmy.world · 5 pts · 166d
Not yet. Ive been too busy tbh. I assume that, like many linux tools, its a bitch to report something. Not just a easy bug tracker or something
DaTingGoBrrr@lemmy.ml · 5 pts · 166d
From what I found this is their official bug tracker
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues
hzl@piefed.blahaj.zone · 3 pts · 166d
How is the latency on Pipewire? Have you tried using it for instruments at all?
SlurpingPus@lemmy.world · 9 pts · 166d
It's weird that parts of this approach have been around for a long time, but barely anyone can make them all work together out of the box.
Mac has AU Lab that can host AU apps, i.e. Apple's analog of VST, and feed system audio through them. Plugging any app into another is a bit more involved, though: there was the open-source Sunflower made like fifteen years ago, but bit rot gotten it, and another open-source clone doesn't work for some reason either — so paid apps are the best recourse, just like on Windows iirc.
Mac also has a feature where one can combine multiple audio inputs into one virtual input. A funny application of this is, if you put the mic into a virtual input and call it ‘Rocksmith Something Something Controller’, you can play guitar with Rocksmith without their special usb device.
Next stop: iOS has an audio bus for connecting apps together just like VST/AU on the desktop (actually I think it's very same Audio Unit stuff). Android has jackshit, and if you feel that audio latency could be lower, it'll spit in your face.
marcos@lemmy.world · 5 pts · 166d
Yes. The only times I've had any problem with pipewire were when pulse decided to run for some reason and disrupted everything.
Also, I can open a pipewire device, write data there, and not run into C assert faults. I can do this with oss and alsa too, of course, but AFAIK, it's impossible with pulse and all the Linux DEs ran on pure magic for a decade.
tempest@lemmy.ca · 3 pts · 166d
It has a tendency to break my USB audio after updating the kernel. I just have to remember the incantation to restart it though and it seems to fix it.
reddit_sux@lemmy.world · 1 pts · 164d
You can put it in a script.
AVengefulAxolotl@lemmy.world · 2 pts · 166d
Easy Effects is such a great app. I like a little bit more bass on my music, and it has presets for that as well!
Samskara@sh.itjust.works · 1 pts · 153d
JamesDSP does most of what Easyeffects does with lower performance penalties.
LodeMike@lemmy.today · 1 pts · 166d
Have you gotten any amount of stable behavior when two users are logged in?
LodeMike@lemmy.today · 99 pts · 166d
Oh no not
systemctl --user restart pipewire.service!Sp00kyB00k@lemmy.world · 43 pts · 166d
Pfff why not the sudo reboot now. That's much better /s
rImITywR@lemmy.world · 30 pts · 166d
May as well just reinstall the os at this point.
Zwiebel@feddit.org · 15 pts · 166d
Windows habit
Alaknar@sopuli.xyz · 5 pts · 166d
It's ironic how, just like people make jokes of Linux audio even though it's been stable for years, people stil joke about Windows throwing BSODs or requiring reinstalls non-stop, even though the last BSOD I had that wasn't caused by faulty hardware or a weird one-of-a-kind driver issue was... 12 years ago? Something like that.
baguettefish@discuss.tchncs.de · 3 pts · 166d
if you've been running the latest windows 11 that's very good luck
Alaknar@sopuli.xyz · 1 pts · 166d
"Latest" as in "Insider"? I'm on the first Patch Ring at work, so I'm one of the five people who get the latest patches, but we're not Insiders. We had 3 BSODs last week when MediaTek fucked up their WiFi drivers and the devices crashed if connected to WiFi 7.
The previous BSOD I saw at work was 3 years ago. The tech came in, replaced the MOBO and the issue was solved.
Miaou@jlai.lu · 2 pts · 166d
A colleague of mine had a BSOD while we were doing our stand-up, and I have had a few over the last few years.
Also, you don't get to tell us that BSODs don't count if the driver is written by someone else, that's not how it works. Otherwise Linux has no audio problem, only alsa does. Completely different thing.
IDK why you're shilling for them honestly
rumba@lemmy.zip · 4 pts · 166d
I have a strange Dual Screen Asus on Intel with mobile arc. About 10% of the time, waking from sleep will crash the taskbar, something about the video driver not being ready yet.
I just wrote a daemon to kick plasmashell in the ass if it notices the bar isn't there.
frankenswine@lemmy.world · -14 pts · 166d
ewwwwww SystemD
ChilledPeppers@lemmy.dbzer0.com · 27 pts · 166d
No, eww is eww. Systemd is systemd.
Xylight@lemdro.id · 23 pts · 166d
Systemd haters when you use systemd instead of UltraXinitializer made in 2005 by John Init in C-- that requires you to manually write init scripts and has 894 critical severity CVEs
Liketearsinrain@lemmy.ml · 8 pts · 166d
frankenswine@lemmy.world · 0 pts · 165d
SyStEmD iS tHe OnLy InIt SyStEm BeCaUsE wE kNoW nO aLtErNaTiVeS
i use GNU Shepherd btw, thanks for asking (:
now go back writing text files for services and pray for them to werk like the cave people you are
ZombieCyborgFromOuterSpace@piefed.ca · 4 pts · 166d
I got your System "D" right here \*grabs crotch\*
Outsider9042@lemmy.world · 47 pts · 166d
Been around since OSS and ALSA was the new kid on the block. Yet to experience these supposed sound issues.
tiramichu@sh.itjust.works · 18 pts · 166d
All i can say is, you have been a very lucky individual.
FishFace@piefed.social · 11 pts · 166d
Then you didn't use your computer for much involving audio.
imsufferableninja@sh.itjust.works · 6 pts · 166d
I 'member having to use a script to do software mixing of multiple audio streams in alsa, so I could listen to a music CD while playing WOW. Otherwise whichever thing started first would grab the audio device and the other thing couldn't use it. This would've been back in like 2006-7.
Fizz@lemmy.nz · 5 pts · 166d
You must have been blessed by the hardware gods. I had several scripts bound to hotkeys to fix various issues that would occur regularly and this was only 5 or so years ago. Volume would reset, wrong sink would get selected, it would crash, it would crackle, it had bad latency but most of the time it was fine.
Trail@lemmy.world · 2 pts · 166d
Yeah I am also running linux for 20 years or so. Minor hiccups here and there, but sound has been solid generally.
rumba@lemmy.zip · 1 pts · 166d
Same, I have it running on several different laptops/desktops, it's probably a certain piece of hardware.
I'm sure it's happening to people, just not everyone.
Strawberry@lemmy.blahaj.zone · 39 pts · 166d
Never buy an HP laptop for linux. They often try to have some gimmicky special audio hardware with terrible driver support
pewpew@feddit.it · 10 pts · 165d
Never buy anything HP
prole@lemmy.blahaj.zone · 6 pts · 165d
My first experience with switching to Linux a few years ago was on an outdated, at the time, ~$400 HP laptop. Switching from Windows 10 to EndeavourOS, and everything just worked, including audio.
In fact, it still works great whenever I turn it on like a few times a year.
rektstarsceosu@lemmy.zip · 5 pts · 166d
hp victus16 is working fine with wireplumber. never buy hp because the anti customer practices, terrible build quality and supporting israel with hardware.
how_we_burned@lemmy.zip · 3 pts · 165d
Same with any Apple Intel based iMac
Driver support is non-existent. Audio via the speakers worked but no volume control, Bluetooth, thunderbolt, mic etc didn't work. Even the headphone socket didn't work.
Shit even the gpu (AMD) didn't work properly. Despite being a 5k panel resolution is stuck at 4k.
Sigh. Would have been a great Linux box if I could have gotten it to work
Edit
ptu@sopuli.xyz · 2 pts · 165d
Which distro did you use? Or is it the same for all?
how_we_burned@lemmy.zip · 1 pts · 164d
Arch
AnUnusualRelic@lemmy.world · 2 pts · 165d
Many hardware companies have the same problem, they can output some decent hardware, but some other series are true lemons (especially for Linux/Unix, but for a lesser extent, for that other system as well). And beforehand, it's not always easy to know which is which. It's a common issue with laptop makers where the hardware is often more esoteric.
Wizard_Pope@lemmy.world · 1 pts · 165d
My elitebook 840 works fine on linux
texture@lemmy.world · 1 pts · 165d
ty, noted.
ColdWater@lemmy.ca · 31 pts · 166d
Strange I never had any problems with PW, for me it's probably the most reliable Linux software there is
tetris11@feddit.uk · 6 pts · 165d
the bluetooth pipewire pulseaudio mix could be a bit better.
It's gotten to the point that my bluetooth headphones will not connect to my laptop because I don't currently have any media playing.
Load up a youtube video, the audio device springs into life, offers it up as pulseaudio source, who signals to bluez that there is a valid audio profile and suddenly everything connects.
From an efficiency standpoint, yes I get it. From a UX standpoint... please just let my earphones connect when I enable bluetooth from the get go
Electricd@lemmybefree.net · 2 pts · 166d
Had to change the quantum because I had audio "cracks"/bug sounds, cutting audio..
Shipgirlboy@sh.itjust.works · 30 pts · 166d
Gotta be real here for a moment, the last time I had any sort of trouble with audio on Linux was back in the day when I was still fiddling about with Gentoo. But that was, what, fifteen, twenty years ago?
orenj@lemmy.sdf.org · 26 pts · 166d
I have a terrible confession: i have loads of audio issues im dealing with atm. My desktop setup basically gets confused and stops working whenever i try to switch fom headphones to speaker, and my two laptops just do not want to pair with my bluetooth headphones unless i futz with bluetoothctl every time
Anyway, tangent aside. my terrible confession is that i go to linuxmemes for tech support, someone pls help
driving_crooner@lemmy.eco.br · 10 pts · 166d
Try to use a normal computer instead of trying to kick linux into a ATM.
FellowHuman@lemmy.world · 10 pts · 166d
Most ATMs are acually now linux based,. Weeell the new ones anyway. Old ones are still running on XP.
myrrh@ttrpg.network · 2 pts · 165d
AnUnusualRelic@lemmy.world · 1 pts · 165d
It used to be, but that was a long time ago.
Diurnambule@jlai.lu · 1 pts · 166d
Dépend of thé country, Saw some are on windows 10. I guess windows 11 is too unstable yet.
Ricaz@lemmy.dbzer0.com · 4 pts · 166d
Do you write in a French accent?
Diurnambule@jlai.lu · 1 pts · 165d
Yep
purplemonkeymad@programming.dev · 1 pts · 166d
Not sure, xp might be too new. I've definitely seen nt 4 on an ATM before.
Ricaz@lemmy.dbzer0.com · 6 pts · 166d
I have been using Arch daily for 13+ years and I still don't have a proper grasp on audio and Bluetooth..
Used raw ALSA, JACK, PulseAudio, and now Pipewire. I had major issues with all of them except ALSA.
I managed to disable devices like my webcam mic and PS5 mic, and even added a noise reduction filter to my real mic that shows up as it's own device, but..
Only because the Arch wiki told me specifically how to do those things. Audio just luckily seems to work fine for the most part, currently. I used qpwgraph to play with wireplumber and it's obviously very powerful, but I have no idea how it works :D
Bluetooth is a different story, it seems to work differently on every single device I've worked on..
zalgotext@sh.itjust.works · 1 pts · 165d
I've had a bunch of audio issues crop up for me as well, after upgrading to Pop 24.04 and the new cosmic DE. I used to have keyboard shortcuts that would reliabily switch from headphones to speakers, but those are hit or miss now. And when they miss, I have to go all the way into into alsamixer and unmute things until it works again. Which begs the question, why can't the normal audio settings UI do everything alsamixer can? Alsamixer isn't complicated, by any stretch. Literally just lets you adjust the volume of all the things on a particular audio card, and mute/unmute.
Reygle@lemmy.world · 17 pts · 165d
I'm going to tempt fate here, you ready?
This hasn't happened to me since pulseaudio
texture@lemmy.world · 3 pts · 165d
exactly this
TropicalDingdong@lemmy.world · 16 pts · 166d
Why is my Bluetooth stuttering
youCanCallMeDragon@lemmy.world · 9 pts · 166d
Yours too?
TropicalDingdong@lemmy.world · 16 pts · 166d
I have linux issues every time I have a "new" machine, and it makes sense. Linux is a volunteer/ opensource project. It isn't getting chipsets before, and building drivers in advance of hardware releases (at least it mostly isn't; I understand that some times it does).
Because of that, the newer your harder, the crappier it works. The longer your hardware has been around, in-general, my experience is that Linux becomes an "it just works experience".
Also, fuck you mediatek 7925e.
bisby@lemmy.world · 13 pts · 166d
I built a new 9950x3d + x870e system last year. trying to use the motherboard's wifi would kernel panic things. couldnt turn bluetooth on and off. couldn't control the RGB.
Now, WiFi works great. Bluetooth works great. OpenRGB supports the RGB. Things are great. Took time to get here, but we got here.
TropicalDingdong@lemmy.world · 6 pts · 166d
🤤
bisby@lemmy.world · 6 pts · 166d
The strong irony is that when high core count and asymmetrical multi-CCD chips started rolling out, they were having CCD pinning issues in windows. But since Linux has a scheduler that has been NUMA awareness for ages... Linux was actually just fine with these things.
Linux was actually better for bleeding edge hardware for once.
Samskara@sh.itjust.works · 1 pts · 153d
How long did it take to work?
bisby@lemmy.world · 2 pts · 153d
I use ethernet for everything, so even now I don't use WiFi. I only figured out it worked because my internet was out a few months later and needed to connect to a hotspot, and was pleasantly surprised that it was not crashing. I also don't really mess with RGB or bluetooth, so I cant really comment on those either. The motherboard itself always worked, it was just the integrated chips (it was new wifi 7 chip) that I wasn't actually using anyway. It may have been fixed in days, weeks... who knows, I wasnt testing it.
tl;dr - sorry, I don't have a good answer. The board always "worked" for my use case.
cenzorrll@piefed.ca · 6 pts · 166d
Try changing the audio codec in the hardware profile.
rumba@lemmy.zip · 3 pts · 166d
try disabling bluetooth power saving
try libspa-bluetooth if pipewire
force A2DB profile in pavucontrol or blueman
make sure you have bluez and bluez-utils?
TropicalDingdong@lemmy.world · 2 pts · 166d
Nah. I'm just gonna hope distros once the paper I'm submitting is accepted and I don't need this machine again. I think I'm going to go fedora so I can stay closer to bleeding edge on the kernel.
Ricaz@lemmy.dbzer0.com · 0 pts · 166d
Just use Arch or a derivative like CachyOS, it's not as scary as you might think
Samskara@sh.itjust.works · 1 pts · 153d
More likely to have broken things though. I‘d recommend an Ubuntu LTS distro for issues like this.
PabloSexcrowbar@piefed.social · 3 pts · 166d
Because it's nervous and under a lot of pressure. Go easy on it.
Samskara@sh.itjust.works · 0 pts · 153d
That can have several reasons. Workarounds typically are:
Find out what Bluetooth or wifi chipset you have. Then research and try various things.
b_tr3e@feddit.org · 0 pts · 166d
That's the best thing bluetooth audio can do for you. Much better than anything it does to music.
BartyDeCanter@lemmy.sdf.org · 13 pts · 166d
I definitely remember having to futz with audio a looooong time ago, but honestly getting xf86config to work with my video card and monitor was much more difficult.
chronicledmonocle@lemmy.world · 12 pts · 166d
The dark days of fucking with xorg.conf files and ndiswrapper to get WiFi working are things I'm glad no longer exist.
BartyDeCanter@lemmy.sdf.org · 2 pts · 166d
I think I managed to skip the ndiswrapper era. I was using Ethernet on desktops and my laptops were Macs. Nowadays my desktop has both wifi and Ethernet, and my laptops run Linux but nmtui just works.
Ricaz@lemmy.dbzer0.com · 1 pts · 166d
I fucked with Xorg literally yesterday to get my display working
Paulemeister@feddit.org · 12 pts · 165d
Configuring pipewire or pulseaudio is dark magic
Frenchgeek@lemmy.ml · 4 pts · 165d
I have a python script that take screenshots using pipewire so, I concur...
TimeSquirrel@kbin.melroy.org · 12 pts · 166d
https://media.tenor.com/Va9M6DvKygYAAAAM/ba-dum-tsss-drum.gif
meekah@discuss.tchncs.de · 8 pts · 166d
Pro tip: putting the URL in the following character sequence will just show the image in your comment instead of the URL
you can also add a description, mostly useful for accesibility (screen readers for e.g. sight impaired people):
FauxLiving@lemmy.world · 3 pts · 166d
Another tip: Be careful linking images from hosts that you don't control.
You don't want to come back and find your funny.gif picture is now displaying a goatse.
AndyMFK@lemmy.dbzer0.com · 12 pts · 166d
Ive not been using Linux for long, maybe only 5 years or so. But I've never had any audio issues.
My audio needs are not as straightforward as the average user. I play drums over midi into reaper. I have used guitars and mics through my audio interface. My midi controllers work without any issues.
Im using pipewire and running reaper with pipewire-jack. I've used mint for years with no issues, and now running debian Trixie with no issues.
Natanox@discuss.tchncs.de · 6 pts · 166d
It's mostly an old notion that just won't die. Especially in the years after its initial release (2004) it was just a disastrous experience sometimes with cracking noises, misconfigured sinks (or outright missing), crashes and - if I still remember one of my first Linux experiences with Ubuntu 8.04 right - the sudden decision to repeat the current audio buffer at maximum volume.
Ever since I came back to Linux on Desktop around 2017 I didn't had any bigger issues with Pulse either. Ever since Pipewire became the default stuff just works, no issues whatsoever.
driving_crooner@lemmy.eco.br · 3 pts · 166d
Linux user for 20 years: in my days I has to compile X by hand if I wanted a graphic interface.
Linux users for 10 years: kinda worked, sometimes you had to install the same a couple of times with different configurations until one worked for you.
Linux user for 5 years: lmao, this easier than windows.
HuntressHimbo@lemmy.zip · 8 pts · 166d
Flashbacks to having
pavucontrolopen, editingdefault.paand watching pulse crash over and over trying to get echo cancelling workinghellfire103@lemmy.ca · 4 pts · 166d
You know, I don't get this joke. I have been using Linux and BSD since 2019, and the only incident I ever had was with
sndio(7), and that was because I decided to switch to the-currentbranch of OpenBSD without heeding the warnings.Apart from that, whether I was using ALSA, PulseAudio, PipeWire, JACK, or OSS (on FreeBSD), I always had a perfect experience.
chronicledmonocle@lemmy.world · 3 pts · 166d
The joke is they can't hear them because their audio broke. You're overthinking it. Lol.
hellfire103@lemmy.ca · 2 pts · 165d
No, that bit's funny. I mean the running joke about Linux audio being bad.
chronicledmonocle@lemmy.world · 2 pts · 165d
Oh. To be fair, the PulseAudio days started off REALLY shit and JACK/ALSA had the limitations of "locking" an audio device to a specific process/application, so it used to be much rougher.
Ever since pipewire came along, it's been really solid.
ulterno@programming.dev · 2 pts · 164d
Apart from the occasional 100% VOLUME Noise Bang that I get into my Headphones (disregarding the volume I have set), pipewire works pretty well, consistently.
cows_are_underrated@feddit.org · 2 pts · 166d
Just had a random occurance of pipewire not allowing me to switch my audio back to my headphones (played some music through speakers before) through the settings. Had to switch it using the terminal but then it worked. Took about 10 minutes to figure out
sundaymidnight@lemmy.world · 2 pts · 166d
what is Pipeware? only install other thing, Linux is rich of alternatives (you don't have to cry for convincing to MS/Apple)
half_built_pyramids@lemmy.world · 2 pts · 165d
My god, there's so many comments
Now run it on a pi zero
Underwaterbob@sh.itjust.works · 1 pts · 166d
Yeah, this and a bunch of nearsighted VST developers are the only things keeping me from switching to Linux entirely anymore. Things have definitely gotten better on the Linux side of things, and definitely gotten worse with Windows, so I feel like it's only a matter of time.
arcine@jlai.lu · 1 pts · 139d
I've never had audio problems on Linux. Wtf are you guys doing x)
Kierunkowy74@piefed.social · 1 pts · 139d
After a pipewire update I can half-reliably trigger a segfault of wireplumber with opening or closing lid of my laptop in specific way. I presume it's hardware issue, though
b_tr3e@feddit.org · -3 pts · 166d
I've been using "Linux audio", namely jack, Ardour, freewheeling, hydrogen e.a. for more than a decade. But you can take your shiny pipewire and shove it where the sun doesn't shine.
lung@lemmy.world · 24 pts · 166d
Pipewire is awesome, I can't believe they did it, they implemented all the old APIs for the other system and brought it into great harmony. But hey I'm a wayland user too
rumba@lemmy.zip · 4 pts · 166d
WAYYYYLANDDDDDD SHAKES FIST IN AUTOHOTKEY
WhyIHateTheInternet@lemmy.world · 9 pts · 166d
I understand a couple of those words!
Qwel@sopuli.xyz · 31 pts · 166d
A decade ago, all distributions switched to a new sound stack that is better by all metrics. He is saying he is old and knows the name of the old stuff, therefore new stuff bad
aBundleOfFerrets@sh.itjust.works · 21 pts · 166d
The pipewire switch happened far more recently than a decade ago, you may be thinking of pulseaudio, which had far more valid criticisms than pipewire does now.
Qwel@sopuli.xyz · 3 pts · 166d
Oh. In my head both had happened in close succession
b_tr3e@feddit.org · -29 pts · 166d
You're an idiot who doesn't know what you're talking about. Pipewire isn't really up for production (and by far not a decade old) and whoever decided to activate it by default might have had easy desktop use and switching to BT or mobile audio trash in mind. If it comes to latency, low complexity or reliability, pipewire is terrible. It also doesn't add anything useful that jack could not do, it only adds complexity where it's not needed.
PW is nice, if you're a newbie and want all your crappy BT shit to connect from the desktop so you can watch five tik-tok vids at the same time using you shiny "soundbar" (and have your voice comm blasting the neighbourhood), but it's a mess if you want to use realtime audio with more than two ports, MIDI and a device chain for recording or playback.
Don't matter replying, "Qwel", I put you in my special place for trolling, abusive children who do not contibute to civilization - the killfile.
civ@lemmy.civl.cc · 15 pts · 166d
Sir, this is a Wendy's
creed10@lemmy.world · 15 pts · 166d
seems to me like you're the troll. people who are advanced enough to want to use MIDI controllers and whatnot are advanced enough to just silently use the tools that work for them
b_tr3e@feddit.org · -16 pts · 166d
Say hello to Mr Killfile...
extremeboredom@lemmy.world · 1 pts · 166d
Qwel@sopuli.xyz · 10 pts · 166d
I do, in fact, not know what I am talking about. Is there actually some sound engineers or musicians that are having real-life issues with it ?
ExtremeUnicorn@feddit.org · 4 pts · 166d
Not strictly an issue in that sense, but I am a musician that heavily uses software monitoring for guitars and vocals, meaning I rely on the lowest latency possible to play back the input.
Pipewire just isn't quite there on the performance level of jack, but I also use realtime kernels and CPU governors to further reduce latency issues, so this is an extreme use case.
While the guy you replied to seens a bit unhinged, I have to agree that pipewire isn't the holy grail some people make it out to be, but I guess it's a better solution than pulse audio for 99% of general users.
Qwel@sopuli.xyz · 1 pts · 166d
Oh wow. How much time does the whole input-processing-output takes? I would have thought it would be so fast that you couldn't notice it
Some musicians assured me that using bluetooth instrument was fine in terms of delay, wouldn't that absolutely blow up all the cool kernel tuning?
ExtremeUnicorn@feddit.org · 3 pts · 166d
I don't know much about "bluetooth instruments", the question is what's meant by that, exactly. There are wireless units for mics and guitars, but they are usually connected to an amp directly, so there is only one way transmission, which may be fine with a bit of latency.
When you use your computer as a digital amp/effects processor, you get a roundtip latency, e.g. from the input into a AD converter, to digital processing and back through a DA into the speakers.
That means you basically have doubled the internal latency and the more effects you use in parallel, the tighter the timings have to be.
With jack on an optimised system, I get anything between 4-8ms of total latency. Anything below 20ms is generally considered "fine", but you can hear it, depending on your subjective brain and ears. I would say I notice anything above 10ms already, but I've played with 16+ when I started and it worked for pracitsing.
Shipgirlboy@sh.itjust.works · 4 pts · 166d
Here, you're not you when you're hungry
PointyFluff@lemmy.ml · -4 pts · 166d
OP. Fuck right off with your nazi-bot repost.