Re: I think that the current state of ALSA is poor

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



wempwer@xxxxxxxxx wrote:
> 1) my work computer with Ubuntu has HDA Intel PCH soundcard
> installed. Moving PCM slider in alsamixer or muting it has no
> effect.

Apparently, on this hardware, whatever output you're using is not
affected by that mixer control.

> Moreover, manipulating volume slider inside pavucontrol results in
> higher volume than when Master and Speakers are set to maximum in
> alsamixer alone.

PulseAudio can increase the volume in software.  However, this does not
increase the possible range of audio samples, so if your original data
is loud enough, you get clipping.

> 2) my home laptop HP Pavilion DV6 3015ew with Slackware has HDA ATI SB
> soundcard installed. Here, moving PCM slider in alsamixer changes
> volume correctly but PCM cannot be muted.

Apparently, this hardware does not implement muting for this stream.

> Why is PCM observed behavior not coherent between 1) and 2) ?

An HDA system consists of two parts, the HDA controller and the HDA
codec.  The "Intel PCH" and "ATI SB" chips are the controllers; the
codecs are different.  (And even if two computers happen to have the
same codec, they are likely to be wired up differently.)

> 3) my Toshiba n550d netbook has 2 soundcards - alsamixer shows
> "HD-Audio Generic" and "HDA ATI SB".

The "Generic" device is the HDMI output of the GPU.

> What is bad is that the first card is set as default

The first card is the one that happens to be found first when
enumerating the devices on the PCI bus.

If you use PulseAudio, you can specifiy which card to use.

If you use only ALSA, use something like this in /etc/asound.conf or in
your ~/.asoundrc:

  defaults.pcm.card "SB"
  defaults.ctl.card "SB"

> I wasn't able to use it with my in-built mic until I set capture
> device to "OSS: /dev/dsp" in Linphone.

The OSS emulation just redirects /dev/dsp to the default ALSA input
device.

> 6) A few months ago I got myself Creative bluetooth speakers. I have
> the following in my ~/.asoundrc.conf:
> ...
> pcm.!default { ...
>
> Some programs such as xmms2 can pick these settings correctly and play
> music on speakers, but some others such as mplayer can't do that and I
> always have to pass "-ao alsa:device=bluetooth"

mplayer uses the "default" device by default, unless you have changed
this in ~/.mplayer/config.

> What's even more, I can't play sound in 2 programs simultaneously

Because your redefinition of the "default" device bypasses PulseAudio.


Regards,
Clemens

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user




[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux