Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Lars Schotte <lars.schotte@schotteweb.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: asus xonar d1
Date: Wed, 14 Apr 2010 16:02:05 +0200	[thread overview]
Message-ID: <4BC5CADD.2020700@ladisch.de> (raw)
In-Reply-To: <20100414154223.246e7416@romy.gusto>

Lars Schotte wrote:
> > What controls are missing?
> 
> hmm. i dont know, i thought there will be more on such a card. because
> on creatives and hd audio usually you have tons of controls and there
> only 5 or so.

The D1/DX hardware doesn't have that many controls because there
aren't so many inputs or outputs.

> and 3 of them is 7.1 output so its a bit confusing.

There is one "Master" control with 8 channels.  How this is displayed
is up to the mixer application.  (alsamixer isn't ideal in this respect,
older versions even less so.)

> to fedora 13 the controls are noticably faster, to my old debian lenny
> even w/ the 2.6.32 kernel they lag. on fedora 13 w/ 2.6.33 they are
> fast as usual, seems like you fixed that already ;-) .

Yes, the driver now doesn't write registers that have not changed.
In theory, this shouldn't make too much of a difference unless the
mixer tries to set the same volume repeatedly.


Regards,
Clemens

  parent reply	other threads:[~2010-04-14 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 16:31 asus xonar d1 Lars Schotte
2010-04-13 16:43 ` Lars Schotte
2010-04-14  7:02   ` Clemens Ladisch
     [not found]     ` <20100414154223.246e7416@romy.gusto>
2010-04-14 14:02       ` Clemens Ladisch [this message]
     [not found]         ` <20100414174955.267cc1dd@romy.gusto>
2010-04-15  8:43           ` Clemens Ladisch
     [not found]             ` <4BC76730.2050700@schotteweb.de>
2010-04-16  6:31               ` Clemens Ladisch

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=4BC5CADD.2020700@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=lars.schotte@schotteweb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox