From: Thomas Charbonnel <thomas@undata.org>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsp multiface pci.
Date: 19 Jan 2003 15:12:50 +0100 [thread overview]
Message-ID: <1042985569.1663.33.camel@satellite.undata.org> (raw)
In-Reply-To: <3E2A952E.6060305@boosthardware.com>
On Sun, 2003-01-19 at 13:08, Patrick Shirkey wrote:
> Using latest cvs, I have been trying to get this device working for my
> friend. We have had some success but it is unreliable.
>
> We could get sound out of the lineout port after using this command
>
> amixer -D hw:0 cset numid=5 0,0,16384
>
This is supposed to route the signal received on analog input 1 to
analog output 1.
> numid=5,iface=PCM,name='Mixer'
> ; type=INTEGER,access=rw---,values=3,min=0,max=65536,step=1
> : values=16384,0,0
>
> Using
>
> numid=5 26,26,16384
> numid=5 27,27,16384
The above should indeed be the correct way to route software playback
channels 1-2 to the line outs (jack's alsa_pcm:playback_1 and _2, for
example).
> or
> numid=5 10,10,16384 <<<--- 10 appears to be line out id
>
What makes you say so ?
> seem to do nothing.
>
> Sometimes after trying to use aplay and usually when trying alsaplayer
> amixer resets the volume to 0.
>
> Is this buggy behaviour?
>
Maybe there is a bug in the matrix mixer. Yesterday, while working in a
complex setup, I couldn't manage to route analog inputs 3-4 to analog
outputs 3-4, it just didn't work. I had those inputs routed to the line
outs, and could hear the signal, but nothing came out of ouputs 3-4. I
had to route inputs 3-4 to outputs 5-6 to get it working. As we were
rehearsing, I had no time to further investigate. One of the problem
preventing proper understanding of the situation is that you actually
can't read from the mixer control, as cget doesn't take a parameter.
I know Paul is not fully satisfied with the way the matrix mixer is
handled right now. Maybe it could be changed so that reading the mixer
state is possible. I am currently writing a totalmix clone, and reading
the mixer state could really prove usefull. Imagine you're working with
a complex mixer setup and accidentally close the mixer app. If you
relaunch the app, it won't be able to read the mixer state back, and
will have to fall back on a preset. Your mixing work will be lost.
Other examples of the need of mixer state readout include
synchronization between different apps using the mixer. I plan to
implement a ladspa plugin to control the matrix mixer, so that you could
automate hardware mixing in ardour, for example. The plugin and the
standalone mixer app should stay synced.
Thomas
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-19 14:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 12:08 hdsp multiface pci Patrick Shirkey
2003-01-19 14:12 ` Thomas Charbonnel [this message]
2003-01-19 15:29 ` Patrick Shirkey
2003-01-19 15:55 ` Patrick Shirkey
2003-01-19 16:07 ` Thomas Charbonnel
2003-01-19 8:23 ` Mark Knecht
2003-01-19 17:27 ` Thomas Charbonnel
2003-01-19 16:33 ` Patrick Shirkey
2003-01-19 17:00 ` Roger Williams
2003-01-19 12:21 ` Mark Knecht
2003-01-19 22:24 ` Roger Williams
2003-01-19 16:34 ` Mark Knecht
2003-01-20 2:14 ` Roger Williams
2003-01-19 19:59 ` Mark Knecht
2003-01-20 6:25 ` Roger Williams
2003-01-20 5:06 ` Mark Knecht
2003-01-20 13:46 ` Roger Williams
2003-01-20 6:44 ` Roger Williams
2003-01-20 8:31 ` Marcus Andersson
2003-01-20 13:35 ` Roger Williams
2003-01-19 17:01 ` Patrick Shirkey
2003-01-19 17:20 ` Thomas Charbonnel
2003-01-19 23:12 ` Roger Williams
-- strict thread matches above, loose matches on Subject: below --
2003-01-20 15:57 markknecht
2003-01-20 16:12 markknecht
[not found] <E18aeXp-00009y-00@sturgeon.coelacanth.com>
2003-01-20 17:01 ` Roger Williams
2003-01-22 18:19 ` Paul Davis
2003-01-22 18:30 ` Roger Williams
2003-01-22 18:41 ` Paul Davis
2003-01-22 18:54 ` Mark Knecht
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=1042985569.1663.33.camel@satellite.undata.org \
--to=thomas@undata.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pshirkey@boosthardware.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.