There has been exactly one person in this thread being hostile and making personal attacks. The people responding to you have been remarkably controlled considering your posts.

If PulseAudio works fine for you, who cares what other people do, and why would you be against Pat making it easier for them to have their preference? Did I miss some announcement where Pat said PulseAudio would no longer be the standard in 15.0? I use and like PA, and I'm not the least bit worried about such a thing occurring.

7 members found this post helpful.

Re: my previous 3 posts/responses...

Is English not your native tongue, a4z? That might explain why you repeatedly misunderstand and misrepresent me. I can't imagine why you assume I'm attacking you. In fact it is now a matter of record that I attacked your opinions, not you personally. Admittedly there is some overlap with Darth's posts since it seems he agrees with you and my posts attempted to address all the issues discussed in this thread that propose that ALSA is somehow "going back", inferior to Pulse, or no longer needed, not just yours.

Ultimately it is as OP entitled this thread which is giving thanks for providing the ALSA-only option to which some seem to feel the need to express negativity to both ALSA and Slackware developers, especially Patrick. This is what I am responding to. I am ignoring your original post because it is a tangent, if not Off Topic, and involves both hardware and software that I don't have nor prefer to have, so I can't speak from experience on that topic. I chose the one post as is my right especially since I quoted it to be absolutely clear as to what I was responding to.

You started with the "back to ALSA? Is this a joke?" to which I explained it is an option not a requirement and one appreciated by audiophiles, especially those who have good hardware and record and edit. I wasn't "talking through my hat" nor was I trying to wow or intimidate anyone with formulae or some ersatz evidence of my training and skill. It wasn't me tooting my own horn it was simply to point out that some people have requirements, real requirements not bat ears, a joke, or delusional, just exacting.

IMHO it is counterproductive to actually communicating a concept to get technical just to flaunt technicality. Albert Einstein is quoted as relating "If you can't explain a concept to a six year old, you don't really understand it yourself" and while that may not always be accurate, where it applies it is profoundly accurate and it is my regarded opinion it applies here.

Bottom Line my responses are a cost/benefit analysis explaining that some use cases enjoy no benefit from Pulse and are "taxed" with considerable "cost". It is about the subject of this thread. It is not about me nor is it about you.

I apologize if anyone thought that I was lobbying for an "Alsa-only" Slackware. That was not my intention at all. I am celebrating the fact that Pat now includes a directory in /extra that has everything you need to set-up Alsa as your default sound system software if you want to do that.
Pulse Audio is and continues to be the default sound system in Slackware. Here's a quote from the man himself in the current changelog about all of this.

1 members found this post helpful.

of course not

this was a reply to post #11, where Jeebizz asked

and this is the context that you, and especially orbea, have ignoring, (beside that I also told the OP that I have no problem with basically the same hardware, what is also total on topic and helpful)
If you would be the same way on topic as I you would bring concrete reproducible examples where ALSA is much better that you can not have the same/very similar result with a proper pulse configured system, or tell me that REAPER needs a pure ALSA system (dont know if this is the case), or something similar...



And orbea who starts, btw the second time now, intimately with a post containing an allegation and an insult on personal level.
and you tell me that is not hostile?

@orbea, the last time I ignored you was just for one thread where you behaved the same, with creating lies and misquotes of what I have written, now I will ignore you for ever. I wish you would do the same with my posts, this would spare this place a lot of trash you produce. You will of course not do this because your personal crusade is too important for you and you psyche, but please, orba, understand, the links your therapist gave you where for the reason that you apply them for your own purpose, not spread them on various places in the internet to train you passive aggressive provocations and trolling. You are, btw, a bad troll anyway. So lets see if this works, I ignore you , you ignore me, and we spare this place text trash, I can do this, can you?

This is a great move by PV. Just for a particular scenario, a4z, you may be interested to know that one of my three Slack machines has Pulse disabled. Why? This is because it's a netbook and the rather cheap onboard sound unit doesn't pack much of a punch. I would have used Pulse if there was an option for an EQ to improve this, but the EQ for Pulse was deprecated. Therefore, I have disabled Pulse altogether and just run everything through ALSA using dmix and alsaequal. This gives me much more control over the sound quality than stock Pulse would.

You may say, well, that's no reason to disable Pulse, but Pulse has other ideas. It likes to take control of my volume button bindings, which causes conflicts and sometimes stops them working. I've therefore re-bound them through amixer and disabled Pulse to stop any more issues.

You can see some of the other issues I've experienced with Pulse on the netbook here: https://www.linuxquestions.org/quest...ns-4175626284/

Like I say, Pulse is absolutely fine on my other two machines, but in this instance it's a hardware-based issue that makes me use ALSA only.

I have and never had anything against people that run a pure ALSA system, thoguht so far I never have seen a usecase that really proves the requirements. So until now I just see disadvantages in such a seutp.

Also, a lot of info I validated from the "I need ALSA" people is simply not correct, like OPs notebook requirement for ALSA, or your deprecation of EQ you write about.
https://github.com/pulseaudio/pulsea...ualizer-sink.c
was updated last time some weeks ago,
here how to activate it
https://wiki.archlinux.org/index.php..._on_every_boot

also qpaeq is under active development, look at the history
https://github.com/pulseaudio/pulsea...rc/utils/qpaeq

but maybe you meant something different when you wrote about a the EQ for Pulse that was deprecated?

anyway, as said, I never had something against pure ALSA system and just that I answered a question that if this should be a default solution is a bad idea does not imply this. That I would find an onboard multilib compiler more useful for me does also not imply I have something against ALSA systems. That I have something against ALSA systems is an phantasm construct of some people here, that's all.
For me everyone can mess up their system as they want, I just some fix some facts, like a t410 needs ALSA, or EQ deprecated, no idea why some self declared hardcore guys here are triggered through that and think they need to spread rumours and attack me

Exactly. I have the same experience. Pulse is fine on 4 work stations, and works intermittently on the 5th work station. I am grateful that Pat has reintroduced Alsa as an option.

I agree! Thanks to Pat V. and team yet again.

I am not sure what all the debate and arguing in this thread is all about. I certainly didn't read much passed the first reply of a4z because I just knew what kind of thread this was going to turn into. Pulse and Alsa are both possible in Slackware-current so there is no reason to discuss it.

3 members found this post helpful.

LOL - It could be worse. I tried some BSD operating systems and found that BSD doesn't support my sound cards on either my laptop or my desktop. No sound. Silence.

FWIW I use whatever is the default and appreciate it for what it does

OK a4Z, it seems you won't just accept my expertise, research and training regarding the issue of flexibility, control and low-latency so here's a quote from a pro article that is, BTW, extremely happy with Pulseaudio in general and not just another rant/wash. You can find it here if you'd like the full read. https://freedompenguin.com/articles/...et-full-roses/

Here is a relevant quote snippet

Please do yourself the favor of being realistic and not imagining the NBA might be better off to hire more guys that are 5 foot 2. There are levels, even on Mt. Olympus. You're happy with Pulse because you are a casual user. Some people are Pros. Oh and please don't bother mentioning that a special version of Jack has been made for Pulseaudio. Jack2 lacks some important features enabled in Jack that cripple it not to mention now we have 3 layers of software instead of just 1.

FWIW because MS deemed it so important to be able to compete with Macs that used to dominate Pro Sound it enabled the audio layer to have direct access to hardware, bypassing the preemptive nature of the OpSys (yeah the same thing responsible for ye olde BSOD, but substantially improved now) to achieve low latency on a par with Mac and Linux. Latency is by no means a trivial issue. In fact it's HUGE.

4 members found this post helpful.

It doesn't always work either. I've tried every way that's been announced on the forums, and for the most part they are not that easy nor little and it's simply way too much jumping through hoops to have something (ALSA) on my system that 'just worked' and worked extremely well compared to this escaped abortion known as pulseaudio.

Luckily I keep 14.1 on another HDD so that when I want to listen to my music and hear it the way it's supposed to sound, I just switch over...far simpler than the supposed 'easy/little mods'.

Dear audiophiles with ears of bat, did you even heard about Real-Time Kernels? https://rt.wiki.kernel.org/index.php/Main_Page

This friend of mine, who is certainly an audiophile and a professional, says that a Real-Time Kernel is a must have, end of line. Everything else is amateurism for the bat-folks.

BTW, he also says that the PulseAudio latency is configurable. To be honest, I don't bothered to research about that myself.

PS. But about the Open Sound System (OSS) did you heard? Apparently the pros use it instead of ALSA which was made right for the "casual user".

in short, no, for 3 short reasons

1) The jack documentation gives more options than a pulse free system
https://docs.fedoraproject.org/en-US...with_JACK.html
https://github.com/jackaudio/jackaud...er_PulseOnJack

2) this is known since very long time
https://docs.fedoraproject.org/en-US...with_JACK.html

3) has nothing to do with my OP, that the t410 hardware does not require a pulse free system to work, and that a pulse free Slackware 15 is a bad idea. or anything else I have written.

you discuss with me issues your, or some other users here, fantasy brought up.

but you bring just more incorrect information, thanks for confirming what I have written about the quality of info of you hardcore guys.
Note that this still has nothing to do with your pulse free system, if you want to have it, fine.
What I do not like are the rumors, bad ideas and wrong info some people spread. Why some people here think they need to critisise me for this, and want to prove me something, no idea
actually, for this info fixes I brought here, and above, someone should say thank you, it says a lot about your guys that you prefer to just write against me, and this just because and without a reason

Edit, but I found one good thing in the article you linked to, enorbet, so thanks for this!
I hope you have read the article you refer to to the end ;-)

Just because you find out that one of the people who were having issues with pulse and concluded it was a hardware issue was wrong, does not mean that everyone who makes such a conclusion is wrong. On my macbook pro mid 2010 13" pulse audio works most of the time, but it still frequently has issues often enough to make me not like it. I've had it crash where I lacked the skills to restore it to operating state until I rebooted the system. I've had odd cracking sound noise and other things that I never am also unable to fix and figure out why without a reboot. Again most of the time it works fine... the difference is I never have a single issue with a pure alsa set up on it. Its my understanding that pulse is supposed to be easy just work... well if that is the case, at least on my macbook, its a failure.

Edit: I think its fine that in 15 Pulse will remain the standard ootb, but, I think it should always be left as optional for several reasons (reasons I don't care to go into in this post).

It is all good just a tool. Programs like firefox and browsers only build against headers. That's what we all do. That way when pulse is not found nothing happens. Pulse is a server. The headers just build objects that can use pulse audio. some programs like I guess bluetooth require it because it is part of the actual build. ALSA is base.
it real close to the kernel. You can build jackd and it will compile against the headers also.
this is way behind when I get back to the states and have time I will bring it up to current
https://github.com/Drakeo/jack-pulse-sink