• TurboWafflz@lemmy.world
    13·
    3 days ago

    i’m so confused whenever i see this, i’ve been using linux since 2012 and sound has always just worked? I can’t think of a single time I’ve had an audio problem that wasn’t damaged hardware

    • jj4211@lemmy.world
      1·
      2 days ago

      Bluetooth. Like it works most of the time, but especially randomly the microphone does not work

    • Naia@lemmy.blahaj.zoneEnglish
      4·
      3 days ago

      It depends. The old ALSA system was flaky from what I remember. Pipewire seems more stable, but can have issues with multiple devices but that might be more a bluetooth problem.

      I’ve also had constant audio problems in windows, including every update shuffling all my audio devices and making a random one default and switching to the wrong device when connecting a new one.

  • quediuspayu@lemmy.dbzer0.com
    37·
    4 days ago

    There’s always sound.

    It takes one second to start and there is some crackling with plenty of forum posts explaining how to fix these things going back to 2005 that are no longer relevant because the sound uses something with a different name now.

    BUT THERE’S ALWAYS SOUND!

    • Victor@lemmy.world
      22·
      4 days ago

      If a sound plays but there’s no audio server to receive it and convert it to an analog signal, does it make a sound?

    • FauxLiving@lemmy.world
      4·
      3 days ago

      there is some crackling with plenty of forum posts explaining how to fix these things going back to 2005 that are no longer relevant because the sound uses something with a different name now.

      This is almost always because your pipewire buffers are too small (because of the defaults erring on the side of low latency) and so when the CPU is busy the buffers empty and you get some crackling. Use pw-top to see all of your devices and sources, next to the devices you should see a number in the QUANT column. Chances are that this is really low (or 1)

      You can change your minimum buffer (pipewire calculates this by setting a ‘quantum’), temporarily with :

      pw-metadata -n settings 0 clock.min-quantum 512

      You can edit /etc/pipewire/pipewire.conf and add a line under the [clocks] section:

      default.clock.min-quantum = 512

      Restart pipewire for the setting to take effect:

      systemctl --user restart pipewire

      (If your sound ever just dies for no reason, restarting pipewire is often all you need to do)

      Use the temporary setting to increase the number. Lower number means a shorter buffer so, you get less audio latency in exchange for the risk of the buffer emptying. I don’t have much problem with 256, but sometimes Proton adds some extra CPU overhead and I’ll bump it up to 512.

      • quediuspayu@lemmy.dbzer0.com
        1·
        3 days ago

        I’m saving your comment for when I’ll reinstall the operating system in a few days. Thanks.

        Any advice on the other issue that mutes all notification sounds? Last time I checked there were plenty of posts on how to disable power savings on pulse but not for pipewire.

        • FauxLiving@lemmy.world
          1·
          3 days ago

          That would depend on the notification application that you’re using.

          Give me any details that you can think of. Software version, things you’ve tried, etc. I’ll look into it after work

          Do sounds work sometimes and then stop or is it that they’re playing but the output is set to muted by default?

          • quediuspayu@lemmy.dbzer0.com
            1·
            3 days ago

            Thank you!

            It always takes about one second to start any sound after staying silent for a little while. I managed to figure out it was a power savings mode putting the service to sleep and not waking up fast enough, for pulse it seems to be as easy as to change a true for a false to a power savings option inside a config file, I guess that in pipewire is the same but I couldn’t find the option, that line probably needs to be added somewhere and I’m not sure where and what to write exactly.

            The part about the muted notifications was because all the sounds shorter than one second end before the thing wakes up.

    • Rai@lemmy.dbzer0.com
      1·
      3 days ago

      I was shocked when sound started coming out of my portable monitor via HDMI when I first installed Pop… I don’t need sound, I just want my dedicated server to run!

  • HorreC@lemmy.world
    4·
    3 days ago

    I spend more time dealing with my partners windows machine when it does an update getting their audio up and back to what it was, then I have with linux in 8 years (at least). And I did a major change from deb based into redhat base. And I dont even think its a bleeding edge distro issue, as I do run a Nobara system and that is based on fedora (which is still considered bleeding edge for the most part).

  • RustyNova@lemmy.world
    4·
    3 days ago

    Funnily, I don’t have sound issues on pipewire (unless I turn on my excessively big easy effect default preset).

    But windows? Oh boy windows… Listening to something after a teams call? Garbled sound. Locking your session then going back? No more sound. Connect the same Bluetooth headphones as the rest of the week? Volume get muted. Press the volume button? Nothing. Press the volume button while sound is playing? Oh hey now it works

  • binarytobis@lemmy.world
    4·
    3 days ago

    Recently my speakers have been switching left/right. I was physically swapping them for a while, now I try and ignore it. I’m sure there’s some eldritch linux magic I too new to know like alsamixer that will fix it.

  • phar@lemmy.world
    4·
    3 days ago

    I had some issues in pre-2019 between alsa and pulse. I don’t think I have had any sound issues since then

    • Rose@slrpnk.net
      3·
      3 days ago

      Long ago, I had SoundBlaster Live! soundcard which was perfectly capable of mixing audio on hardware under ALSA, which in my mind meant that all of the userland sound daemon nonsense could go straight to hell for all I cared. Earlier, EsounD never worked right and no app supported it directly and the wrapper utility was a hassle when it even worked. Then came PulseAudio. I could get buuutttery smooth audio on direct ALSA or laggy barely working audio on Pulse. Absolute hog.

      Sure, nowadays the situation is better. But back in the day, for me, the answer to “why isn’t the sound working?” was usually “you tried to use anything but direct ALSA”.

      • phar@lemmy.world
        2·
        3 days ago

        I have not made the switch to Linux in the days where I still had a dedicated sound card. But I had extremely similar circumstances without a dedicated sound card. So I definitely believe you

      • davidgro@lemmy.world
        1·
        3 days ago

        Funny. My experience was the exact opposite. Maybe it was bad defaults which I never managed to fix, but I could never get two apps to use sound at the same time, which meant until Pulse became the standard and fixed everything, it was always constant battles between aRts, ESD, and apps that used neither.