From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Creative ZXR channels and volume messed up
Date: Sun, 30 Nov 2025 17:02:40 +0100 (CET) [thread overview]
Message-ID: <187cd44798748000-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <187cd447984f1e00-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #484 was opened from CommonDirt:
posted this over @ Pipewire, but i'm guessing this is an ALSA issue
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4996
Issue URL : https://github.com/alsa-project/alsa-lib/issues/484
Repository URL: https://github.com/alsa-project/alsa-lib
next parent reply other threads:[~2025-11-30 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <187cd447984f1e00-webhooks-bot@alsa-project.org>
2025-11-30 16:02 ` GitHub issues - opened [this message]
[not found] <187cd4af4560ee00-webhooks-bot@alsa-project.org>
2025-11-30 16:10 ` Creative ZXR channels and volume messed up GitHub issues - edited
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=187cd44798748000-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).