From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: speaker-test channel descriptions don't match expectations
Date: Tue, 19 Jul 2022 03:34:02 +0200 (CEST) [thread overview]
Message-ID: <20220719013402.0BF44F801EC@alsa1.perex.cz> (raw)
In-Reply-To: <1658194438061773062-webhooks-bot@alsa-project.org>
alsa-project/alsa-utils issue #159 was opened from pfps:
The text output of speaker-test for -c6 appears to indicate that it is using 5+1 channels, with FL, FR, RL, RR, FC, LFE channels (output in a different order). But the wav files that it uses say FL, FR, RL, ??, FC, Rear Center. And this channel order doesn't seem correct, as the channels are not down-mixed to stereo correctly on my system with pipewire and pipewire-media-session.
What can be done to get speaker-test and pipewire to agree on the channels?
Issue URL : https://github.com/alsa-project/alsa-utils/issues/159
Repository URL: https://github.com/alsa-project/alsa-utils
parent reply other threads:[~2022-07-19 1:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1658194438061773062-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=20220719013402.0BF44F801EC@alsa1.perex.cz \
--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