All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: alsa-devel@alsa-project.org
Subject: How much of the X-Fi (emu20k1) chip has Creative documented?
Date: Sun, 17 Jan 2010 16:43:08 -0800 (PST)	[thread overview]
Message-ID: <760045.1231.qm@web52904.mail.re2.yahoo.com> (raw)

Hi,

I am thinking about upgrading my Audigy2 sound card, and was looking at the X-Fi. However, the feature matrix for X-Fi cards on the ALSA site only says "PCI". (I assume that also includes PCIe these days.) Given that there is a basic snd-ctxfi driver, it seems likely that this matrix should also include "ANALOGio", and so I was wondering if someone could tell me what the actual matrix entry for the X-Fi cards should be these days, please?

Would the documentation that Creative has released allow any additional features to be implemented in the future? I am obviously hoping at least for feature parity with the Audigy2, i.e. multi-voiced hardware mixing. That "crystalizer" would seem to be one of the cards main selling points, too. However, if the driver is "feature complete" as far as Creative's documentation goes, then one of the Xonar cards would seem better value for money.

Thanks for any assistance,
Cheers,
Chris

             reply	other threads:[~2010-01-18  0:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  0:43 Chris Rankin [this message]
2010-01-18 20:51 ` How much of the X-Fi (emu20k1) chip has Creative documented? Brendan Pike
2010-01-18 22:21   ` Chris Rankin
2010-01-18 22:27     ` Brendan Pike
2010-01-23 22:04       ` Chris Rankin
2010-01-23 22:41         ` Brendan Pike
2010-01-23 22:46           ` Chris Rankin
2010-01-24 10:28             ` Takashi Iwai
2010-01-24 14:26               ` Brendan Pike
2010-01-24 16:57               ` Chris Rankin
2010-01-25  6:57                 ` Takashi Iwai
2010-01-25  8:49                   ` Chris Rankin

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=760045.1231.qm@web52904.mail.re2.yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=alsa-devel@alsa-project.org \
    /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.