From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: A52 producing static noise
Date: Wed, 3 Sep 2025 11:34:56 +0200 (CEST) [thread overview]
Message-ID: <1861bc0d2e545300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <1861bc0d2e4cf800-webhooks-bot@alsa-project.org>
alsa-project/alsa-plugins issue #63 was edited from mingww64:
Setup is GPU----(HDMI)----TV----(eARC)----Sonos Arc
Playing AC3 audio sample works and can confirm the speakers is receiving in AC3 format (Sonos app displaying Dolby Digital 5.1), however using the a52 plugin with `speaker-test` only static noise was coming out intermittently and Sonos app doesn't show any audio format. The GPU is a rx9070xt , I'm unsure if the problem is on the plugin or on AMD's side.
```log
Slave: Hardware PCM card 0 'HDA ATI HDMI' device 9 subdevice 0
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 3072
period_size : 768
period_time : 16000
tstamp_mode : NONE
tstamp_type : MONOTONIC
period_step : 1
avail_min : 768
period_event : 0
start_threshold : 3072
stop_threshold : 3072
silence_threshold: 0
silence_size : 0
boundary : 6917529027641081856
appl_ptr : 0
hw_ptr : 0
0 - Front Left
4 - Front Center
1 - Front Right
3 - Rear Right
2 - Rear Left
5 - LFE
Time per period = 17.888669
0 - Front Left
4 - Front Center
1 - Front Right
^C 3 - Rear Right
2 - Rear Left
5 - LFE
Time per period = 8.512034
```
Issue URL : https://github.com/alsa-project/alsa-plugins/issues/63
Repository URL: https://github.com/alsa-project/alsa-plugins
next parent reply other threads:[~2025-09-03 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1861bc0d2e4cf800-webhooks-bot@alsa-project.org>
2025-09-03 9:34 ` GitHub issues - edited [this message]
[not found] <1861bbeed2850400-webhooks-bot@alsa-project.org>
2025-09-03 9:32 ` A52 producing static noise GitHub issues - opened
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=1861bc0d2e545300-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).