From: Paul Davis <paul@linuxaudiosystems.com>
To: Vincenzo Di Salvo <Vincenzo.DiSalvo@isti.cnr.it>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: No mixer elems found
Date: Wed, 31 Mar 2004 07:38:13 -0500 [thread overview]
Message-ID: <200403311238.i2VCcD33015334@dhin.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Wed, 31 Mar 2004 13:59:37 +0200." <6.0.0.22.0.20040331135721.0242fb48@pop.isti.cnr.it>
>The problem is that I cannot get the mixer to have any "elements" (or=20
>"elems" as the alsamixer calls them) which thus makes the card un-openable=
>=20
>even with the alsamixer.
thats correct. the hdsp has no mixer that can be represented using
conventional mixer elements. there is nothing corresponding to any of
the controls that other cards tend to have (e.g. PCM volume, main
volume, capture source, etc)
if you want to control the mixer, use thomas charbonnel's hdspmixer,
which is a reimplementation of RME's TotalMix. it provides complete
control over the mixer. it is a standard part of ALSA.
--p
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-31 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 11:59 No mixer elems found Vincenzo Di Salvo
2004-03-31 12:38 ` Paul Davis [this message]
2004-03-31 15:33 ` snd_pcm_writei not returning (?!?) Tom Browne
2004-04-05 14:25 ` Tom Browne
2004-04-05 15:49 ` Clemens Ladisch
2004-04-05 16:16 ` Tom Browne
2004-04-06 7:48 ` Clemens Ladisch
2004-04-06 9:07 ` Tom Browne
2004-04-06 9:15 ` Jaroslav Kysela
2004-04-06 9:58 ` Tom Browne
2004-04-06 10:15 ` Jaroslav Kysela
2004-04-06 10:44 ` Tom Browne
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=200403311238.i2VCcD33015334@dhin.linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=Vincenzo.DiSalvo@isti.cnr.it \
--cc=alsa-devel@lists.sourceforge.net \
/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.