From: Florian Schmidt <mista.tapas@gmx.net>
To: Florian Schmidt <mista.tapas@gmx.net>
Cc: Jack O'Quin <joq@io.com>, alsa-devel@lists.sourceforge.net
Subject: Re: CVS commit [0.99.11] ALSA playback latency patch
Date: Thu, 18 Nov 2004 14:52:04 +0100 [thread overview]
Message-ID: <20041118145204.4c000eca@mango.fruits.de> (raw)
In-Reply-To: <20041118143600.59ca28b1@mango.fruits.de>
On Thu, 18 Nov 2004 14:36:00 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:
> On 17 Nov 2004 23:09:24 -0600
> "Jack O'Quin" <joq@io.com> wrote:
>
> >
> > I should have made it clear that this is a JACK update, not ALSA. :-)
>
> Frankly i must say, that i do not quite understand what this patch changes.
>
> from jackd 0.99:
>
> -p, --period Frames per period (default: 1024)
> -n, --nperiods Number of periods in hardware buffer (default: 2)
>
> --nperiods never set the buffer size. This was always done by --period. Care
> to elaborate? I have the feeling i must be blindstruck. Also i think the
> 0.99 behaviour is perfectly allright.
arr, well i think i got it now. You are talking about the _total_ buffer
size, right? Up to now it was determined by --nperiods * --periods. But
since some soundcards don't support these exact buffer sizes, you changed it
so that the total buffer size is big enough that --nperiods * --periods fits
into it, right?
flo
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-18 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 5:04 CVS commit [0.99.11] ALSA playback latency patch Jack O'Quin
2004-11-18 5:09 ` Jack O'Quin
2004-11-18 13:36 ` Florian Schmidt
2004-11-18 13:52 ` Florian Schmidt [this message]
2004-11-18 17:20 ` [Alsa-devel] " Jack O'Quin
2004-11-18 19:11 ` Takashi Iwai
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=20041118145204.4c000eca@mango.fruits.de \
--to=mista.tapas@gmx.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=joq@io.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