From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>, Takashi Iwai <tiwai@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>,
Jaroslav Kysela <perex@perex.cz>,
Linux ALSA Subsystem Development <alsa-devel@alsa-project.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: linux-6.4 alsa sound broken
Date: Wed, 3 May 2023 11:40:02 +0700 [thread overview]
Message-ID: <b449cbf6-8286-e22d-ca87-b1bc3dce29d7@gmail.com> (raw)
In-Reply-To: <CAAJw_ZveoPfnBsSkHZqmLiVWATcOosR--6Ds4cdekdi=t1yV7A@mail.gmail.com>
On 5/1/23 22:03, Jeff Chua wrote:
>> There was no description about which sound backend is used. Is it
>> PulseAudio, pipewire or dmix/dsnoop?
>
> Just pure alsautils.
>
> arecord -D hw:1,0,0 -f S16_LE -r 48000 recorded.wav
> aplay -D hw:1,1,0 /local/share/sounds/alsa/Side_Right.wav
>
> [recorded.wav] attached.
> [Side_Right.wav] attached.
> aplay: version 1.2.8 by Jaroslav Kysela <perex@perex.cz>
> arecord: version 1.2.8 by Jaroslav Kysela <perex@perex.cz>
>
> alsautils, alsaplugins alsalibs all using latest git pull.
Are you sure you build alsa tools straight from the git repo?
Can you also reproduce with latest stable version of these?
Otherwise it's anyone's guess due to moving parts...
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-05-03 4:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 3:59 linux-6.4 alsa sound broken Jeff Chua
2023-05-01 4:36 ` Bagas Sanjaya
2023-05-01 6:35 ` Takashi Iwai
2023-05-01 13:16 ` Jeff Chua
2023-05-01 14:52 ` Takashi Iwai
2023-05-01 15:03 ` Jeff Chua
2023-05-03 4:40 ` Bagas Sanjaya [this message]
2023-05-03 5:42 ` Jeff Chua
2023-05-01 13:08 ` Jeff Chua
2023-05-01 7:17 ` Oswald Buddenhagen
2023-05-01 15:05 ` Jeff Chua
2023-05-03 4:34 ` Bagas Sanjaya
2023-05-03 4:37 ` Bagas Sanjaya
2023-05-03 6:06 ` Takashi Iwai
2023-05-03 12:19 ` Jeff Chua
2023-05-03 13:44 ` Takashi Iwai
2023-05-03 15:06 ` Jeff Chua
2023-05-03 15:47 ` Takashi Iwai
2023-05-03 16:10 ` Takashi Iwai
2023-05-03 19:32 ` Jaroslav Kysela
2023-05-03 20:00 ` Oswald Buddenhagen
2023-05-03 20:17 ` Jaroslav Kysela
2023-05-04 6:15 ` Takashi Iwai
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=b449cbf6-8286-e22d-ca87-b1bc3dce29d7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oswald.buddenhagen@gmx.de \
--cc=perex@perex.cz \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.de \
/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