From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000753]: Setting of hw params rate and channels in c++ interface on development seems to use old parameter setting functions.
Date: Mon, 30 May 2005 13:21:18 +0200 [thread overview]
Message-ID: <fd4acdfeaf710dff78d6546b8facfcd0@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=753>
======================================================================
Reported By: fredy
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 753
Category: pcm - digital audio
Reproducibility: always
Severity: crash
Priority: normal
Status: new
======================================================================
Date Submitted: 12-28-2004 23:28 CET
Last Modified: 05-30-2005 13:21 CEST
======================================================================
Summary: Setting of hw params rate and channels in c++
interface on development seems to use old parameter setting functions.
Description:
In developing a c++ class for pcm_interface I can't set the rate an
channels. For example setting a rate of 48000 samples/sec leaves the
parameters with odd values.
By debugging I see that while setting access and format uses the regular
pcm_hw_params_... functions, setting rate uses _old_pcm_hw_params and
probably uses different parameters structures. I've searched #defines in
headers that force the use of old functions without finding anthing
related.
The test program pcm works correctly.
======================================================================
----------------------------------------------------------------------
jdthood - 03-16-05 22:27
----------------------------------------------------------------------
Could this possibly be related to http://bugs.debian.org/288652 ?
----------------------------------------------------------------------
perex - 05-30-05 13:21
----------------------------------------------------------------------
It appears like a linking problem. What does this command says?
nm <your_c++_apps> | grep set_rate
It should be something like:
U snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
Issue History
Date Modified Username Field Change
======================================================================
12-28-04 23:28 fredy New Issue
03-16-05 22:27 jdthood Note Added: 0003968
05-30-05 13:07 perex Category ordinary pcm => pcm -
digital audio
05-30-05 13:21 perex Note Added: 0004808
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next reply other threads:[~2005-05-30 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 11:21 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 5:22 [ALSA - lib 0000753]: Setting of hw params rate and channels in c++ interface on development seems to use old parameter setting functions bugtrack
2005-05-30 11:07 bugtrack
2005-03-16 21:27 bugtrack
2004-12-28 22:28 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=fd4acdfeaf710dff78d6546b8facfcd0@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