alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mike Oliphant <oliphant@nostatic.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Support for NUX MG-300 USB interface
Date: Wed, 20 Jan 2021 15:33:12 +0100	[thread overview]
Message-ID: <s5ha6t3el07.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHXb3bfUv7QzvgOmtV3LxJXaY=Uk+pKhWZmU0M+YkgB0kNrXmA@mail.gmail.com>

On Tue, 19 Jan 2021 18:40:04 +0100,
Mike Oliphant wrote:
> 
> Your mixer.c patch does get rid of the RANGE errors. No change to behavior,
> though.
> 
> I'd already tried setting "implicit_fb=1" even though I didn't expect it to
> work, since there is a separate feedback endpoint. I just tried it again - it
> doesn't seem to hurt anything, but it doesn't help either.
> 
> Capture seems to be working perfectly with the clock patch - I'm not sure why
> I was initially getting noisy input.
> 
> I checked "/proc/asound/card*/pcm*/sub*/status" during playback, and the
> pointer seems to be moving forward as it should. All indications are that the
> system thinks playback is working fine.
> 
> One interesting piece of information - alsamixer shows two stereo outputs
> ("pcm" and "pcm1"). Not sure why there are two - maybe output is going to the
> wrong one?

You might need to unmute and increase both.  The first one should be a
master volume/switch while the second one is for the stereo channels.

Naming the mixer elements properly for USB-audio is a really tough
task.  Many firmware don't set the right strings and a guess work
doesn't fit to all.  But certainly there are some rooms for
improvements there.


Takashi

  reply	other threads:[~2021-01-20 14:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 18:56 Support for NUX MG-300 USB interface Mike Oliphant
2021-01-18  7:43 ` Takashi Iwai
2021-01-18 16:33   ` Mike Oliphant
2021-01-18 17:54     ` Mike Oliphant
2021-01-18 19:19       ` Takashi Iwai
2021-01-18 21:15         ` Mike Oliphant
2021-01-18 21:59           ` Takashi Iwai
2021-01-19  0:26             ` Mike Oliphant
2021-01-19  9:05               ` Takashi Iwai
2021-01-19 17:40                 ` Mike Oliphant
2021-01-20 14:33                   ` Takashi Iwai [this message]
2021-01-20 21:17                     ` Mike Oliphant
2021-01-20 21:38                       ` Takashi Iwai
2021-01-20 21:47                         ` Mike Oliphant
2021-01-21 19:04                           ` Mike Oliphant
2021-01-21 20:18                             ` Mike Oliphant

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=s5ha6t3el07.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=oliphant@nostatic.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;
as well as URLs for NNTP newsgroup(s).