All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Homann <linuxaudio@showlabor.de>
To: chris-alsa@rauros.net
Cc: Grant Diffey <gdiffey@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: M-Audio FastTrack C400
Date: Sat, 5 May 2012 09:05:35 +0200	[thread overview]
Message-ID: <CAFz=ag4ST+StciziAjTyLs5E+kLedULYSceuABV0d1uL+hHeRA@mail.gmail.com> (raw)
In-Reply-To: <4FA45B69.5010608@rauros.net>

Hi again,

2012/5/5 Chris Cavey <chris-alsa@rauros.net>:
> No change.

Hmm, do you still get this message:

   ALSA mixer.c:352 cannot get ctl value: req = 0x83, wValue = 0x101,
wIndex = 0x4001, type = 4
   ALSA mixer.c:877 64:1: cannot get min/max values for control 1 (id 64)

If so, can you please look at mixer.c 352 if line 352 corresponds to
get_ctl_value_v2? (My line numbers are a bit off compared to yours it
seems). Can you send some Ci lines from usbmon from before the
mesasage appears.


>  According to usbmon looks like no matter what channel I adjust,
> the clock ctl is always being adjusted as if the wrong wIndex gets selected.
> The clock wIndex is 0x8001 but the mixer volume is 0x4001. The wValue looks
> correct (first mixer, according to my docs, should be 0x0100).

That's strange. Can you try if your "return 0" instead of "break" in
the device parsing is still needed now that we have a mixer quirk?
(Just a blind guess...)


> I'm going to
> trace down the rabbit hole to learn how wValue/wIndex is derived from the
> mixer controls.

Just compare with the FTUs controls.

>
> I'll keep tinkering. At some point I should probably just buy you a C400,
> probably easier.

Have you thought about switching to a MOTU or RME device? Maybe we
should work on these ;-)

Kind regards,

Felix

  reply	other threads:[~2012-05-05  7:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 12:37 M-Audio FastTrack C400 Chris Cavey
     [not found] ` <CACckToXF6yW+GzhzJ3zVBKi3e+thwrpDVnFmMCtjQOqePuixZg@mail.gmail.com>
     [not found]   ` <4F8DF29B.9090907@rauros.net>
2012-04-18  1:12     ` Grant Diffey
2012-04-18  7:26       ` Clemens Ladisch
2012-04-19  2:01         ` Chris Cavey
2012-04-19  7:58           ` Chris Cavey
2012-04-19  8:53           ` Clemens Ladisch
2012-04-19 10:26             ` Chris Cavey
2012-04-19 11:09               ` Grant Diffey
2012-04-19 11:19                 ` Chris Cavey
     [not found]                   ` <CACckToXHxm0y28ir+HGjE+Wug9PusHdrOeJpb3zQAFgQLjdP5w@mail.gmail.com>
2012-04-19 19:47                     ` Chris Cavey
2012-04-20  7:54             ` Daniel Mack
2012-04-21  1:29               ` Chris Cavey
2012-04-21  8:10                 ` Felix Homann
2012-04-21  8:48                   ` Felix Homann
2012-04-21  9:19                   ` Grant Diffey
2012-04-21 16:07                     ` Chris Cavey
2012-04-29  3:09                     ` Chris Cavey
2012-04-29  6:51                       ` Felix Homann
2012-04-29 13:30                         ` Chris Cavey
2012-05-02 10:05                           ` Felix Homann
2012-05-02 20:44                             ` Chris Cavey
2012-05-03 14:58                               ` Felix Homann
2012-05-04  4:54                                 ` Chris Cavey
2012-05-04  8:26                                   ` Felix Homann
2012-05-04 22:42                                     ` Chris Cavey
2012-05-05  7:05                                       ` Felix Homann [this message]
2012-05-09  1:11                                         ` Chris Cavey
2012-05-09  8:33                                           ` Felix Homann
2012-08-18 17:47       ` Mudwalker
2012-11-02 16:11 Raphael Souza

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='CAFz=ag4ST+StciziAjTyLs5E+kLedULYSceuABV0d1uL+hHeRA@mail.gmail.com' \
    --to=linuxaudio@showlabor.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=chris-alsa@rauros.net \
    --cc=gdiffey@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.