Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Unable to find an usable access for 'default'
Date: Fri, 06 Jul 2007 17:32:37 -0500	[thread overview]
Message-ID: <468EC305.8080301@freescale.com> (raw)
In-Reply-To: <1183719027.2620.1198799059@webmail.messagingengine.com>

Clemens Ladisch wrote:

> ALSA-lib's access type specifies whether to use mmap or not, and whether
> the sample are interleaved or not.  (The SNDRV_PCM_INFO_*INTERLEAVED and
> SNDRV_PCM_INFO_MMAP* flags specify the capabilities of the device.)

Is mmap support ever required?  I don't have that support turned on in my PCM driver, so 
could that cause some ALSA applications to fail to match?

> Look at the values in the snd_pcm_hardware structure and at the
> constraints the driver adds manually, if there are any.

Ok, I think I fixed some issues there, but I'm still having problems.

I think part of the problem is that I'm telling ALSA that I only support these sample 
rates: 192000, 96000, 64000, 48000, 32000, and 16000.  For playback, I'm using alsaplayer 
to play an MP3.  Could it be that alsaplayer is picking a sample rate like 44100 and since 
it doesn't find a match, it's failing?  I thought ALSA always did sample rate conversion. 
  Is that not true?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-07-06 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 22:19 Unable to find an usable access for 'default' Timur Tabi
2007-07-04  6:34 ` Clemens Ladisch
2007-07-05 12:44   ` Timur Tabi
2007-07-06 10:50     ` Clemens Ladisch
2007-07-06 22:32       ` Timur Tabi [this message]
2007-07-09  6:51         ` Clemens Ladisch
2007-07-09 21:02           ` Timur Tabi
2007-07-10  6:29             ` Clemens Ladisch

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=468EC305.8080301@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=cladisch@fastmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox