[SOLVED] Thanks for the pure alsa software in /extra/pure-alsa-system
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for the pure alsa software in /extra/pure-alsa-system
I'm running Slackware64-current on five units. One of my units, an older T410 Thinkpad, has difficulty with Pulse Audio. The sound will randomly cut-out.
Sound works well again after removing Pulse Audio and installing Alsa as per the instructions in the README located in /extra/pure-alsa-system.
Many thanks to Pat and the entire Slackware Team for adding the alsa software in /extra/pure-alsa-system! Very grateful.
Likewise, I have used /extra/pure-alsa-system since it was introduced and have experienced no problems with it. I think its great that pulseaudio doesn't have to be a decisive issue with Slackware.
Sure. My point was that the pulseaudio implementation was never a big deal to begin with. But of course, it's really nice that there is now an official way to get a pure-alsa system.
Sure. My point was that the pulseaudio implementation was never a big deal to begin with.
This is exactly what I was doing before the pure-alsa-system was implemented. I did see some people who had difficulty doing this on their own though and its good they have an easy way to accomplish this now.
Question: Alien BoB's VLC package, for instance, will likely have to be rebuilt without pulse, then? (I don't use pulse because I do a lot with computer music. I realize I'm not normal and will likely have to tweak things myself.) If it's too much bother, I'll likely do what I did for 14.2 and have pulse set to never start.
Question: Alien BoB's VLC package, for instance, will likely have to be rebuilt without pulse, then? (I don't use pulse because I do a lot with computer music. I realize I'm not normal and will likely have to tweak things myself.) If it's too much bother, I'll likely do what I did for 14.2 and have pulse set to never start.
I really doubt that a modern VLC, Chromium or even Firefox can be built without PulseAudio support.
And makes sense that.
Why they should mess with a full handling of the audio mixers and to handle every audio input or output, when then just can use the standard input and output given by PulseAudio? Also, ALSA is Linux-only, then for Windows or *BSD they should chose another paths. PulseAudio works everywhere.
------------------------------------------------------
And speaking of "computer music", I have a friend who's that type of audiophile who considers an insult for his ears to listen to something else than a vacuum tubes based power amp, and that a Beethoven Symphony stored in a MP3 is plain and simple a sacrilege.
He talks about real-time kernels, that the variable clock on CPUs should be avoided at all costs, and other things like this.
However, looks like he is not so impressed about PulseAudio "latency" and when someone asks, he says that that is just a matter of configuration.
Last edited by Darth Vader; 08-19-2018 at 09:37 AM.
From what I understand of Alien Bob's vlc.slackbuild, you can build vlc without PulseAudio.
Code:
# Explicitly enable pulseaudio or it will not be picked up by ffmpeg:
if pkg-config --exists libpulse 2>/dev/null ; then
USE_PULSE="--enable-libpulse"
else
USE_PULSE=""
fi
So if the system doesn't have libpulse, vlc is build without PulseAudio.
So, if I am interpreting this thread - the next release of Slackware it will be easier to go completely free of pulse-audio? I am intrigued. In principle I am not against pulse-audio , but it just does not seem as mature as ALSA and so if there is a viable way of removing pulse-audio and still being able to use programs such as VLC , etc without any real hassle - I am all for this!
So, if I am interpreting this thread - the next release of Slackware it will be easier to go completely free of pulse-audio? I am intrigued. In principle I am not against pulse-audio , but it just does not seem as mature as ALSA and so if there is a viable way of removing pulse-audio and still being able to use programs such as VLC , etc without any real hassle - I am all for this!
Yes. If you follow the README in /extra/pure-alsa-system it is dead simple to safely remove Pulse Audio and install Alsa. Pat also includes a script to revert to Pulse Audio if you wish to do so.
The purpose of my initial post is not to criticize Pulse Audio(I use Pulse Audio on 80% of my Slackware units), but, rather to celebrate the fact that Pat gives us alternatives for setting up audio on our systems.
back to alsa? what a joke. Attach an HDIM monitor and stream the sound to it.
not possible without restarting a lot of things with alsa? ont a use case for you?
seriously, I do not know how those people that claim that pulse does not work for them have fucked up their system, maybe some manual configuration, than omg it does not work, back to alsa, and being happy that the one app they use produces some sound.
seriously, the whole world is using pulse without too many problems, and here we have a hand full of people not being able to do it because of ????
To the OP (and the others here to validate the value of the thread):
I have a t410s, so basically the same hardware, with Slackware 14.2 installed, 64 bit, no problem with sound at all in its default installation.
So this is obvious just an other self produced problem on the keyboard report rather than a alsa free system solved something that was never a problem.
Yes. If you follow the README in /extra/pure-alsa-system it is dead simple to safely remove Pulse Audio and install Alsa. Pat also includes a script to revert to Pulse Audio if you wish to do so.
The purpose of my initial post is not to criticize Pulse Audio(I use Pulse Audio on 80% of my Slackware units), but, rather to celebrate the fact that Pat gives us alternatives for setting up audio on our systems.
I have tried pulse-audio but I rather prefer ALSA, but what irks me is the outright forcing to use a certain audio server over another, which that I am against. Just like a certain other init system that shall not be named. In principle I am not against it, but if said project just outright decides it will be the requirement because reasons - well....
I have tried pulse-audio but I rather prefer ALSA, but what irks me is the outright forcing to use a certain audio server over another, which that I am against.
I believe this is why Pat has added /extra/pure-alsa-system to slackware-current and the upcoming Slackware 15.0. Pulse Audio is now the default sound system on Slackware-current, but, any end user can now switch to Alsa if they wish to do so. I am grateful that Pat gives us options with system set-up.
It is interesting to note that I own two identical T410 Thinkpads. One unit works flawlessly with Pulse Audio on Slackware 14.2(full install) and Slackware64-current. The other unit set-up in a similar fashion has difficulty with Pulse Audio. PEBKAC (problem exists between keyboard and computer) isn't the issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.