All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ryan Underwood <nemesis-lists@icequake.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa hw params on SB Pro
Date: Thu, 10 Feb 2005 18:17:25 +0100	[thread overview]
Message-ID: <s5hacqc1gii.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050208053606.GB8616@dbz.icequake.net>

At Mon, 7 Feb 2005 23:36:06 -0600,
Ryan Underwood wrote:
> 
> Hi,
> 
> I seem to have the following problem.  On snd-sb8 with a SBPro (which is
> capable of stereo), the best stereo playback mode is 22KHz - going above
> 22KHz implies that the output will be only one channel.
> 
> If I call snd_pcm_hw_params_set_channels_near with argument of 2
> channels, I get 2 channels as requested.  But then I call
> snd_pcm_hw_params_set_rate_near with argument of 44100, and have 44100
> returned.  Thus I end up with a hwparams that the hardware is not
> capable of.
> 
> Is there a reason the second call returns 44100 instead of 22050?
> Conversely, calling _set_rate_near first and having 44100 returned
> should mean that I only get 1 channel returned from _set_channels_near.
> Isn't this the point of _near functions after all?
> 
> This is with libasound 1.0.8 and drivers version 1.0.8+2 from debian
> (kernel 2.4.27).

Looking at sb8_main.c, the driver seems to try tighter the hw
constraint when channels=2 is set.  If this doesn't work, this might
be a bug of hw params configurator.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-10 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  5:36 alsa hw params on SB Pro Ryan Underwood
2005-02-10 17:17 ` Takashi Iwai [this message]
2005-02-10 17:29   ` Giuliano Pochini
2005-02-14  9:43 ` Clemens Ladisch
2005-02-20  7:19   ` Ryan Underwood

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=s5hacqc1gii.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nemesis-lists@icequake.net \
    /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.