Reply To: Today’s upgrade of Pipewire in antiX 23 Bookworm

Forum › Forums › Official Releases › antiX-23 “Arditi del Popolo › Today’s upgrade of Pipewire in antiX 23 Bookworm › Reply To: Today’s upgrade of Pipewire in antiX 23 Bookworm

#180948
Brian Masinick
Moderator

    Update:

    Installing the package rtkit removes the error messages immediately from the wpctl output. But no effect on the plopping noise (maybe it is not as loud now, but that is subjective impression only and needs further investigation and testing).

    $ apt-cache policy rtkit
    rtkit:
      Installiert:           0.13-5.0nosystemd1

    You could comment out the libpipewire-module-rt sections in pipewire.conf, pipewire-pulse.conf, and wireplumber.conf, though I sort of doubt rtkit is related to the “plop” you described.

    Is your user even a member if the pipewire group? I don’t think antix adds that group by default.

    My conclusion is: You heard them already, since you are running sid, and thus have got the troublesome update long before I have got it.

    Your pipewire packages should be coming from the antix repos, not debian. So sid/stable shouldn’t affect it. The kernel version certainly could via the ALSA driver. Different hardware is the most likely explanation, though. Every ALSA driver is written differently, so they can have very different behavior.

    Whatever the root cause actually is, it certainly seems that “one size” just can’t fit all, especially with the extremely wide range of hardware, firmware and software that we either use or support. That’s why we typically have an older and a newer kernel somewhere, whether actually distributed on our images or contained in the repositories we use or support.

    I vaguely remember some time ago commenting about certain kernels we had at the time, thinking they ought to handle most needs and even @anticapitalista replied to the contrary, suggesting that a more complete environment is more extensive even than what we offer or support, to which I have to back off and agree.

    Case in point: this community is certainly not strong in supporting, or even wanting to talk about commercial, proprietary systems, except possibly in a critical way, and yet though these are not choices that most of us choose to make, they are and continue to be a plausible and preferable choice for millions of people, particularly people who are willing to pay considerably more for them in order to get support, assistance, and familiarity with what they’ve learned – NOT what most of us are interested in using at all, yet it IS a choice for certain people. Besides, I doubt that very many of us would want to be incessantly answering questions from people arriving in massive numbers from who knows where.

    Instead, we typically like and enjoy software that is decidedly different in many ways, even different than the vast majority of other freely based software systems and distributions. It’s leaner, it doesn’t use the same process management as the others, so DIFFERENT is definitely one label that most of us identify with. We don’t like to punch the same buttons, and most of us do not like mindless activity, we choose to actively engage in what we are doing and why we are doing it.

    So whether we use pulse, ALSA, pipewire, or some combination or selection of each, we can and will provide something that’s efficient and works; it probably WON’T be “one size fits all”; this conversation strongly suggests that this will not work for all of us. What we end up using may not please everyone in whatever choice or compromise we select, but it’ll be an intelligent solution that works in as lean and practical methods as we can accomplish without seriously compromising our goals and principles.

    --
    Brian Masinick
    Alternate "Search B":
    This search page