From: Grant Diffey <gdiffey@gmail.com>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Daniel Mack <zonque@gmail.com>
Subject: Re: A plea for help on mixer support for Fast Track Ultra (8R)
Date: Wed, 25 May 2011 09:55:58 +1000 [thread overview]
Message-ID: <BANLkTikhpGSum+N8JRewkT0u-dxK53KkHQ@mail.gmail.com> (raw)
In-Reply-To: <4DDB8444.4010500@showlabor.de>
Guys,
So I'm not going to get to this for ~10hrs which means missing the merge
window nost likely for 2.6.40/2.8.0/3.0/whateverlinusdecidestocallit I'm
comefortable with Felix having tested. I will get to it when I can but I'm
currently @work and will be for 8hrs or so.
Grant.
On Tue, May 24, 2011 at 8:11 PM, Felix Homann <linuxaudio@showlabor.de>wrote:
> Hi again,
>
> Am 20.05.2011 17:08, schrieb Grant Diffey:
>
> I think there's something whacky with the control map. (I can't seem to
>> send
>> Ain5 to out 1 and 2 successfully. but I'll test this with felix's original
>> code.
>>
>
> Grant, could you please try the attached patch. I haven't tested all 128
> controls but it seems to work fine here. And while you're at it, could you
> please try some other "outs" as well. My FTU is in a rack and I can't easily
> access out 5-8.
>
>
>
> The Ain's are not capture volumes for this device
>> There's 8 "analog ins" and 8 "software returns" (pcm channels) that are
>> mixed to 8 outputs. all the input gain controls are physical or line +4db
>> level balanced
>>
>
> That's true. I abused the term "Capture Volume" for my purely personal
> interest, since it made navigating through the controls easier in alsamixer
> and alsamixer-qt4. So, Daniel and Takashi, please feel free to change the
> names to whatever you think is more appropriate.
>
> Kind regards,
>
> Felix
>
>
>
>
>
prev parent reply other threads:[~2011-05-24 23:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 15:19 A plea for help on mixer support for Fast Track Ultra (8R) Felix Homann
2011-05-18 15:29 ` Felix Homann
2011-05-18 17:51 ` Daniel Mack
2011-05-18 18:46 ` Felix Homann
2011-05-18 21:30 ` Daniel Mack
2011-05-19 0:51 ` Grant Diffey
2011-05-19 5:42 ` Takashi Iwai
2011-05-19 6:45 ` Felix Homann
2011-05-19 7:15 ` Clemens Ladisch
2011-05-19 7:24 ` Takashi Iwai
2011-05-19 8:14 ` Felix Homann
2011-05-19 8:52 ` Daniel Mack
2011-05-19 10:56 ` Felix Homann
2011-05-19 11:05 ` Daniel Mack
2011-05-19 12:23 ` Felix Homann
2011-05-19 13:36 ` Felix Homann
2011-05-19 13:42 ` Felix Homann
2011-05-19 14:12 ` Daniel Mack
2011-05-20 10:12 ` Felix Homann
2011-05-20 11:12 ` Daniel Mack
2011-05-20 11:14 ` Felix Homann
2011-05-20 11:37 ` Daniel Mack
2011-05-20 15:08 ` Grant Diffey
2011-05-20 15:43 ` Grant Diffey
2011-05-20 15:52 ` Felix Homann
2011-05-20 15:54 ` Daniel Mack
2011-05-20 16:25 ` Grant Diffey
2011-05-20 16:38 ` Daniel Mack
2011-05-20 16:44 ` Felix Homann
2011-05-20 16:52 ` Felix Homann
2011-05-24 10:11 ` Felix Homann
2011-05-24 10:47 ` Daniel Mack
2011-05-24 11:54 ` Takashi Iwai
2011-05-24 23:55 ` Grant Diffey [this message]
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=BANLkTikhpGSum+N8JRewkT0u-dxK53KkHQ@mail.gmail.com \
--to=gdiffey@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linuxaudio@showlabor.de \
--cc=tiwai@suse.de \
--cc=zonque@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 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).