Xunzi_23
Hi Robin, I absolutely disagree with but the antiX setup as found in antiX full is sound and stable. In regard to sound and over many guided installs it has been a pain in the ass from the beginning. On many installs sound fails, users switch over to pipewire as they attempt to get things working. That is normal but causes more issues.
If the crap needs turning on and off twice to turn it off or remove the files it leaves behind the code does not do its job and needs fixing.
PipeWire was designed with a powerful security model that makes interacting with audio and video devices from containerized applications easy, with support for Flatpak applications being the primary goal.
Do we use propriety Fatpack crap, no.
Pewire is more secure, because it breaks sound, it is a frontend to alsa designed by IBM red hat engineers, for a change not pottering but what is the point of having software:
Designed for a packaging system which is propriety
Has from the start never been an improvement
Is hard to setup and its presense causes user frustration.
Bug #1070348 drove everyone mad for months, message in syslog, once a second and mentioned nowhere but clearly audible stuttering, at least on my setup with, ha ha Kali Studio Monitors.
> >
> > pipewire-pulse[]: default: snap_get_audio_permissions: kernel lacks
> > ‘fine grained unix mediation’; snap audio permissions won’t be honored.
When the fix came it was: Disable snap support in Debian, keep it enabled only for Ubuntu (Closes: #1070348)
For many months users had sound problems when using pwieird, pls, take a read. Sound stops at indeterminate intervalls, A workaround that almost always fixes the issue is to restart either Pipewire or Wireplumber and all applications. I hit that hundreds of times. Returning to pure alsa, headphones, DAC, active speakers, no more issues.
https://bbs.archlinux.org/viewtopic.php?id=292316
eventually a fix came along, add below to the config. Obvious right. Wrong, it works but pretty much nobody knows why but default.clock.q the dreaded snd_pcm_avail after recover: Broken pipe stops its freaky behaviour.
quantum = 2048
default.clock.min-quantum = 1024
default.clock.max-quantum = 4096
But audio crackling and sample rate weirdness still exists on local devices.
I struggle to be polite here, sorry, this is not personal it is about crap on top of the base linux sound system which works for users.
pls take an endless read here https://gitlab.freedesktop.org/pipewire/pipewire/-/issues
Jack Audio usually used with pipewire over 300 bugs open, Builds failing for a year or so, no new release in the pipeline.
Recent issues with the underlying alsa, rare.
one thing I have encountered several times from upstream devs, I can not hear what you are talking about, I ask, how is your hearing, mine is not exactly optimal but I hear issues. I ask, what audio setup do you have, answer computer or laptop speakers, or in German Brüllwürfel. Noise boxes. I was even told my speakers are the issue because too revealing.
- This reply was modified 1 year, 3 months ago by Xunzi_23.