Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Zhao <linuxzsc@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
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: Sun, 15 Mar 2009 18:38:13 +0800	[thread overview]
Message-ID: <4e090d470903150338q74cd3538xe908bc3d7df9a8de@mail.gmail.com> (raw)
In-Reply-To: <49AC0232.1060909@ladisch.de>

On Mon, Mar 2, 2009 at 11:58 PM, Clemens Ladisch <clemens@ladisch.de> wrote:
> Richard Zhao wrote:
>> 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,
>
> Did you install your own constraint rules, as described in section
> "Constraints" of "Writing an ALSA Driver"?
>
>
> Best regards,
> Clemens
>

Sure I can add rules. but the rules will be checked as hw_param. If
hw_param failed, does alsalib convert fmt or sample rate
automatically?

For example:
One codec, support:
44.1k : s8 s16 s24 s32
96k:  s24 s32

When user try to play s8/s16 96k audio file, hw_param will fail. I
don't know, how to let alsalib convert s8/s16 to s32 or convert 96k to
44.1k automatically?

Thanks
Richard

  reply	other threads:[~2009-03-15 10:38 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
2009-03-02 15:58   ` Clemens Ladisch
2009-03-15 10:38     ` Richard Zhao [this message]
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=4e090d470903150338q74cd3538xe908bc3d7df9a8de@mail.gmail.com \
    --to=linuxzsc@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox