Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TE
Posts
0
Comments
216
Joined
10 mo. ago

  • Technically it has been a thing since like 2015, but Pipewire 1.0 was only released 10 months ago , even though many distributions were already using it by default since 2021 (Fedora) and 2022 (Ubuntu, Pop! OS), given how much of an improvement it was over pulseaudio.

  • Not trying to blame you or anything, just stating the facts. It does sound like you don’t want to hear the other side though, and are completely convinced that these issues you’re having are normal to the average Linux system.

    Installing a recent version of a normal Linux distribution (Debian, Ubuntu, Fedora, Mint) will come by default with the following: Pipewire server (most likely wireplumber), Wayland, network drivers (except Debian) for most adapters, stable graphics drivers (unless you’re an NVIDIA victim), a DE of your choice (KDE, GNOME, Cosmic, etc). This setup will not have any audio cracking or popping, no flickering at certain resolutions, working USB ports. However, if you’re the type who refuses to update from the unmaintainable Xorg, old pulseaudio/alsa drivers, uses some obscure distribution, uses an NVIDIA GPU, or uses hardware from 2 decades ago, then you’ll have a horrible experience and it will only get worse with time, not better (unless you have an NVIDIA GPU, which will get not-garbage drivers eventually).

  • What’s the “plenty of stuff that doesn’t work”? And what audio/video issues are you having? Pipewire is miles better than anything Windows can conjure up in latency, quality, and customization. Video is literally just rendering pixels, which works with web browsers, and local video players (mpv and vlc). The only valid complaint is [Windows] software availability.

  • This isn’t really driver related. It is the Wayland compositor’s job to properly handle multiple GPUs, which is lacking in some (a very popular, Wayland library that lacks proper multi-GPU support is wlroots) compositors. Vulkan drivers and DRM are already enough to properly handle multiple GPUs. I guess Wayland implementers just haven’t cared enough about the issue, or maybe are figuring out a “perfect” way to address it (a la 3 year long pull request on wayland-protocols repo incoming)

  • Not saying this is the right thing to do. But it does seem like social media consistently suppresses the spread of “hacked” (whatever their definition of hacked might be) material related to political candidates, regardless of party. The same thing happened with the Hunter Biden laptop stuff, which was pretty much impossible to spread on social media. Although Elon Musk is obviously all in on trying to help Donald Trump win, the decision to suppress this information is not surprising. Meta is also suppressing the links.