Today’s upgrade of Pipewire in antiX 23 Bookworm

[anticapitalistaForum Admin]

Fixed debs should be installable now via apt (thanks to Dave for uploading them to the repos quickly)

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[abc-nixMember]

👍

Corruption has two hands: the Right and the Left. Don't let them squeeze you.

[marcelocripeMember]

olsztyn, thank you very much for reporting the issue and many thanks to all the people involved in fixing the issue.

[olsztynMember]

Thanks to anticapitalista/Dave for such quick fixing this issue. Pipewire upgrade appears to be working now as expected.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Xunzi_23Member]

@anticapitalista Thank you for the prompt assistance, updating stable works fine now.

[Brian MasinickModerator]

This seems to work fine; I’ve updated multiple instances between late yesterday and now.

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

[RobinMember]

Bad news.

Having meanwhile the upgrade to 1.4.2-1.0nosystemd2 on antiX 23.1 full runit 64 bit (live) installed and remastered, I notice now a bad deterioration. When with the former version there were no crackling noises for me at all, with the new version now I get constantly a loud, explosion like pop, when either starting another application accessing sound output or starting playback in an already running audio application after a while of idling. I have never seen that in any antiX pipewire version before.

Morever now I get the following new error messages on console when running wpctl while something is playing back in an audio program:

$ wpctl status
W 16:47:05.896111             mod.rt ../src/modules/module-rt.c:330:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
W 16:47:05.896206             mod.rt ../src/modules/module-rt.c:995:do_rtkit_setup: RTKit does not give us MaxRealtimePriority, using 1
W 16:47:05.896572             mod.rt ../src/modules/module-rt.c:330:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
W 16:47:05.896590             mod.rt ../src/modules/module-rt.c:1000:do_rtkit_setup: RTKit does not give us MinNiceLevel, using 0
W 16:47:05.896969             mod.rt ../src/modules/module-rt.c:330:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
W 16:47:05.896990             mod.rt ../src/modules/module-rt.c:1005:do_rtkit_setup: RTKit does not give us RTTimeUSecMax, using -1

(followed by its expected default report)

These errors have been described already by others before:
@Xunzi_23 has stated crackling noises in pipewire, while I never could hear them. 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. Now they reached me, and do harm to my speakers. This needs a fix, really.
@newbornin2k has provided a wpctl output which shows precisely the same error messages some days ago.

From the error messages, just a shot into the blue: Is it possible that pipewire meanwhile expects an RT-kernel for running fine?

Or maybe the rtkit package needs to be installed now?

$ apt-cache policy rtkit
rtkit:
  Installiert:           (keine)
  Installationskandidat: 0.13-5.0nosystemd1

Additional observations here:
– When stopping and resuming playback within a relatively short period of time the plop doesn’t occur. Only when waiting a bit longer with resuming, this starts with an explosion like plop again. Sounds like unplugging an analogue audio cable from an amplifier under full load without muting the speakers before.
– Some time after stopping any playback, wpctl reduces its error list to a single line, reading:
W 16:59:36.383692 mod.rt ../src/modules/module-rt.c:330:translate_error: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
(followed by its expected default report)
Immediately when resuming playback or starting another audio program, the plop comes back together with the long error message list from wpctl. But the messages not necessarily reduce again, when the plop reappears.

Hopefully this can be fixed in some way, otherwise I’ll either have to downgrade to the former version, or I’ll have to switch to plain alsa. Will have to countercheck on antiX 25.a1 whether it is actually present there also. When performing the testing on it, I noticed some crackling there already, but didn’t pay attention since I thought it was caused by another arbitrary factor So it needs deeper inspection now, when I see the very same thing after the update of antiX 23 to the very same pipewire version.

Versions in use (latest I get on antiX23 bookworm from apt) :

pipewire:
  Installiert:           1.4.2-1.0nosystemd2
  Versionstabelle:
 *** 1.4.2-1.0nosystemd2 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bookworm bookworm/nosystemd amd64 Packages
wireplumber:
  Installiert:           0.5.7-1.0nosystemd1
  Installationskandidat: 0.5.7-1.0nosystemd1
  Versionstabelle:
     0.5.8-1~bpo12+1 100
        100 http://deb.debian.org/debian bookworm-backports/main amd64 Packages
 *** 0.5.7-1.0nosystemd1 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bookworm bookworm/nosystemd amd64 Packages

Windows is like a submarine. Open a window and serious problems will start.

[RobinMember]

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

Windows is like a submarine. Open a window and serious problems will start.

[anti-apXosMember]

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.

Robin wrote:

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.

"--"

[Brian MasinickModerator]

Robin wrote:

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

anti-apXos wrote:

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.

Robin wrote:

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

[Author]

Posts