From: Peter Grasch <me@bedahr.org>
To: alsa-devel@alsa-project.org
Subject: snd_device_name_hint: Inconsistent output
Date: Thu, 15 Nov 2012 01:27:00 +0100 [thread overview]
Message-ID: <1352939220.424.10.camel@localhost> (raw)
Hi!
Today, I noticed that some devices (specifically, the "pulse" device,
but there might be others as well) do not show up in a call to
snd_device_name_hint when it is called for the first time within an
application.
I've managed to reproduce the problem on three different systems:
Get the source of a current version of aplay, compile it, run aplay -L
and store the output.
Then add another call to snd_device_name_hint in pcm_list to make it
look like this (leaking memory, but it doesn't matter for this
demonstration):
315 static void pcm_list(void)
316 {
317 void **hints, **n;
318 char *name, *descr, *descr1, *io;
319 const char *filter;
320
321 snd_device_name_hint(-1, "pcm", &hints);
322 if (snd_device_name_hint(-1, "pcm", &hints) < 0)
323 return;
Compile and run this version of aplay and again store the output of
"aplay -L".
For me, the two outputs differ.
Please net me know how I can help to resolve this issue. Thanks.
Best regards,
Peter
reply other threads:[~2012-11-15 0:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1352939220.424.10.camel@localhost \
--to=me@bedahr.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