You must log in or register to comment.
Try run the decibel linux pendrive you made earlier and preserved in a working audio state.
And/or there are GUIs for JACK connectivity… ?
Outlook and now Pulse!
It’s a joke about the outlook thing. Not actually real
This is psyop, they run windows up there, their outlook doesn’t work, and everyone kinda accepted that.
This is a meme, sir.
Most of psyops are done via memes nowadays
While I don’t disagree, given there was a user making throwaway accounts solely to post controversial comics on [email protected], this is a pretty specific joke that only Linux users would understand and appreciate. It of course is parodying the 2 instances of outlook issue they had on the rocket.
Yeah, I don’t actually believe all of that jokes are literally psyop. It wasn’t entirely serious comment.
It wasn’t entirely unserious either.
I hope that’s like a personal laptop or something. I’d hate to think we shot people into space on something that’s running windows for a critical system.
I have not worked on human rated launch vehicles, but I’ve been adjacent to them, saw what went into them, and a few close personal friends have worked it.
Anything that can jeapordize the safety of the crew must go through a rigorous independent validation and verification process that takes years, software included. No shot a Microsoft product was even in consideration for those systems.
Being in industry I find it crazy that so many people are freaked out by this. Astronauts have email, they have tasks and schedules and reports to make. Why would NASA reinvent the wheel on a task/schedule manager when the ground operators and astronauts are already used to using Outlook.
Wait are you saying they do or don’t have Microsoft products?
I think they’re saying they’re not using Windows to operate Artemis II but the astronauts are probably used to using Microsoft products. So when it comes to simple logging and data entry they probably are using Windows. But these are their own computers and not used to run Artemis II. I may be wrong but that’s how I understood it.
Yup, sometimes it’s too easy for me to just slip into work mode when talking about this kind of stuff and I don’t elaborate enough. Thanks for stepping in.
Based on industry rumors I believe the Orion capsule control computers are running VxWorks (I’ve heard that maybe a few boxes are using RTEMS?) All of that source code would have been reviewed, audited, and tested to hell and back.
The day-in-the-life stuff for the astronauts is entirely believable to be Windows. The risk of it failing is so low (medium probability, low impact), it’s what they’d be familiar with, and it’s part of daily life at NASA anyways. Linux is no better when it comes to safety critical components and the astronauts almost certainly wouldn’t want to be dealing with Gnome’s… uniqueness…
But on a serious note, mine just jumps up and down in volume randomly
I have it piping audio to three different devices at the same time. And believe it or not they’re all in sync… most of the time.
I actually had a sound issue the other day. Just no sound, how weird. It worked the day before. Checked wpactl, volumes etc, everything was fine and working. Restarted pipewire, still no sound.
Turns out my external mixer lost power because the powet socket was slightly loose.
Can’t believe Linux would do such a thing
This is a joke right? Yesterday I saw a post that outlook was a problem for them
Yes it’s a joke referencing the two Outlook instances issue, but for Linux people
Haha thanks. I feel dense in retrospect
Sometimes satire is hard to detect in this joke of a reality we’re living in.
Ain’t that the truth. Have a good evening!
They’re not supposed to have both installed.
Pipewire is newer and emulates PulseAudio so that it can be used as a drop-in replacement. There’s literally a command called
pipewire-pulserelated to this.It makes me wonder if they really have both installed or are mistaking Pipewire’s emulation for an active PulseAudio installation, and so it’s just Pipewire that’s acting up.
I’d say reboot, but being in space might be one of those times where that’s a non-starter. In which case, they’re going to have to get their hands dirty unpicking system hooks and trying to reattach them all again as and when Pipewire’s working again, assuming it doesn’t do that automatically.
I never had a problem with either Pipewire or real PulseAudio back when that was current. I had motherboard sound physically pop, requiring the purchase of a separate sound card, but never a driver issue, so I can’t even imagine what might be going on.
I’m pretty sure this is a meme based on the real report that they had 2 instances of outlook on windows and not real.
Wait, they had two instances of not real? They are learning too much.
Sorry I am autistic and often don’t know how to properly formulate my thoughts into sentences :D
You’re in the right place, most social media users can’t properly formulate their thoughts into sentences, lol.
Dad, don’t do this in front of my friends. You’re embarrassing me.
Its not real its referring to the issues they had with outlook
My laptop is Mint and it’s never given me audio issues. My gaming rig is Nobara and the only audio issue I’ve had with it is that I forgot to switch the output to the TV.
They’re just like me! I have no idea which I’m using either.
My Mint laptop audio stopped working for a couple months and then miraculously fixed itself this week. I made various attempts to fix it with no luck. It’s either a hardware issue or some obscure software issue.
In the past, I had plugged in a HDMI cable to mirror the screen and couldn’t get the audio working again until I plugged it back into HDMI and switched it back to the internal speakers before unplugging HDMI. Before the audio broke this time, I had connected a USB microphone, so it’s possible that’s what did it.
Happened to me on Mint as well. Never resolved it. Using Nobara and Fedora now and never had any audio issues. Seems to be something with how Mint handles audio as I see people mention this a lot.
Interesting, I’ve only ever had this issue in Mint as well.
Real talk, though: why has Linux taken at least five tries (OSS, ALSA, JACK, PulseAudio, PipeWire) to get audio right?!
OSS came first, then got replaced by ALSA after it became proprietary.
PulseAudio is a userspace audio server to which programs connect. It manages audio settings per app, then sends everything to ALSA. JACK is the same but with a focus on low latency.
PipeWire is a modern drop-in replacement for both, and also has support for video on Wayland.
And then there’s also sndio, ported from OpenBSD. This does basically the same thing as OSS/ALSA.
Ohhhhhh the newbies don’t remember EsounD (
EnlightenmentEnlightened Sound Daemon). Basically, it was an attempt at doing PulseAudio-esque stuff way back in the OSS era. Which is to say, it just supported software mixing of multiple audio sources, because OSS usually only allowed single process to output audio. EsounD was janky and didn’t work well, obviously. Probably the neatest thing about it was that it exposed the mixed output stream to any other app, so that made visualisers much easier to make (edit: another thing that newbies in this day and age don’t realise, but I cannot emphasise enough how crucial visualisers were for the late 1990s / early 2000s music experience). ALSA basically supported hardware mixing (if available) out of the box, so of course it immediately became my favourite.That’s the thing about open source. Someone always thinks they can do better
That’s not a feature thats exclusive to open source though. Circular reasoning like this just distracts from the fact that software just like hardware is constantly evolving, even in personal spaces. Thinking someone can do better has no relevance on the “open source” aspect or the political leaning.
You mean someone thinks they need to do better not by enhancement but by complete replacement. See: Systemd and its own flailing.
SystemD knows what it has to do.
everything
They don’t have the same goals.
JACK is for professional audio.
OSS and ALSA are kernel audio drivers, they’re the most powerful of them all but extremely low level. Everything else, like pulseaudio/pipewire are just higher-level interfaces that feed ALSA audio.
Pulseaudio and pipewire are sound servers.
So really it only took two tries:
OSS -> ALSA
Pulseaudio -> Pipewire
I’m still waiting for the latency to be viable for playing guitar with an audio interface.
I’m using pipewire just fine to do so? I just needed to set the buffer size to something appropriately low and I’ve had no issues from popewire’s side
Holy audio
New tip just dropped
Maybe it’s time to give it a shot again. Does pipewire have similar functionality to voicemeeter the virtual audio cables?
There’s helvum and carla control that allow you to edit the entire audio graph with all ins and outs for all hardware and software so you can route it however you like. No need for VAC and such. But even if you do, you can load pulseaudio modules i.e.
pactl load-module module-null-sinkand then route them withqjackctlwhich is absolutely crazy and awesome how pipewire lets you do that.Never used it, but I use something called pipewire graph or something (I’m on vacation and I can’t be bothered sorry heh)
Give Ubuntu Studio a try maybe? It comes with a lot of audio production stuff preinstalled and preconfigured, one of the most important ones in this context being low-latency process scheduling.
Essentially most distros just have default process scheduling options, which means a process might be starved for CPU time, theoretically for up to 2s or so at a time, which is very bad if that process is generating or consuming an audio stream. Low-latency scheduling, while not entirely preventing it from happening, should significantly reduce this.
You could also just configure most other distros Kernels to do low-latency scheduling of course. Or if you don’t want to muck about with kernel settings try Ubuntu Studio, which has that and more all ready to use.
My pipewire seems to have issues with crackling audio and severely dampening my mic and I have no clue why.
Still better than Windows.
My pipewire seems to have issues with crackling audio and severely dampening my mic and I have no clue why.
Pipewire’s default quantum (buffer size, effectively) is incredibly low, this is good for low latency audio but anytime your system is too busy to keep the buffers filled you get crackling.
If you look at
pw-topyou’ll see all of your devices and nodes. The quant column is probably 1 or a very small number for the devices.You can increase the quantum with this command. This only lasts until pipewire restarts:
pw-metadata -n settings 0 clock.min-quantum 512At a sample rate of 48000, this is roughly a 10ms buffer. 1024 is 20ms, etc. You want it as low as possible without getting crackling. Start with 512 and adjust from there (you don’t have to use a power of 2, a quantum of 1234 works just as well).
severely dampening my mic and I have no clue why.
By default pipewire doesn’t do any ‘mic boost’, as Windows calls it. You can get the same effect by raising the maximum volume.
In your sound control panel you should be able to turn the mic up higher than 100%. In KDE Plasma, you can do this in System Settings -> Sound -> Configure Volume Controls… [top right button] -> Raise maximum volume.
Alternatively, you can use EasyEffects to add a compressor. This will boost your mic volume and also prevent it from getting too loud
Compressors basically reduce the dynamic range of an audio signal by attenuating loud sounds and boosting quieter ones, this would provide a better mix.
Other useful plug-ins are noise canceling, (kills background noise) and echo canceling (lets you play sound out of your speakers which won’t get picked up by your mic). Sometimes apps, like Discord, will do this signal processing for you while others, like Signal, do no signal processing.
I absolutely wasn’t expecting a helpful response under a meme, so thank you very much for taking the time to write it!
anytime your system is too busy to keep the buffers filled you get crackling
I’d have to test that more thoroughly, but I do think that lines up with the timing of the issues.
You can increase the quantum with this command. This only lasts until pipewire restarts:
Can I put that in some config to make it stick?
I’m admittedly very junior to pipewire config, so most of what I have is copied from the internet, tweaked for node names / descriptions, but I generally like working with config files and slowly learning what all that stuff in there means.
I have two loopbacks (I like having music and games each grouped separately from other audio), an echo-cancel and a noise cancel (filter-chain with a single rnnoise node), all configured via
.conffiles. As an aside, is there a “best order” to chain echo cancel and noise cancel?Echo cancel seems to have a quantum/rate of 480/48000 across the board. Loopbacks, rnnoise and alsa_output (my headset) all have 0/0. I imagine it makes sense for the Loopbacks and rnnoise, but should it be something else for the main output?
By default pipewire doesn’t do any ‘mic boost’, as Windows calls it. You can get the same effect by raising the maximum volume.
Well, it seemed to work just fine without echo cancel, if I capture the mic directly, but putting it through echo cancel (with or without noise cancel) seems to reduce the gain significantly.
I’m gonna mess with the volume sliders and see which ones I can crank up to fix that issue.
But I’m confused why that issue would occur in the first place and if I have something misconfigured.
Alternatively, you can use EasyEffects to add a compressor. This will boost your mic volume and also prevent it from getting too loud
Sounds like a compressor would be a good idea to have anyway. Is that also doable through the config? I’m not opposed to graphical tools, I just feel like working with the config directly is more educational. It’s also more prone to screwing things up, but that’s just bonus lessons on what not to do.
Sometimes apps, like Discord, will do this signal processing for you
Curiously, the reason I looked at echo-cancel in the first place is that Discord’s own echo fucks with things, cutting me out at times while also not cancelling the echo at others.
Can I put that in some config to make it stick?
Make a file in pipewire.conf.d: ~/.config/pipewire/pipewire.conf.d/min-quantum.conf
With this, replace the quantum with one you’ve found works best:
context.properties = { default.clock.min-quantum = 512 }Restart pipewire for it to take effect.
I have two loopbacks (I like having music and games each grouped separately from other audio), an echo-cancel and a noise cancel (filter-chain with a single rnnoise node), all configured via .conf files. As an aside, is there a “best order” to chain echo cancel and noise cancel?
Echo cancel seems to have a quantum/rate of 480/48000 across the board. Loopbacks, rnnoise and alsa_output (my headset) all have 0/0. I imagine it makes sense for the Loopbacks and rnnoise, but should it be something else for the main output?
I have been doing echo-cancel -> rnnoise. That way echo cancel gets a clean stream to do what ever correlations that it needs to do and then rnnoise de-noises what is remaining.
As far as the latency, I think it is because echo cancel needs a bit of a default wait in order to actually hear the sound coming out of your speakers (speed of sound is slow, smh) which is why I think that delay is there (though this is complete speculation, if someone knows better I’d love to know).
The quantum of all of the devices is propagated through the chain so if you have echo cancellation in a graph then all everything will use at least its quantum (if there are not higher quantum objects in the chain). If a device doesn’t have a quantum, it’ll either use the min-quantum or the highest quantum of any node in the graph.
Sounds like a compressor would be a good idea to have anyway. Is that also doable through the config? I’m not opposed to graphical tools, I just feel like working with the config directly is more educational. It’s also more prone to screwing things up, but that’s just bonus lessons on what not to do.
I agree, learning the underlying system pays dividends.
Any LADSPA filter will work as a node in pipewire. So the world is your oyster!
This explains how to set it up better than I can here: https://forum.endeavouros.com/t/pipewire-filter-chains-normalize-audio-noise-suppression/31661
Curiously, the reason I looked at echo-cancel in the first place is that Discord’s own echo fucks with things, cutting me out at times while also not cancelling the echo at others.
Yeah, I’ve had similar experiences. I typically disable any sound processing done by the application and depend on my own plugins to handle that.
I adapted the normalizer Sink from that post to be a normalizer Source, replaced the local paths with the system lib names, made a mistake, fixed it, got everything hookes up as I think it should be. How it performs under load remains to be seen, and which order noise cancel and nornalizer go will be tinkered with, but at least the service restarts and everything looks fine.
May life be as kind to you as you have been to me.
I’m glad you got it figured out!
Just pay it forward, there’s always people with questions that need answered :P
Oh I had this issue and it drove me bonkers trying to fix it! I have to go digging a not to try and remember what fixed it in the end.
Sorry @[email protected], I got out of bed and completely forgot to actually go check what I did. My issue was under high load the audio would crackle, I could never quite establish if it was GPU or CPU, but at least it was during intenser moments in games. I played around a lot with the quantization that people in here have already suggested but it never fixed the crackling.
What finally solved it for me was to enable
threadirqs. You can do this withsudo kernelstub -a threadirqs. I don’t entirely understand it, but I believe it makes the interrupted handler execute in threads.Thanks for remembering, checking and getting back to me! I’ll look into that
threadirqsthing, thanks for the pointer!
Bluetooth headphones by any chance?
Nope, wired. Separate ports for input / output on the front of the case.
Read the arch wiki on troubleshooting pulse audio. I remember having this issue long ago.
The issue occurred yesterday gaming with friends and I didn’t have time to troubleshoot yet, but I’ll keep that in mind, thanks!
I’m still trying to figure out why the only real way of taking screenshots fast in Wayland is to do a video capture of the desktop with pipewire…
I don’t know what you mean. I can just hit the print screen key on my keyboard and have a screenshot in my clipboard.
I need it to automate fishing in Minecraft, and the normal way to take screenshots in Python (which is one line with PIL) on Linux went from at least 30 possible fps on X11 to 2 on Wayland. The only way to do it fast enough then is to use Pipewire. Which is one hell of a convoluted mess. (The next part of this whole mess will be finding a way to send mouse clicks without having Minecraft registering a mouse move too in case xdotools stop working)
You need the print screen key for something else is what you’re saying (I had trouble following your reply)?
Can only speak for KDE, but you can easily change the screenshot shortcut to something else in settings.
I’m writing a script that automatically take screenshots of the desktop (in particular the Minecraft game window) and then use OpenCV to do template matching to recognize if I’ve caught a fish or not.
If I use any usual screenshot capabilities of any python library, I simply cannot take pictures fast enough (at least 10 images per second) to have the script work (under Wayland the usual system top out at 2 images per second).
The only way fast enough I’ve found so far is to use Pipewire to create a livestream of the desktop and get frames of it to do the job.
And it is a complex mess. (At least I’ve found a (very basic and badly documented) library to do most of the work instead of having to work it all through Dbus myself.)
It’s just that what once was a single line in my previous X11 script is now a full on script by itself, and I understand almost nothing of it.
Surely there’s a better way to determine if you’ve caught a fish or not? Because damn…
The alternative is to create a multiplayer bot that directly speaks the network protocol. Mine simply looks for the relevant subtitles when fishing, and use template matching avoid bringing out a full on OCR. Others use audio cues to work. There’s no real simple way to solve the problem there. Unless Mojang manage to make fishing not boring.
I feel this one. Used to daily drive Linux but due to a work requirement had to switch to Windows several years back. Windows has been getting shittier and shittier and I no longer need to use Windows for work and it only just gets shittier so I just switched to CachyOS and love it. Except the one and only issue I haven’t been able to fix is audio. I use a Bluetooth speaker on my computer and it cuts out randomly even using low bit rate audio streams. Tried switching pulseaudio to pipewire because the internet said I could increase the latency and that that would fix it but no dice.
Some Mediatek chips are doing this, that is bt audio cutting out while WiFi doing things. Nothing fancy, 1080p video on YouTube will cause that.
Hm? Removed pulse, installed pipewire-pulse, ran
pipewire && wireplumber && pipewire-pulseas user and everything just works. Except that my cheap bt-inear sometimes cause a crash of bluetoothd (and that one should restart by itself but whatever) but that’s not pipewire’s fault.@MonkderVierte @tjhrulz
Hm? Removed pulse, installed pipewire-pulse, run pipewire && wireplumber && pipewire-pulse as user and got no available sound devices.Why? Because wireplumber’s bullshit crashed after forking to daemon somewhere in camera support code (but i do not have cameras!).
With reference pipewire-media-session everything worked, but everybody forcing unstable and bloaty wireplumber, making old configuration not supported…
Yes, maybe it’s not pipewire fault, just it’s modular architecture, but it makes me unhappy with it, so i still using jack. And i sure, there should be separate provider processes for camera and audio devices
fake. pipewire is actually awesome.
that nagging sleep issue though? yeah…
Sleep is my favourite function to complain about, it breaks shit at random on windows and Linux, nobody seems to know why or how. The fact that sleep works as well as it does on consoles and steam deck is a miracle to me.
Well that one is pretty obvious isn’t it? Consoles and the like have a single target hardware, or very few at least, so their testing is way more reliable. Meanwhile a random PC will have one of several hundred chip designs, implemented by a few dozen different vendors, ranging over decades. Development for and testing under such conditions is just way more complicated, so all devs can really do is aiming for #worksonmymachine and hope for detailed bug reports and feedback when others have issues.
actually awesome
It shits the bed about weekly for me. I’m glad it’s working reliably for someone.
pipewire was actually the magic end of all my audio issues on all my computers. what kind of setup do you run?
Just life, linux just works with audio
