From: Takashi Iwai <tiwai@suse.de>
To: Jack O'Quin <joq@io.com>
Cc: "Asbjørn Sæbø" <asbjs@stud.ntnu.no>, alsa-devel@lists.sourceforge.net
Subject: Re: Lowest latency: JACK, or ALSA directly?
Date: Thu, 18 Nov 2004 13:38:33 +0100 [thread overview]
Message-ID: <s5hvfc3qqly.wl@alsa2.suse.de> (raw)
In-Reply-To: <87d5ybvria.fsf@sulphur.joq.us>
At 17 Nov 2004 20:07:57 -0600,
Jack O'Quin wrote:
>
> > Untested as usual :)
>
> I'll try it here with my Delta-66.
>
> That won't test any of the strange cases where -nperiods=2 but the
> device actually requires a three-period buffer. Which cards do you
> know of that are affected by this?
rme32, rme96 and korg1212 have the fixed buffer size.
ymfpci has 3 periods as minimum, too.
> > (BTW, the jack code is still based on the older ALSA API.
> > Is this intentional?)
>
> It was intentional last year so JACK would work with all ALSA
> versions. A patch was recently submitted to use the newer interfaces.
> The consensus on jackit-devel was that it is time to do that now, but
> the patch has not yet been committed to CVS.
>
> (Patch follows for your review...)
> > [2. text/x-patch; 2004-11-02.0.patch]...
> @@ -620,19 +621,15 @@
(snip)
> + err = snd_pcm_hw_params_get_period_size (
> + driver->playback_hw_params, &p_period_size, &dir);
> + err = snd_pcm_hw_params_get_periods (
> + driver->playback_hw_params, &p_nfragments, &dir);
> + err = snd_pcm_hw_params_get_format (
> + driver->playback_hw_params, &(driver->playback_sample_format));
> + snd_pcm_access_t access ;
^^^ the variable declaration should be moved in the beginning of the
block.
Otherwise it looks fine.
You could check the return value of snd_pcm_hw_params_get_*, but it's
usually ok.
Takashi
-------------------------------------------------------
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 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 14:41 Lowest latency: JACK, or ALSA directly? Asbjørn Sæbø
2004-11-11 15:11 ` Jack O'Quin
2004-11-12 9:04 ` Asbjørn Sæbø
2004-11-12 16:42 ` Jack O'Quin
2004-11-12 17:01 ` Takashi Iwai
2004-11-12 17:19 ` Jack O'Quin
2004-11-17 14:55 ` Takashi Iwai
2004-11-17 17:32 ` Jack O'Quin
2004-11-17 18:28 ` Takashi Iwai
2004-11-17 19:41 ` Takashi Iwai
2004-11-18 2:07 ` Jack O'Quin
2004-11-18 12:38 ` Takashi Iwai [this message]
2004-11-11 15:34 ` Paul Davis
2004-11-12 9:11 ` Asbjørn Sæbø
2004-11-12 14:47 ` Gilles Degottex
2004-11-12 15:28 ` Giuliano Pochini
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=s5hvfc3qqly.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=asbjs@stud.ntnu.no \
--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