Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
To: linux-sound@vger.kernel.org
Subject: Re: Status of ALi5451(trident)?
Date: Fri, 12 Jul 2002 18:03:09 +0000	[thread overview]
Message-ID: <marc-linux-sound-102649697824581@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-102629084116513@msgid-missing>

Neale Banks wrote:
> 
> On Fri, 12 Jul 2002, Joern Nettingsmeier wrote:
> 
> > Neale Banks wrote:
> [...]
> > > Are you suggesting that the current drivers in 2.2 and 2.4 kernels (OSS?)
> > > aren't worth using?
> > >
> > > That is, that I should just give up on those and use ALSA?
> >
> > basically, yes. the oss drivers are probably perfectly ok,
> 
> 'tis not my experience :-(
> 
> > but the whole
> > alsa architecture is superior to oss, although more complex. if you just
> > need simple audio playback/recording, oss is fine. for anything more
> > demanding (low-latency operation, multichannel or even full-duplex with
> > some cards), go for alsa.
> 
> My immediate requirements are fairly mediochre:
> 
> 1) audio for mpeg video playback
> 2) midi synth for rosegarden
> 
> > it's going to be "official" soon, it's already in the current
> > development kernel.
> 
> Yes, ALSA appears to be coming in 2.5 - but my interest right now is in
> 2.2 and 2.4.

alsa is widely used for 2.2 and 2.4, only you have to compile the
modules yourself (they are not shipped and built along with the kernel).

> I'm somewhat astonished that (a) OSS sound doesn't want to work for me in
> 2.2 and (b) MIDI code appears to be missing from the OSS driver in 2.4.

alsa's midi sequencer is really very nice. you can hook just about
anything together that speaks alsa-seq. check out the kaconnect alsa
midi patchbay, for instance (suse.de/~mana iirc).

give it a try. from your past experience, it can be any worse :)

best,

jörn

> I have that awful Arthur Dentish feeling that I've missed something
> here....
> 
> > btw, there is a linux-audio-user list at
> > http://www.linuxdj.com/audio/lad, in case you have questions concerning
> > which application to choose for a job etc.
> 
> Not one of my immediate problems, but thanks for the pointer.
> 
> Regards,
> Neale.

  parent reply	other threads:[~2002-07-12 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10  8:49 Status of ALi5451(trident)? Neale Banks
2002-07-10  9:07 ` Joern Nettingsmeier
2002-07-12  6:29 ` Neale Banks
2002-07-12  8:20 ` Joern Nettingsmeier
2002-07-12 14:34 ` Neale Banks
2002-07-12 18:03 ` Joern Nettingsmeier [this message]
2002-07-17  5:36 ` Neale Banks

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-102649697824581@msgid-missing \
    --to=nettings@folkwang-hochschule.de \
    --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