From: meschi@posteo.de
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Steinberg UR22 Crackling and Clicks
Date: Tue, 08 Dec 2020 21:53:14 +0100 [thread overview]
Message-ID: <987d1956f52ba49dc3b587c33e08bfb2@posteo.de> (raw)
In-Reply-To: <s5ho8j4ujwx.wl-tiwai@suse.de>
Am 08.12.2020 21:23 schrieb Takashi Iwai:
> On Tue, 08 Dec 2020 20:41:33 +0100,
> meschi@posteo.de wrote:
>>
>>
>>
>> Am 08.12.2020 15:57 schrieb Takashi Iwai:
>> > On Tue, 08 Dec 2020 15:50:28 +0100,
>> > meschi@posteo.de wrote:
>> >>
>> >> > 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
>> When I try to play a file now this happens:
>> $ aplay -D plughw:CARD=UR22 ./file.wav
>> Playing WAVE './file.wav' : Signed 16 bit Little Endian, Rate 44100
>> Hz, Stereo
>> aplay: set_params:1407: Unable to install hw params:
>
> It's a known side-effect of the implicit feedback mode, and the latest
> patchset I mentioned earlier addresses the issue.
>
>
> Takashi
I'm already running the kernel built from the linux-next tree...
I built next-20201208 from
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Is there another patch set that I'm missing?
next prev parent reply other threads:[~2020-12-08 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 14:00 meschi
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=987d1956f52ba49dc3b587c33e08bfb2@posteo.de \
--to=meschi@posteo.de \
--cc=alsa-devel@alsa-project.org \
--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