From: Peter Kirk <pwk.linuxfan@gmx.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: making aoss able to wrap fopen() calls
Date: Mon, 9 Feb 2004 19:19:07 +0100 [thread overview]
Message-ID: <200402091920.53309.pwk.linuxfan@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0402091500250.2364@pnote.perex-int.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Montag, 9. Februar 2004 15:07 schrieb Jaroslav Kysela:
> On Fri, 6 Feb 2004, Peter Kirk wrote:
> > Am Donnerstag, 5. Februar 2004 17:49 schrieb Jaroslav Kysela:
> > > > Could you point me to a good idea of implementing this ? On irc I was
> > > > discussing doing a libc wrapper that replaces the fopen calls with
> > > > some substitute (that aoss can handle), but I'm not sure if its the
> > > > way to go.
> > > >
> > > > Please tell me how it can be achieved.
> > >
> > > The whole libaoss is based on glibc wrappers (open, close, ioctl,
> > > write, read, mmap) so follow this rule ;-)
> >
> > Right,
> >
> > I have done some looking at source code, and have found the places I
> > needed to find (in alsa-oss.c).
> > Two questions:
> > (1) Is my assumtion right, that I will have to write substitute functions
> > for fopen(), fclose(), fread() and fwrite() ?
> >
> > (2) My current approach is to "translate" the f* calls into calls that
> > can be handled already. Is this a good idea ?
>
> I'm more digging to this problem now and it seems that it's completely
> broken idea. Basically the FILE structure is not public outside the glibc,
> so mangling is very hard and very difficult to maintain.
>
> The sox has already support for ALSA, but because it use f* calls, it's
> limited to "hw:X,Y" devices only. So I suggest to use pipes (and stdin or
> stdout in sox) rather than doing something very ugly.
>
> I also don't like very much the situation with the OSS->ALSA wrapper.
> Right now, I'm working on a very small library which will reroute the
> native OSS calls to any dynamic library. So ALSA, arts, esd and other
> audio subsystems can use modified OSS programs directly. The modification
> of one application requires only a few minutes for a middle skilled
> programmer. Now, I need persuade audio developers to use this library
> rather than direct calls.
Ok,
that propably explains why my patch causes some weird results...will not spend
anymore time with it. Hopefuly I will see the day where I can use teamspeak
with multiple input streams.
Thanks for the update, saves me from the headaches
Peter
- --
The husband who doesn't tell his wife everything probably reasons that
what she doesn't know won't hurt him.
-- Leo J. Burke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAJ88fg2ieGvTmHiURAntnAJ9mas87AX20ZGOzbOctGDRHFRAz9gCeK0Z7
6sy3rbbRgFb2JQrcTA0CyH4=
=ka4v
-----END PGP SIGNATURE-----
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-02-09 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 16:26 making aoss able to wrap fopen() calls Peter Kirk
2004-02-05 16:49 ` Jaroslav Kysela
2004-02-06 11:28 ` Peter Kirk
2004-02-09 14:07 ` Jaroslav Kysela
2004-02-09 18:19 ` Peter Kirk [this message]
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=200402091920.53309.pwk.linuxfan@gmx.de \
--to=pwk.linuxfan@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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