From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001724]: simple PCM helper function
Date: Tue, 31 Jan 2006 10:26:23 +0100 [thread overview]
Message-ID: <bf566c7e354e89b1960ecfcea21c6adb@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1724>
======================================================================
Reported By: Raymond
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 1724
Category: 0_general
Reproducibility: always
Severity: block
Priority: normal
Status: new
======================================================================
Date Submitted: 01-07-2006 05:10 CET
Last Modified: 01-31-2006 10:26 CET
======================================================================
Summary: simple PCM helper function
Description:
/cvs/alsa-lib/test/pcm_min
ALSA lib pcm.c:7127:(snd_pcm_set_params) Unable to set buffer time
(latency) 500000 for PLAYBACK: Invalid argument
Playback open error: Invalid argument
sound card is au8830, the au88x0 driver only accept period size in power
of 2.
======================================================================
----------------------------------------------------------------------
perex - 01-31-06 10:19
----------------------------------------------------------------------
Yes and no. It's combination pow2 and periods == integer issue. If the
buffer size is 24000 and period size is 2048, then 24000 / 2048 = 11.7188
which is not integer value and then configuration fails.
In this case depends on the parameter order. Or a better fix maybe to
describe that buffer_size must be N * period_size with pow2 restriction
(create a list with all combinations).
I've tried to add a workaround to snd_pcm_set_params() to CVS, but it does
not prevent other apps using the hw_params ALSA API directly to fail.
----------------------------------------------------------------------
perex - 01-31-06 10:26
----------------------------------------------------------------------
To be sure: I'm talking about SNDRV_PCM_HW_PARAM_PERIOD_BYTES restriction.
See pci/emu10k1/emupcm.c code how you can use the
snd_pcm_hw_constraint_list() for this parameter.
Issue History
Date Modified Username Field Change
======================================================================
01-07-06 05:10 Raymond New Issue
01-09-06 15:19 Raymond Note Added: 0007537
01-19-06 15:04 Raymond Note Deleted: 0007537
01-19-06 15:36 Raymond Note Added: 0007721
01-28-06 07:58 Raymond Note Added: 0007828
01-28-06 07:58 Raymond Note Deleted: 0007721
01-30-06 18:46 Raymond Note Added: 0007840
01-31-06 03:15 Raymond Note Added: 0007844
01-31-06 06:41 Raymond Note Edited: 0007840
01-31-06 07:03 Raymond Note Edited: 0007840
01-31-06 07:08 Raymond Note Edited: 0007840
01-31-06 07:11 Raymond Note Edited: 0007840
01-31-06 08:31 Raymond Note Edited: 0007840
01-31-06 09:48 Raymond Note Edited: 0007844
01-31-06 10:19 perex Note Added: 0007845
01-31-06 10:26 perex Note Added: 0007847
======================================================================
-------------------------------------------------------
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-31 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 9:26 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-31 9:19 [ALSA - lib 0001724]: simple PCM helper function bugtrack
2006-01-31 2:15 bugtrack
2006-01-30 17:46 bugtrack
2006-01-28 6:58 bugtrack
2006-01-19 14:36 bugtrack
2006-01-09 14:19 bugtrack
2006-01-07 4:10 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=bf566c7e354e89b1960ecfcea21c6adb@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