All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: On output devices, `snd_pcm_open()` makes a bad loud tick.
Date: Sun, 13 Apr 2025 14:48:36 +0200 (CEST)	[thread overview]
Message-ID: <1835e1a0d2c45500-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <1835e1a0d217ae00-webhooks-bot@alsa-project.org>

alsa-project/alsa-lib issue #451 was opened from ewtoombs:

Minimal reproduction:

```
#include <alsa/asoundlib.h>
#include <stdbool.h>
int main(int argc, const char **argv)
{
    snd_pcm_t *out;
    assert(snd_pcm_open(&out,
                "default",    // the name of the device being opened
                SND_PCM_STREAM_PLAYBACK, // it is an output stream
                false         // iff nonblocking stream
                ) == 0);
}
```
(Compile with `gcc -o test test.c -lasound`.)

Relevant `lspci`:
```
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
```

`uname`:
```
Linux robert 6.13.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 23 Mar 2025 17:17:30 +0000 x86_64 GNU/Linux
```

alsa-lib version: 1.2.13-1 (archlinux)

I've heard similar artefacts on many different sound cards, though, across many different architectures, always on linux.
One must wait about five minutes in between trials, or the artefact does not occur.

This isn't a minor detail.
The tick is very loud.
It might even damage speakers in a worst case scenario.

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/451
Repository URL: https://github.com/alsa-project/alsa-lib

           reply	other threads:[~2025-04-13 12:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1835e1a0d217ae00-webhooks-bot@alsa-project.org>]

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=1835e1a0d2c45500-webhooks-bot@alsa-project.org \
    --to=github@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 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.