From: Giuliano Pochini <pochini@shiny.it>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: snd_pcm_hw_params_get_*() without snd_pcm_open(
Date: Mon, 28 Apr 2003 12:37:21 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20030428123721.pochini@shiny.it> (raw)
In-Reply-To: <Pine.LNX.4.44.0304281009570.1603-100000@pnote.perex-int.cz>
On 28-Apr-2003 Jaroslav Kysela wrote:
> On 27 Apr 2003, Giuliano Pochini wrote:
>
>> I need to read the properties of a pcm device, but snd_pcm_open() blocks
>> or exits with an error if something is using that device. Is there any
>> workaround ?
>
> No, the characteristic of a PCM device is dynamic (might be changed during
> runtime)
Ah, this is a good news :) My card has digital i/o, but the number of
channels changes when the user switches between S/PDIF and ADAT. Now I
can fix it properly.
> thus it's not useful to obtain this information in another way.
> Also, I think that most of applications want to be clever than user,
> simply use device passed by user and try work with it.
I'm writing a mixer. I need some infos I cannot get from the ctl
interface (eg. # of channels). I can register an "info" ctl to pass
the data I need to userspace, but I don't like that hack. And I don't
like to store a list of capabilities of each card inside the mixer.
Any hints ?
Bye.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-04-28 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 22:46 snd_pcm_hw_params_get_*() without snd_pcm_open() ? Giuliano Pochini
2003-04-28 8:12 ` Jaroslav Kysela
2003-04-28 10:37 ` Giuliano Pochini [this message]
2003-04-28 15:47 ` Unusual pcm contraint Giuliano Pochini
2003-04-28 16:00 ` Jaroslav Kysela
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=XFMail.20030428123721.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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.