Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Paul Barton-Davis <pbd@Op.Net>
To: linux-sound@vger.kernel.org
Subject: Re: 4D-NXs (was Re: Sync Issues)
Date: Wed, 27 Oct 1999 13:53:34 +0000	[thread overview]
Message-ID: <marc-linux-sound-94103039210064@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94102459902838@msgid-missing>

>> >  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...

actually, no.

i've had many discussions with different companies. the problem has
*never* been "Oh, Linux's audio API isn't worth us developing
for". Its also never been "Well, what applications are there ?"
(remember, most of these companies simply *assume* the existence of
apps, or alternatively, write their own). 

Instead, its a combination of:

      * "some other people wrote a Linux driver for our board and it sucked"
      * "we don't have enough programmers to do that"
      * "we don't have any written documentation to give you guys -
         we wrote the driver by having the software group sit in with
	 the hardware group"
      * "we think our hardware's proprietary secrets will be revealed
         if there is a source code driver"
      * "Linux ? Is that like Cakewalk ?"

>  4D-NX seems to be just the chipset.  Which card are you referring to
>here? 

go to www.hoontech.com and look at the SoundWave NX.

--p

  parent reply	other threads:[~1999-10-27 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 11:40 4D-NXs (was Re: Sync Issues) Billy Biggs
1999-10-27 11:54 ` Jaroslav Kysela
1999-10-27 13:53 ` Paul Barton-Davis [this message]
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-94103039210064@msgid-missing \
    --to=pbd@op.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