[SOLVED] Alien Bob's Chromium package no pulseaudio?

Daedra · 07-28-2016, 05:25 PM

This is not a big deal but I noticed today while I was running Eric's Chromium binary for 14.2 that the audio is piping out to alsa and not pulseaudio. I looked at the SlackBuild and it has support for pulseaudio. I rebuilt Chromium from the SlackBuild without changing anything and now the audio is being piped through pulseaudio. I've attached two screenshots so you can see what I mean. Is this normal for the binary, I am just curious?

GazL · 07-28-2016, 06:12 PM

Can't speak for chromium, but google's google-chrome binary uses the pulse alsa-plugin too.

Daedra · 07-28-2016, 06:22 PM

Quote:

Originally Posted by GazL

Can't speak for chromium, but google's google-chrome binary uses the pulse alsa-plugin too.

I just found it odd because Eric's binaries are built from his SlackBuild so if hes building on 14.2 pulseaudio should be picked during build time since it is in his script.

kingbeowulf · 07-28-2016, 07:23 PM

Alien Bob's Chromium binary here plays via the ALSA plugin on several sites - even Youtube (HTML5). FF plays some via ALSA and on some via pulseaudio. Weird that HTML5 video plays via PA in FF but via ALSA plugin in chromium.

This doesn't seem to effect multiple streams: I can play several streams via chromium and/or FF simultaneously regardless of the plugin. I think that is telling me that PA is still managing the audio streams.

Emerson · 07-28-2016, 07:33 PM

ALSA can play multiple streams simultaneously no problem.

kingbeowulf · 07-28-2016, 08:05 PM

Quote:

Originally Posted by Emerson

ALSA can play multiple streams simultaneously no problem.

Yes it can, but you have to set up a proper $HOME/.asoundrc or /etc/asound.conf if your soundcard does not have a hardware mixer (such as SoundBlaster). Most motherboard audio (realtek, Intel, etc) need to have software mixing set up in soeftware. This has been discussed at length in this forum.

the3dfxdude · 07-28-2016, 08:45 PM

Quote:

Originally Posted by kingbeowulf

Yes it can, but you have to set up a proper $HOME/.asoundrc or /etc/asound.conf if your soundcard does not have a hardware mixer (such as SoundBlaster). Most motherboard audio (realtek, Intel, etc) need to have software mixing set up in soeftware. This has been discussed at length in this forum.

I don't think that has been true for about the past 10+ years.

http://alsa.opensrc.org/Dmix

Quote:

NOTE: For ALSA 1.0.9rc2 and higher you don't need to setup dmix for analogue output. Dmix is enabled by default for soundcards which don't support hardware mixing. You still need to set it up for digital outputs.

But what do I know. I've never really remember having any problem that required a custom config with Alsa. There could have been other problems all along.

dugan · 07-28-2016, 10:50 PM

Quote:

Originally Posted by kingbeowulf

Yes it can, but you have to set up a proper $HOME/.asoundrc or /etc/asound.conf if your soundcard does not have a hardware mixer (such as SoundBlaster). Most motherboard audio (realtek, Intel, etc) need to have software mixing set up in soeftware. This has been discussed at length in this forum.

That hasn't been true for a decade. The correct defaults for playing multiple streams are set by default, in /usr/share/alsa/alsa.conf.

The actual discussions have usually been started by people who wrote their own .asoundrc files and accidentally disabled that.

kingbeowulf · 07-28-2016, 11:17 PM

Well, then perhaps I have always run on decades old hardware; or crappy sound cards/drivers. 14.x was better, but not perfect. The defaults have rarely worked here without hardware mixing capability, not to mention HDMI and multiple microphone input. Getting Steam and Mumble to play nice was exciting.

Alien Bob · 07-29-2016, 02:52 AM

FYI,
I do not compile every package for every release of Slackware. I only compile a package for a newer Slackware release if the package is broken.
The chromium package is built on Slackware 14.1 and made available for 14.2 and -current too. This means that it is not supporting PulseAudio. I do not consider that "broken".

Daedra · 07-29-2016, 03:54 AM

Quote:

Originally Posted by Alien Bob

FYI,
I do not compile every package for every release of Slackware. I only compile a package for a newer Slackware release if the package is broken.
The chromium package is built on Slackware 14.1 and made available for 14.2 and -current too. This means that it is not supporting PulseAudio. I do not consider that "broken".

I hope that wasn't directed at me. I didn't mean to imply that anything was "broken" and didn't use the word broken in my post. I was just curious to know and your explanation makes sense. Sorry if I offended you, I didn't mean any disrespect. I appreciate all the EXTREMELY hard work you do.

Alien Bob · 07-29-2016, 03:57 AM

Quote:

Originally Posted by Daedra

I hope that wasn't directed at me. I didn't mean to imply that anything was "broken" and didn't use the word broken in my post. I was just curious to know and your explanation makes sense. Sorry if I offended you, I didn't mean any disrespect. I appreciate all the EXTREMELY hard work you do.

Hi Daedra, I did not take offense at all. The quotes surrounding "broken" were only meant to illustrate that I do not consider a lack of PA support as something which is broken. After all, audio still works, it's just using ALSA.