From: Takashi Iwai <tiwai@suse.de>
To: Kilian <meschi@posteo.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Steinberg UR22 Crackling and Clicks
Date: Wed, 09 Dec 2020 17:09:22 +0100 [thread overview]
Message-ID: <s5hmtynrmfh.wl-tiwai@suse.de> (raw)
In-Reply-To: <c7194dab05d5bbff24b589dfc126fd54@posteo.de>
On Wed, 09 Dec 2020 17:07:53 +0100,
Kilian wrote:
>
> >> > Then try to pass implicit_fb=1 option to snd-usb-audio module.
> >> > It's a new option that was added recently.
> >> >
> >> >
> >> > Takashi
> >>
> >> Nice, that did the trick. there was a small glitch on first playback
> >> but I can not reproduce it now. Playback seems glitch-free now. I will
> >> test it with pulseaudio in the gui if I can. It's not quite easy to
> >> test, because the system locks up after a while with the new kernel
> >> and gnome 3. I will also test concurrent playback and recording,
> >> too. Thank you very much, that was a huge help!
> >
> > Good to hear. If the implicit_fb option works, we can add a static
> > quirk table entry easily. Just add IMPLICIT_FB_GENERIC_DEV() with the
> > device ID to playback_implicit_fb_quirks[] table in
> > sound/usb/implicit.c.
> >
> >
> > Takashi
>
> Still having problems with the nouveau driver, so i couldn't thest
> this with pulseaudio. Recording with arecord works parallel to playing
> back with aplay. so here is my patch for implicit.c
OK, I'll cook up the proper patch and submit for 5.11 merge.
thanks,
Takashi
> diff --git a/sound/usb/implicit.c b/sound/usb/implicit.c
> index 386198b36b87..c729ff634b9d 100644
> --- a/sound/usb/implicit.c
> +++ b/sound/usb/implicit.c
> @@ -46,6 +46,7 @@ static const struct snd_usb_implicit_fb_match
> playback_implicit_fb_quirks[] = {
> IMPLICIT_FB_GENERIC_DEV(0x0763, 0x2081), /* M-Audio FastTrack
> Ultra */
> IMPLICIT_FB_GENERIC_DEV(0x0763, 0x2030), /* M-Audio Fast Track
> C400 */
> IMPLICIT_FB_GENERIC_DEV(0x0763, 0x2031), /* M-Audio Fast Track
> C600 */
> + IMPLICIT_FB_GENERIC_DEV(0x0499, 0x1509), /* Steinberg UR22 */
>
> /* Fixed EP */
> /* FIXME: check the availability of generic matching */
>
next prev parent reply other threads:[~2020-12-09 16:10 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
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 [this message]
-- 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=s5hmtynrmfh.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=meschi@posteo.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