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: Wed, 9 May 2012 10:33:57 +0200	[thread overview]
Message-ID: <CAFz=ag4EBn139_zyLihz6cjDiRt9guWT_cpYNccCPsr2HEQ3uw@mail.gmail.com> (raw)
In-Reply-To: <4FA9C454.7060201@rauros.net>

Hi again,

2012/5/9 Chris Cavey <chris-alsa@rauros.net>:
> I do not get that message anymore.

That's good.

Could you please send me the contents of your
/proc/asound/[YOUR_DEVICE]/usbmixer.

BTW, you could try to experiment a bit with volume quirks: See,
mixer.c  search for 2081 to see how it's done for some of the FTU
controls. The volume controls for the FTU are reported in usbmixer to
range from -32768 to 0.

>
> Fixing the "return 0" back to "break" results in the device not even
> registering, back to the -5 error from the beginning of this thread.

OK, it was just a blind guess as I said.



> I really just want to find a single device, USB or Firewire (or
> PCIE), which works flawlessly in both Windows and Linux. Instrument/Mic
> input as well as independent balanced out and headphones.
>
> Any thoughts on this?

I was just joking when I mentioned the MOTUs and RMEs ;-) I would
certainly enjoy getting a MOTU Ultralite mk3 hybrid or a RME Babyface
to play around with and personally I will never buy a M-Audio device
again.

But while I'm quite confident that we can get the C400 working (might
take some time though) I don't know wether or not the MOTUs and RMEs
do behave in any way like  UAC1/2 devices at all. I haven't seen a
single report on them, yet.

Regards,
Felix

  reply	other threads:[~2012-05-09 12:36 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
2012-05-09  1:11                                         ` Chris Cavey
2012-05-09  8:33                                           ` Felix Homann [this message]
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=ag4EBn139_zyLihz6cjDiRt9guWT_cpYNccCPsr2HEQ3uw@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.