From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Possible bug in alsa-lib. snd_pcm_hw_params_get_periods_max() returning 512 instead of 2.
Date: Fri, 11 Jun 2004 16:07:10 +0100 [thread overview]
Message-ID: <40C9CA9E.4030207@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.HPX.4.33n.0406111651150.18177-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
> James Courtier-Dutton wrote:
>
>>I cannot think of any circumstances where doing sample rate conversion
>>(using the "plug:" plugin) would change the amount of periods.
>>Is this a bug in the "plug:" plugin ?
>
>
> Works as designed, I guess. It's the job of the plug plugin to remove
> hardware limitations, just in case an application wants to use 42
> periods.
>
>
> Regards,
> Clemens
>
Ok, well the "design" is not working, because with the "plug:", I still
can only ever get 2 periods. i.e. If I set period_size to 1024, the
buffer_size can only be set to 2048, when in fact I wanted to set the
buffer_size to 8192. i.e. I wanted 8 periods, but "plug:" forced me to
have 2, just like the hardware can do.
So, I conclude from this that the "plug:front" cannot handle a different
amount of periods than "front".
I think that "plug:" works fine for sample rate and sample format
conversions, but seems to fail on the number of periods adaptions.
James
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
prev parent reply other threads:[~2004-06-11 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 11:52 Possible bug in alsa-lib. snd_pcm_hw_params_get_periods_max() returning 512 instead of 2 James Courtier-Dutton
2004-06-10 16:45 ` Clemens Ladisch
2004-06-11 14:26 ` James Courtier-Dutton
2004-06-11 14:54 ` Clemens Ladisch
2004-06-11 15:07 ` James Courtier-Dutton [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=40C9CA9E.4030207@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--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 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.