All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Diffey <gdiffey@gmail.com>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: alsa-devel@alsa-project.org, chris-alsa@rauros.net
Subject: Re: M-Audio FastTrack C400
Date: Sat, 21 Apr 2012 19:19:00 +1000	[thread overview]
Message-ID: <CACckToUVQu=p0ZSaGw-oRn2ASgfQ_Po2im1ha5-yUVeyt7JUaQ@mail.gmail.com> (raw)
In-Reply-To: <CAFz=ag4viHQ-K7qbpCk-G+H3Q8GKe=7-anfOeCy3jhUCYUJ5BQ@mail.gmail.com>

> >(channels = 2, ifnum = 2).
>
> Why do you use channels=2. As fas as I can tell the device has 6
> channels. Try that.
>
>
> > Except I can't get it to play anything (figure it would all be too good
> > to be true)
> >
> > $ speaker-test -Dfront:C400
> > speaker-test 1.0.25
> >
> > Playback device is front:C400
> > Stream parameters are 48000Hz, S16_LE, 1 channels
> > Using 16 octaves of pink noise
> > Sample format not available for playback: Invalid argument
> > Setting of hwparams failed: Invalid argument
> >
>
> The device probably supports only S24_3LE audio. At least that's what
> you tell Alsa with the FTU quirk. Try to play something through the
> corresponding hw device or use Jack or convert some audio file to
> S24_3LE and play through aplay etc...
>
>
that's a good point

try speaker-test -D plughw:C400

  parent reply	other threads:[~2012-04-21  9:19 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 [this message]
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
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='CACckToUVQu=p0ZSaGw-oRn2ASgfQ_Po2im1ha5-yUVeyt7JUaQ@mail.gmail.com' \
    --to=gdiffey@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=chris-alsa@rauros.net \
    --cc=linuxaudio@showlabor.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 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.