From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001766]: jackd : ALSA: cannot set period size to 1024 frames for capture
Date: Sat, 21 Jan 2006 05:25:02 +0100 [thread overview]
Message-ID: <7aedcab49fcc6fca348b2f3afc681614@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1766>
======================================================================
Reported By: Raymond
Assigned To: mjander
======================================================================
Project: ALSA - driver
Issue ID: 1766
Category: PCI - au88x0
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Distribution:
Kernel Version:
======================================================================
Date Submitted: 01-21-2006 05:02 CET
Last Modified: 01-21-2006 05:25 CET
======================================================================
Summary: jackd : ALSA: cannot set period size to 1024 frames
for capture
Description:
snd_pcm_hw_params_get_channels_max() return 4 for capture stream
static struct snd_pcm_hardware snd_vortex_playback_hw_adb = {
.info =
(SNDRV_PCM_INFO_MMAP | /* SNDRV_PCM_INFO_RESUME | */
SNDRV_PCM_INFO_PAUSE | SNDRV_PCM_INFO_INTERLEAVED |
SNDRV_PCM_INFO_MMAP_VALID),
.formats =
SNDRV_PCM_FMTBIT_S16_LE | SNDRV_PCM_FMTBIT_U8 |
SNDRV_PCM_FMTBIT_MU_LAW | SNDRV_PCM_FMTBIT_A_LAW,
.rates = SNDRV_PCM_RATE_CONTINUOUS,
.rate_min = 5000,
.rate_max = 48000,
.channels_min = 1,
#ifdef CHIP_AU8830
.channels_max = 4,
#else
.channels_max = 2,
#endif
.buffer_bytes_max = 0x10000,
.period_bytes_min = 0x1,
.period_bytes_max = 0x1000,
.periods_min = 2,
.periods_max = 32,
};
static int
vortex_adb_allocroute(vortex_t * vortex, int dma, int nr_ch, int dir, int
type)
{
stream_t *stream;
int i, en;
if ((nr_ch == 3)
|| ((dir == SNDRV_PCM_STREAM_CAPTURE) && (nr_ch > 2)))
return -EBUSY;
therefore jackd fail with "ALSA: cannot set period size to 1024 frames for
capture"
jackd -d alsa hw:0 -S
jackd 0.100.9
...
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|16bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
no message buffer overruns
======================================================================
----------------------------------------------------------------------
rlrevell - 01-21-06 05:25
----------------------------------------------------------------------
I don't understand - where is the bug? In JACK or the driver?
Issue History
Date Modified Username Field Change
======================================================================
01-21-06 05:02 Raymond New Issue
01-21-06 05:25 rlrevell Note Added: 0007735
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-01-21 4:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 4:25 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 1:24 [ALSA - driver 0001766]: jackd : ALSA: cannot set period size to 1024 frames for capture bugtrack
2006-06-28 2:58 bugtrack
2006-05-26 6:22 bugtrack
2006-05-24 11:38 bugtrack
2006-03-03 21:36 bugtrack
2006-03-03 9:49 bugtrack
2006-03-03 8:02 bugtrack
2006-03-03 7:41 bugtrack
2006-03-03 7:12 bugtrack
2006-03-01 6:55 bugtrack
2006-02-28 6:08 bugtrack
2006-02-27 18:15 bugtrack
2006-02-27 8:30 bugtrack
2006-02-27 4:55 bugtrack
2006-02-27 4:14 bugtrack
2006-02-27 4:07 bugtrack
2006-02-18 7:34 bugtrack
2006-02-04 5:14 bugtrack
2006-01-31 12:49 bugtrack
2006-01-28 1:23 bugtrack
2006-01-24 10:25 bugtrack
2006-01-23 9:36 bugtrack
2006-01-21 6:59 bugtrack
2006-01-21 6:36 bugtrack
2006-01-21 4:02 bugtrack
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=7aedcab49fcc6fca348b2f3afc681614@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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