Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 25 Feb 2021 18:28:41 +0100
From:   Heinz Diehl <htd+ml@fritha.org>
To:     linux-kernel@vger.kernel.org
Cc:     tiwai@suse.de, lpoetter@redhat.com
Subject: Re: [BISECTED] Kernel 5.11.x breaks pulseaudio
Message-ID: <YDfeSZjdNKFcNKN8@fritha.org>
References: <YDfYAYCaC9KDc1F0@fritha.org>
 <s5him6gnkdu.wl-tiwai@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <s5him6gnkdu.wl-tiwai@suse.de>
Organization: private site
OpenPGP: id=60F4A92C; url=http://www.fritha.org/htd.asc;
 preference=signencrypt
User-Agent: Mutt/1.14.7+158 (b0ccf259) (2020-09-25)
Precedence: bulk

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?

Thanks,
 Heinz