From: Takashi Iwai <tiwai@suse.de>
To: Heinz Diehl <htd+ml@fritha.org>
Cc: linux-kernel@vger.kernel.org, lpoetter@redhat.com
Subject: Re: [BISECTED] Kernel 5.11.x breaks pulseaudio
Date: Thu, 25 Feb 2021 19:01:59 +0100 [thread overview]
Message-ID: <s5hft1kni08.wl-tiwai@suse.de> (raw)
In-Reply-To: <YDfeSZjdNKFcNKN8@fritha.org>
On Thu, 25 Feb 2021 18:28:41 +0100,
Heinz Diehl wrote:
>
> On 25.02.2021, Takashi Iwai wrote:
>
> > It's no regression but the right behavior. This indicates that you're
> > trying a stream in 44.1kHz in one side of the full duplex stream while
> > 48kHz in another rate, and this cannot work properly with the implicit
> > feedback devices.
> [....]
>
> Well, I'm by no means an audio or recording professional, but if what you describe
> is the correct behavior, it means that absolutely all audio files played on
> my machine always will be resampled to 44.1kHz. Youtube from native 48kHz,
> highres audio 24/96, virtually anything I play. Could that be correct? And
> what can I do to be able to listen to highres audio again?
As already mentioned, it's about the sample rate of full duplex
streams, i.e. both playback and capture streams need to be aligned to
the same rate. IOW, if both streams are in the same 48kHz, it should
be fine as is.
Check which streams are running when you get the unexpected sample
rate by inspecting /proc/asound/card*/pcm* entries.
Takashi
next prev parent reply other threads:[~2021-02-25 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 17:01 [BISECTED] Kernel 5.11.x breaks pulseaudio Heinz Diehl
2021-02-25 17:10 ` Takashi Iwai
2021-02-25 17:28 ` Heinz Diehl
2021-02-25 18:01 ` Takashi Iwai [this message]
2021-02-26 9:23 ` Heinz Diehl
2021-02-28 8:18 ` Takashi Iwai
2021-02-28 11:46 ` Heinz Diehl
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=s5hft1kni08.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=htd+ml@fritha.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpoetter@redhat.com \
/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