[Thinlinc-technical] multiple and/or non-default sound card in terminal

David Edmondson dme at dme.org
Tue Jan 29 14:59:33 CET 2013


On Tue, Jan 29 2013, David Edmondson wrote:
> On Tue, Jan 29 2013, Pierre Ossman wrote:
>> On Tue, 29 Jan 2013 12:58:03 +0000
>> David Edmondson <dme at dme.org> wrote:
>>
>>> 
>>> Does the thinlinc PulseAudio server only use the zeroth ALSA device?
>>> With my on-board audio disabled, ALSA finds only the USB audio as device
>>> 1, but the thinlinc client/server doesn't use it.
>>
>> It uses the default device, which might not even be a physical sound
>> card. So no, not "hw:0".
>
> Understood.
>
>> I have no idea why your USB card isn't becoming the default one under
>> those circumstances. Does aplay work?
>
> No, it complains "cannot find card 0". This means that it's an ALSA
> issue?

Debian includes the following in /etc/modprobe.d/alsa-base.conf:

# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2

If I remove this, rmmod snd-usb-audio, modprobe snd-usb-audio then the
USB card appears as device 0. Restarting the thinlinc client allows the
thinlinc server to see it now, and everything works well.

That seems like a usable fix - if the terminal doesn't have a USB sound
card things should work much as before. Thanks for your help in figuring
it out.

I'm still puzzled as to why card 1 wasn't usable as the default when
it's the only card.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.cendio.se/pipermail/thinlinc-technical/attachments/20130129/dfe375b5/attachment.bin>


More information about the Thinlinc-technical mailing list