From: PgmHelmi <pgmhelmi@tele2.at>
To: alsa-devel@alsa-project.org
Subject: Re: Different returns from snd_pcm_readi() in differen versions from ALSA driver
Date: Thu, 11 Nov 2010 09:33:04 +0100 [thread overview]
Message-ID: <4CDBAA40.3060603@tele2.at> (raw)
In-Reply-To: <4CD81FEB.3090100@tele2.at>
Hi!
Has at least somebody a hint for us, where we can find a solution for
our problem? We searched already in mailing list and internet but could
not found something fitting. And the list of release changes is very
long and descriptions are not always very clear.
Kind regards
PgmHelmi schrieb:
> Hi!
>
> We had to write a driver for audio playing and recording on Linux thin
> clients. We are using ALSA driver + libs for it, but we are
> depending on the versions which are installed on them.
>
> We have a certain buffer size for this and set the corresponding
> hardware and software parameters and call for capture
> snd_pcm_readi(). The function returns the read buffer frames. In most
> versions this is equal to the number of wanted passed frames, but
> not in all. We have ALSA driver version 1.0.15 and 1.0.22.1 where the
> returned number is the same. But we have also version 1.0.21
> where the returned number is the period size or a multiple of it.
>
> So conclusion is, that something was changed between 1.0.15 and 1.0.21
> and changed back till 1.0.22.1. As we are dependent on the
> behaviour of the former and newer version, my question is, if there is a
> possibility to get the same behaviour in version 1.0.21?
>
> Thank you for your answer in advance!
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
prev parent reply other threads:[~2010-11-11 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 16:06 Different returns from snd_pcm_readi() in differen versions from ALSA driver PgmHelmi
2010-11-11 8:33 ` PgmHelmi [this message]
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=4CDBAA40.3060603@tele2.at \
--to=pgmhelmi@tele2.at \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).