From: thomas schorpp <thomas.schorpp@googlemail.com>
To: Ekiga development mailing list <ekiga-devel-list@gnome.org>,
alsa-devel@alsa-project.org
Cc: michel@twinklephone.com
Subject: Re: [Ekiga-devel-list] Pls don't require exclusive Alsa audio device access, use snd_pcm_dmix_open ()
Date: Wed, 28 Nov 2007 19:16:07 +0100 [thread overview]
Message-ID: <474DB067.1050008@googlemail.com> (raw)
In-Reply-To: <s5hir3mgx1m.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Wed, 28 Nov 2007 17:01:47 +0100,
> thomas schorpp wrote:
>>> +1 Dmix should not be enforced... this can be handled at a lower
>>> level.... e.g. with dmix configured in alsa config or by using
>>> pulseaudio instead of dmix (my preferred solution so I can switch from
>>> my internal speakers to my usb headset should I plug it in mid-call).
>>>
>>> Col.
>> alsa docs say dmix config files are no longer neccessary?
>
> The behavior depends on the name string passed to snd_pcm_open().
> If you open the PCM with "default", the alsa-lib takes an approriate
> configuration for multi-playback and automatic conversions. But, if
> app opens with other strings like "hw" or "plughw", then it means
> that it's an exclusive access. dmix cannot be involved with that.
>
>
> Takashi
>
thx guys. using the "default" device in ekiga audio device config solved it :)
skype 5218 skype mem CHR 116,24 8292 /dev/snd/pcmC0D0c
skype 5218 skype mem CHR 116,16 8284 /dev/snd/pcmC0D0p
iceape-bi 5277 schorpp 0r CHR 1,3 1107 /dev/null
ekiga 5411 schorpp mem CHR 116,16 8284 /dev/snd/pcmC0D0p
ekiga 5411 schorpp mem CHR 116,24 8292 /dev/snd/pcmC0D0c
ekiga 5411 schorpp 0r CHR 1,3 1107 /dev/null
ekiga 5411 schorpp 63r CHR 116,33 7972 /dev/snd/timer
ekiga 5411 schorpp 64u CHR 116,24 8292 /dev/snd/pcmC0D0c
ekiga 5411 schorpp 67r CHR 116,33 7972 /dev/snd/timer
ekiga 5411 schorpp 68u CHR 116,16 8284 /dev/snd/pcmC0D0p
many thx, Takashi. ALSA rocks!
BTW:
http://www.xs4all.nl/~mfnboer/twinkle/manual.html#sys_audio
"NOTE:The ALSA default device should only be used for the ring tone and/or speaker. It is not recommended to use the ALSA default device for the microphone as it gives poor quality."
this is not the case. fine here.
http://www.xs4all.nl/~mfnboer/twinkle/faq.html#alsa_no_sound
"There can be many reasons why you do not get sound. With ALSA, a common problem is the lack of a proper /etc/asound.conf file. Here is a copy of my asound.conf."
twinkle guys should update their docs.
y
tom
prev parent reply other threads:[~2007-11-28 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <471FE2A7.9080309@googlemail.com>
[not found] ` <47201223.5050304@googlemail.com>
2007-11-28 9:06 ` Pls don't require exclusive Alsa audio device access, use snd_pcm_dmix_open () thomas schorpp
2007-11-28 9:17 ` Jaroslav Kysela
2007-11-28 11:36 ` Colin Guthrie
2007-11-28 16:01 ` [Ekiga-devel-list] " thomas schorpp
2007-11-28 16:22 ` Takashi Iwai
2007-11-28 18:16 ` thomas schorpp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=474DB067.1050008@googlemail.com \
--to=thomas.schorpp@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ekiga-devel-list@gnome.org \
--cc=michel@twinklephone.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.