From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Peter Zubaj <pzubaj@gaya.sk>
Cc: Lee Revell <rlrevell@joe-job.com>,
James Courtier-Dutton <James@superbug.co.uk>,
Takashi Iwai <tiwai@suse.de>, Emmanuel Fleury <fleury@cs.aau.dk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: [Alsa drivers] Creatives X-Fi chip
Date: Tue, 23 Aug 2005 14:48:34 -0400 [thread overview]
Message-ID: <20050823184834.GC28578@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1124829672.3351.5.camel@localhost.localdomain>
On Tue, Aug 23, 2005 at 09:41:11PM +0100, Peter Zubaj wrote:
> This is too expensive card to be only able use it as simple card.
> My advice buy something else.
> I don't think fight with creative can bring anything good to linux.
> Leave Creative as is. There is plenty of other hardware from other
> manufacturer worth money.
If I could get the same level of support as my sb live has, I would be
quite happy. I don't need EAX, but I do want midi synth and multi
channel audio playback and recording and such to work, and all the line
in and out on the device. We have that on the emu10kx cards as far as I
can tell (at least everything I have used on my sb live platinum works).
I don't mind if the fancy DSP algorithms and EAX is windows only, since
it really only applies to games, and if I want to play a windows game, I
will reboot to windows. Doesn't happen very often lately, but with an
athlon 700, it isn't that surprising really. Maybe when someday I get
an athlon 64 instead.
So I would buy creative's new card if it had the same level of support in
alsa as the current emu10kx cards do. Any more I don't expect, but any
less would mean I don't buy one. The emu10k1 sb live was the first
creative product I was ever willing to buy and with the support it has
in linux I have been happy with it. I didn't want their older cards,
and I don't want most of the other cheap crap cards that have been
around (I used to have a few gravis cards and liked those).
Most onboard audio seems to pretty decent these days, but if you expect
midi to work, you want something a bit better.
So I for one would love to see creative offer enough documentation or
example code to replicate the features of the emu10kx on the new chip,
even if we still don't get DSP algorithms. If they don't, well I won't
buy one, and I won't recomend it to anyone either. If they do, I will
highly recomend it (if it works as well as it appears it should), and I
will buy one too.
Len Sorensen
next prev parent reply other threads:[~2005-08-23 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 9:55 Emmanuel Fleury
2005-08-19 22:52 ` Lee Revell
2005-08-20 5:17 ` Lee Revell
2005-08-20 6:48 ` Emmanuel Fleury
2005-08-20 7:08 ` Lee Revell
2005-08-22 12:18 ` [Alsa-devel] " Takashi Iwai
2005-08-22 20:38 ` James Courtier-Dutton
2005-08-22 21:54 ` Lee Revell
2005-08-23 20:41 ` Peter Zubaj
2005-08-23 18:48 ` Lennart Sorensen [this message]
2005-08-23 22:12 ` Lee Revell
2005-08-23 21:39 ` Lee Revell
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=20050823184834.GC28578@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=pzubaj@gaya.sk \
--cc=rlrevell@joe-job.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®