All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John L. Utz III" <jutz@dmx.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: John Utz <John.Utz@dmx.com>, Takashi Iwai <tiwai@suse.de>,
	ALSA Developers <alsa-devel@alsa-project.org>
Subject: Re: CMI8788/AV200/Oxygen Volume Controls in alsamixer (oxygen_mixer.c:dac_volume_get())
Date: Mon, 26 Jan 2009 15:36:59 -0800	[thread overview]
Message-ID: <497E491B.8020104@dmx.com> (raw)
In-Reply-To: <497D7993.8070009@ladisch.de>

Clemens Ladisch wrote:
> John Utz wrote:
>> if my employer decides that we will use the card
> 
> If you're thinking about the Xonar D2/D2X: please note that I removed
> the "Master" control in the latest kernel in the hope of fixing some
> unexplained bug where the card's EEPROM would be deleted.  (I think that
> I may be able to prove that the Master control isn't related to this
> bug, and revert that change.)

Good to know, but not relevant in our case, we are exploring the D1.

>> (not entirely clear, it's expensive and IMHO the sound quality isnt
>> worth the money)
> 
> The Xonar D1/DX has almost the same capabilities as the D2/D2X (in Linux)
> and is more reasonably priced.

It's definitely reasonable when compared to the D2, but it's still 
relatively expensive.

> What are your requirements?

Low price, good power output on *all* channels, good fidelity. robust 
linux multichannel support.

not a big list, eh?. :-)

onboard stuff tends to only provide amplification on the front channels 
and expects that the user will provide a separate amplifier for rear and 
surround.

Sound *cards* tend to have onboard amps for all the channels because 
they have the pcb real-estate to spare for that sort of thing.

> 
> Best regards,
> Clemens
> 

  reply	other threads:[~2009-01-26 23:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 23:36 CMI8788/AV200/Oxygen Volume Controls in alsamixer (oxygen_mixer.c:dac_volume_get()) John L. Utz III
2009-01-23 13:51 ` Clemens Ladisch
2009-01-23 13:56   ` Takashi Iwai
2009-01-23 14:13     ` Clemens Ladisch
2009-01-23 14:18       ` Takashi Iwai
2009-01-23 14:21         ` Takashi Iwai
2009-01-23 19:21       ` John Utz
2009-01-24 10:12         ` Takashi Iwai
2009-01-26  8:51         ` Clemens Ladisch
2009-01-26 23:36           ` John L. Utz III [this message]
2009-01-23 19:08     ` John Utz
2009-01-24 10:01       ` Takashi Iwai
2009-01-23 19:07   ` John Utz

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=497E491B.8020104@dmx.com \
    --to=jutz@dmx.com \
    --cc=John.Utz@dmx.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=tiwai@suse.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.