this post was submitted on 04 Apr 2026
880 points (96.7% liked)

linuxmemes

31120 readers
159 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    880
    systemctl status --user pipewire (lemmy.world)
    submitted 2 weeks ago by cannedtuna@lemmy.world to c/linuxmemes@lemmy.world
    130 comments fedilink hide all child comments
     

    you are viewing a single comment's thread
    view the rest of the comments
    [–] luciferofastora@feddit.org 1 points 2 weeks ago (1 children)

    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 .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?

     

    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.

    [–] FauxLiving@lemmy.world 2 points 2 weeks ago (1 children)

    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.

    [–] luciferofastora@feddit.org 2 points 1 week ago (1 children)

    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.

    [–] FauxLiving@lemmy.world 2 points 1 week ago

    I'm glad you got it figured out!

    Just pay it forward, there's always people with questions that need answered :P