From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Unable to find an usable access for 'default'
Date: Mon, 09 Jul 2007 08:51:35 +0200 [thread overview]
Message-ID: <1183963895.22813.1199147561@webmail.messagingengine.com> (raw)
In-Reply-To: <468EC305.8080301@freescale.com>
Timur Tabi wrote:
> 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?
No, but the ALSA framework does all mmap stuff for you if it knows what
type of memory you're using for the buffer, i.e., when you're using the
snd_pcm_lib_* memory management functions.
> > 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?
This is possible. Try using aplay with a .wav file that uses a sample
format supported by the hardware.
> I thought ALSA always did sample rate conversion.
It does when using the "default" device, but it's possible that
alsaplayer tries to use some "hw" device that does not.
HTH
Clemens
next prev parent reply other threads:[~2007-07-09 6:51 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
2007-07-09 6:51 ` Clemens Ladisch [this message]
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=1183963895.22813.1199147561@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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