From: "Dominic Sacré" <dominic.sacre@gmx.de>
To: alsa-devel@alsa-project.org
Subject: snd-fireworks requires larger period sizes than FFADO
Date: Sun, 22 Nov 2015 01:20:47 +0100 [thread overview]
Message-ID: <56510A5F.4080004@gmx.de> (raw)
Hi,
I'm trying to use an Echo AudioFire 4 with the snd-fireworks driver.
With FFADO the device works reasonably well at a period size of
64 samples (on a PREEMPT_RT kernel), whereas with snd-fireworks the
lowest possible period size seems to be 256 samples.
This is what JACK says when I try to start it with a period size of 128
samples:
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: cannot set period size to 128 frames for capture
The lowest achievable analog roundtrip latency seems to be around 19ms
(at 2x256 frames), as opposed to 8.3ms with FFADO (at 2x64). Are there
any known limitations of the snd-fireworks driver in this regard?
Thanks,
Dominic
next reply other threads:[~2015-11-22 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 0:20 Dominic Sacré [this message]
2015-11-23 10:40 ` snd-fireworks requires larger period sizes than FFADO Clemens Ladisch
2015-12-01 14:31 ` Stefan Richter
2015-12-01 17:15 ` Clemens Ladisch
2015-12-02 0:31 ` Takashi Sakamoto
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=56510A5F.4080004@gmx.de \
--to=dominic.sacre@gmx.de \
--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 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.