From: Billy Biggs <vektor@div8.net>
To: linux-sound@vger.kernel.org
Subject: 4D-NXs (was Re: Sync Issues)
Date: Wed, 27 Oct 1999 11:40:13 +0000 [thread overview]
Message-ID: <marc-linux-sound-94102459902838@msgid-missing> (raw)
On Tue, 26 Oct 1999, Paul Barton-Davis wrote:
> > Drivers had better be forthcomming. Yes, I'm talking about cards like
> >those, such as the Event Layla and Darla, etc. Without them, it makes
> >Linux pretty useless as a multitrack platform...
>
> the manufacturers of such cards don't have much of an interest in
> Linux. i did a little work at AES to try to change that, but its going
> to be a long uphill battle.
Well, if there were a more powerful audio API, and applications that
took advantage of it, that would all change pretty quick...
> > Well, at least pretty annoying. Personally, I have two AudioPCI cards
> >and a dedicated MPU-401 card for MIDI. Each of the AudioPCI cards have
> >two dsps, giving me four /dev/dsp devices.
>
> if you had 2 4D-NX's, you'd have 64 openable (mono) channels for
> playback (*)... is that enough for you ? :))) total cost $78+postage,
> plus you'd have two excellent MIDI interfaces as well.
> (*) but just 4 mono channels for recording, sigh.
4D-NX seems to be just the chipset. Which card are you referring to
here? And, how does it get so many seperate openable channels?
More importantly, would I be able to sync channels on the same sound
card?
--
Billy Biggs vektor@div8.net
http://www.div8.net/billy wbiggs@uwaterloo.ca
next reply other threads:[~1999-10-27 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 11:40 Billy Biggs [this message]
1999-10-27 11:54 ` 4D-NXs (was Re: Sync Issues) Jaroslav Kysela
1999-10-27 13:53 ` Paul Barton-Davis
1999-10-27 20:06 ` Dan Hollis
1999-10-27 22:53 ` David Olofson
1999-10-28 0:04 ` Paul Barton-Davis
1999-10-28 0:23 ` Dan Hollis
1999-10-28 0:38 ` Paul Barton-Davis
1999-10-28 0:50 ` Dan Hollis
1999-10-28 2:46 ` John Littler
1999-10-28 12:39 ` Paul Barton-Davis
1999-10-28 18:33 ` Dan Hollis
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=marc-linux-sound-94102459902838@msgid-missing \
--to=vektor@div8.net \
--cc=linux-sound@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox