All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <pbd@op.net>
To: Ivica Bukvic <ico@fuse.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: question regarding latest CS4205 laptop soundcard driver
Date: Wed, 27 Feb 2002 22:09:11 -0500	[thread overview]
Message-ID: <200202280309.WAA14147@renoir.op.net> (raw)
In-Reply-To: Your message of "27 Feb 2002 14:11:18 EST." <1014837078.10692.18.camel@meowing.memh.uc.edu>

>I agree, my "flawless" statement was certainly overrated. Yet, the
>question remains: what am I to do as a musician needing to utilize my
>portable laptop while the apps/software I currently use get ported to
>the JACK architecture (if they get ported at all)? 

1a) Get Abramo to post (or point to) detailed information on using a
   "share" PCM device

1b) Get Abramo or Jaroslav to post (or point to) detailed information
   on setting up libaoss (specifically, how to map /dev/dspN to a specific
   ALSA PCM device)

2) edit your ~/.asoundrc file to define a "share" PCM device

3) run all your legacy (OSS) apps with LD_PRELOAD set to preload libaoss.
      a small wrapper script is useful for this; ALSA may already
      come with one (*)

4) run all your newer (ALSA) apps with an argument telling it to use
     the "share" PCM device

and you should be done. if, that is, the "share" device type is really
working. if not, you can help us debug it.

--p

(*) something like:

% cat aoss
#!/bin/sh

export LD_PRELOAD=/where/i/put/libaoss.so
exec $*
% 

then you can just run OSS apps like this: 

% aoss oss-app-name oss-app-args...

i know this appears hacky. like i said, there is no way around this
because of the way OSS was designed.




_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  reply	other threads:[~2002-02-28  3:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200202271510.KAA11571@renoir.op.net>
2002-02-27 19:11 ` question regarding latest CS4205 laptop soundcard driver Ivica Bukvic
2002-02-28  3:09   ` Paul Davis [this message]
2002-02-28  5:32     ` Ivica Bukvic
2002-02-28 14:12   ` Steve Harris
2002-02-27  9:02 Patrick Shirkey
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27  8:48 Patrick Shirkey
     [not found] <Pine.LNX.4.44.0202261906010.21337-100000@sasami.anime.net>
2002-02-27  6:00 ` Ivica Bukvic
     [not found] <Pine.LNX.4.44.0202261636480.19581-100000@sasami.anime.net>
2002-02-27  2:26 ` Ivica Bukvic
     [not found] ` <000001c1bf36$280ec3c0$ac1f830a@ico>
2002-02-27  3:09   ` Dan Hollis
2002-02-27  3:31   ` Andy Wingo
2002-02-27 15:10   ` Paul Davis
     [not found] <20020226072437.47ED22756@sitemail.everyone.net>
2002-02-26 22:49 ` Ivica Bukvic
2002-02-27  0:41   ` Dan Hollis
2002-02-26  0:11 Ivica Bukvic
2002-02-26 10:59 ` Steve Harris

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=200202280309.WAA14147@renoir.op.net \
    --to=pbd@op.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=ico@fuse.net \
    /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.