From: meschi@posteo.de
To: Alsa devel <alsa-devel@alsa-project.org>
Subject: Re: Steinberg UR22 Crackling and Clicks
Date: Tue, 08 Dec 2020 15:00:19 +0100 [thread overview]
Message-ID: <728dfc14a17bde2b0a7442ea071d386f@posteo.de> (raw)
-------- Originalnachricht --------
Betreff: Re: Steinberg UR22 Crackling and Clicks
Datum: 08.12.2020 14:58
Von: meschi@posteo.de
An: Takashi Iwai <tiwai@suse.de>
> It's likely the issues with the implicit feedback.
>
> The latest development tree (either linux-next tree or
> topic/usb-audio-refactoring branch of my sound.git tree) contains the
> improvements of the implicit feedback mode.
>
>
> Takashi
I've compiled a kernel from
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
uname -a is "Linux meschi-Precision-WorkStation-T5500
5.10.0-rc7-next-20201208 #1 SMP PREEMPT Tue Dec 8 12:28:39 CET 2020
x86_64 x86_64 x86_64 GNU/Linux"
The problem is still there. Is it possible to fallback to explicit
feedback mode for the device from user space?
I'd like to learn more about these feedback modes, is there a place
where this is explained?
I'm curious how this device is working on another machine. I'm not quite
proficient with the alsa kernel subsystem to debug this myself,
but I would be happy to test patches and learn along the way if somebody
is interested in debugging this.
next reply other threads:[~2020-12-08 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 14:00 meschi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 10:15 Steinberg UR22 Crackling and Clicks meschi
2020-12-08 10:34 ` Takashi Iwai
2020-12-08 14:50 ` meschi
2020-12-08 14:57 ` Takashi Iwai
2020-12-08 19:41 ` meschi
2020-12-08 20:23 ` Takashi Iwai
2020-12-08 20:53 ` meschi
2020-12-08 21:29 ` Takashi Iwai
2020-12-08 22:14 ` meschi
2020-12-09 6:58 ` Takashi Iwai
2020-12-09 11:56 ` meschi
2020-12-09 12:00 ` Takashi Iwai
2020-12-09 12:10 ` meschi
2020-12-09 12:13 ` Takashi Iwai
2020-12-09 16:07 ` Kilian
2020-12-09 16:09 ` 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=728dfc14a17bde2b0a7442ea071d386f@posteo.de \
--to=meschi@posteo.de \
--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