From: Cournapeau David <cournape@atr.jp>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: ALSA LIST <alsa-devel@lists.sourceforge.net>
Subject: Re: Question regarding period/buffer and error handling
Date: Mon, 31 May 2004 10:04:38 +0900 [thread overview]
Message-ID: <40BA84A6.30406@atr.jp> (raw)
In-Reply-To: <Pine.HPX.4.33n.0405281746010.24462-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
>Cournapeau David wrote:
>
>
>> My second problem is related to snd_card_next: If the card value
>>returned by snd_card_next is different from -1, does that always mean
>>than a alsa audio device is present on the system ?
>>
>>
>
>It means that same kind of device with an ALSA driver is present.
>This does not mean that you'll be able to play PCM data to it. And
>there may be software devices available.
>
>
>
>>Is it the best method to probe a soundcard with alsa support?
>>
>>
>
>snd_card_next() and snd_ctl_pcm_next_device() will give you a list of
>hardware devices only.
>
>Usually, you should use the device named "default" and let the user
>allow to specify another device name.
>
>
>
Ok, that's what I thought reading the different sources I checked,
concerning the device name. But I am still a bit confused how to probe a
soundcard to play a pcm stream to it: what should I do after having
found an hardware device with snd_card_next ?
Is there always a "default" name ? Or is it user dependant ?
cheers,
David
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
prev parent reply other threads:[~2004-05-31 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 1:34 [alsa-dev]Question regarding period/buffer and error handling Cournapeau David
2004-05-28 7:02 ` Måns Rullgård
2004-05-28 8:00 ` Question " Cournapeau David
2004-05-28 8:22 ` Måns Rullgård
2004-05-28 15:52 ` Clemens Ladisch
2004-05-31 1:04 ` Cournapeau David [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=40BA84A6.30406@atr.jp \
--to=cournape@atr.jp \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
/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.