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.
Of course how stupid I am. But what about support for alsa only? So far it is only version of firefox with sound on non-pulse system. I was expecting to see something difference in ldd for this firefox. Hate pulse-s.
on AlienBob Liveslak. See no pa running. But I am happy to listen to Tycho on youtube. On MX Linux, Porteous - there is no sound in firefox without pulseaudio. On MX Linux forum I found that they use upstream Debian build - and supposedly Debian build does not have direct alsa support. In case of Porteous - it is less clear. Firefox on Porteous without pa has no sound. Now - guys claim Porteous is on top of Slackware. So or Slackware default firefox build lacks alsa support - or Porteous is using custom firefox build - which means it is not quite on top of Slackware. In former case firefox in Liveslak is AlienBob custom build. Complicated. But I really greatly appreciate that I can use firefox on alsa only system. This saves a lot of money - in other case I would have to spend them to buy good audio system - to cover poor pa quality.
FYI, igadoter, pulse is not an audio server. It has no means to interact with audio hardware. It still uses ALSA for that. PA is just a "conductor" for the "symphony" of options and connections. In that it creates considerable latency which really does not affect Playback, only Recording. I Record and Edit so I don't like PA either but it's easy to configure it to "go sit in a corner" even without PipeWire. PipeWire can essentially do all that at low latency and fool apps like Firefox to think PA is being used.
None of them have saved me money, not even ALSA, since I buy audiophile (not to be confused with "audiophool") gear. It would cost around $5000.00 USD to replace my PC audio gear that began 25 years ago... LONG before PA ever existed.
Sorry enorbet, you are not right. If someone has very good audio, or even good audio - there is no difference between PA and pure alsa. But for middle ware one can hear difference - in pa drums and cymbals sound like poured sand. The sound is flat. Someone posted pa was never created with audio quality in mind. Just magical word: server. But even arts (?) KDE 3.5 sound server was better in terms of sound quality. For people who create audio application - pa was a savior from alsa - say audacious still has problems with alsa only audio - but for price of sound quality. And of course pa was forced by the same side of force which pushes now pipewire. Say firefox with support for alsa, pa and pipewire?
You could be right, igadoter, but I don't see how. How does PA have any effect on playback quality? It doesn't control the hardware. It only controls ALSA AFAIK. Actaully that's what pisses me off about Firefox.
I understand why they would prefer to take the easy way out by dropping any concern for what is underneath and only deal with what is above, but the option for ALSA is still there, just disabled! Why would they bother to disable it? Of what value is it to Mozilla? Seems like a mere washing of hands to me, with no concern for those who prefer a more direct approach.
Nevertheless if using PA on "middleware" is somehow reduced quality for you, it seems likely to me you haven't setup ALSA correctly with a solid User .asoundrc.
Also, what do you consider Middleware? Onboard? Personally I consider any onboard audio chipset as substandard if only for the degradation due to noise floor. I see numerous PCI and PCIe semi-pro quality soundcards, new and used, for $30-$100 on sites like eBay. If you prefer external, some decent ones are in similar price ranges. The hardware will make WAY more difference than the software.
Of course how stupid I am. But what about support for alsa only? So far it is only version of firefox with sound on non-pulse system. I was expecting to see something difference in ldd for this firefox. Hate pulse-s.
You need to run ldd on the binary of Firefox, which is located in /usr/lib64/firefox/firefox
Code:
ldd /usr/lib64/firefox/firefox
However, I hate to break it to you, but even Mozilla's official binaries don't show pulse as a shared library, but it's compiled without alsa support.
Package was created using ruario's latest-firefox.sh script (mozilla-firefox-83.0-x86_64-1ro -- yes, I'm out of date, but Firefox is not my primary browser).
Quote:
Originally Posted by igadoter
Sorry enorbet, you are not right. If someone has very good audio, or even good audio - there is no difference between PA and pure alsa. But for middle ware one can hear difference - in pa drums and cymbals sound like poured sand. The sound is flat. Someone posted pa was never created with audio quality in mind. Just magical word: server. But even arts (?) KDE 3.5 sound server was better in terms of sound quality. For people who create audio application - pa was a savior from alsa - say audacious still has problems with alsa only audio - but for price of sound quality. And of course pa was forced by the same side of force which pushes now pipewire. Say firefox with support for alsa, pa and pipewire?
As has been said on other threads, this must be unique to your hardware. I noticed no difference when I moved my htpc from 14.1 to 14.2 (and to -current). I don't use passthrough (although, I did test passthrough and it sounds the same). My htpc is plugged into a relatively high-end Onkyo receiver via HDMI for video and audio. Sounds are all clear and crisp. Explosions are never muddled (and they will shake my house if I have the system turned up loud enough).
However, I hate to break it to you, but even Mozilla's official binaries don't show pulse as a shared library, but it's compiled without alsa support.
This is what I try to understand. For sure I don't run now pa - but I can listen to music in youtube - but so far only in firefox on AlienBob Liveslak. I know ldd output - I did it - in hope I will find a clue why do I have sound in firefox on alsa? Maybe this will help
This is what I try to understand. For sure I don't run now pa - but I can listen to music in youtube - but so far only in firefox on AlienBob Liveslak. I know ldd output - I did it - in hope I will find a clue why do I have sound in firefox on alsa? Maybe this will help
Have you got anything selected under "Firefox Data Collection and Use" in the "Privacy and Security" page of Firefox's "Preferences"?
I didn't touch anything there - firefox reports standard - but perhaps one of extensions I use may spawn RDD process - https everywhere, noscript, ublock origin, privacy badger - I use them to kill google adds on youtube. I like to enjoy non-stop music.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.