[LAU] Internal speaker set as default playback, not my usb soundcard.

[Andrew C]

Excellent, thanks for that tip, Phillip! Got it fixed now.

Put "autospawn = no" into $HOME/.config/pulse/client.conf, killed PA as you
suggested and everything worked as expected, alsamixer controls the volume
(.asoundrc works perfectly again) and mplayer/flash/MOCP plays through my
usb card.

Andrew.


On Tue, Aug 19, 2014 at 2:47 PM, Philipp Überbacher <murks at tuxfamily.org>
wrote:

> On Tue, 19 Aug 2014 13:48:22 +0100
> Andrew C <countfuzzball at gmail.com> wrote:
>
> > Speaking of .asoundrc, I had set up my like so (which predictably no
> > longer works, even though my usb card is still at index 0):
> >
> > pcm.!default {
> >     type            plug
> >     slave.pcm       "softvol"   #make use of softvol
> > }
> >
> > pcm.softvol {
> >     type            softvol
> >     slave {
> >         pcm         "dmix"      #redirect the output to dmix (instead
> > of "hw:0,0")
> >     }
> >     control {
> >         name        "PCM"       #override the PCM slider to set the
> > softvol volume level globally
> >         card        0
> >     }
> > }
> >
> > I doubt this would cause a mess up (even so, even *that* is no longer
> > working, my soundcard ignores any changes made by alsamixer).
> >
> > At this point, would I guess there's some pulseaudio weirdness
> > happening? Any ideas how I can use alsa straight up, unless I've
> > somehow been using a pulseaudio-alsa wrapper this entire time.
> >
> > To my mind, it makes absolutely no sense why stuff would be playing
> > out of Card 1, and not Card 0. Or at least why that has suddenly
> > changed to be the default with this upgrade.
> >
> > Andrew.
>
> I'm not sure whether you get direct alsa access while PA is running.
>
> You could disable pulseaudio and try again. I have configured PA
> so that it is only ever started manually by me and I simply use
> 'pulseaudio --start' and 'pulseaudio --kill'. However, depending on
> your distributions setup it might be a PITA to stop PA and keep it
> stopped. You can use 'pulseaudio --check' to see whether it runs, it
> returns 0 if it runs, 1 otherwise. Or just use 'pulseaudio --kill' and
> see whether it throws an error or succeeds because something started PA
> again. This can happen because PA is set to respawn or because some
> program started PA on startup. That's a PITA I don't want to deal with,
> hence my entirely manual setup.
>
> Regards,
> Philipp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20140819/fd43a1d3/attachment.html>