From: Takashi Iwai <tiwai@suse.de>
To: Richard Zhao <linuxzsc@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: How to tell user level hardware not support a certain format in a certain sample rate
Date: Mon, 02 Mar 2009 15:12:40 +0100 [thread overview]
Message-ID: <s5hwsb8c8tj.wl%tiwai@suse.de> (raw)
In-Reply-To: <4e090d470903020604h27ce2ce8l47f996edc9764ada@mail.gmail.com>
At Mon, 2 Mar 2009 22:04:04 +0800,
Richard Zhao wrote:
>
> 2009/2/23 Richard Zhao <linuxzsc@gmail.com>:
> > Hi,
> >
> > runtime->hw.rates and runtime->hw.formats indicate the rate and
> > formats hardware can support, so the user level plugins can
> > auto-convert the audio data. But hardware may not support a certain
> > combin of sample rate and format, and will cause hw_parm fail. In such
> > case, plugin auto-convert will not work.
> > How can I let userlevel know the failure conbin, so let auto-convert work?
> >
> > Thanks
> > Richard
> >
>
> Anybody can do me a favor please?
Could you be more specific, e.g. test cases with numbers?
There are some known problems with the configuration space reduction,
and I think your problem is one of them, though. Basically, the
config space is reduced one after one for each
snd_pcm_hw_params_refine(), and the existence of a singular point
makes hard to pick up the right point.
If the problem is such one, currently there is no elegant solution.
Takashi
next prev parent reply other threads:[~2009-03-02 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 7:02 How to tell user level hardware not support a certain format in a certain sample rate Richard Zhao
2009-03-02 14:04 ` Richard Zhao
2009-03-02 14:12 ` Takashi Iwai [this message]
2009-03-02 15:58 ` Clemens Ladisch
2009-03-15 10:38 ` Richard Zhao
2009-03-16 8:54 ` Clemens Ladisch
2009-03-17 6:57 ` Richard Zhao
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=s5hwsb8c8tj.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linuxzsc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox