At Mon, 12 Jan 2004 07:54:37 -0500,
Paul Davis wrote:
>
> >Yes, we're aware that our APIs are rather too much complicated for simple
> >applications. We are designing the very simple (current name ordinary)
> >APIs to let more developers join us. But as Kai noticed, these APIs will
> >be a bit
>Yes, we're aware that our APIs are rather too much complicated for simple
>applications. We are designing the very simple (current name ordinary)
>APIs to let more developers join us. But as Kai noticed, these APIs will
>be a bit limited, so they won't be intended for more complex applications.
On Mon, 12 Jan 2004, Lorn Potter wrote:
> > Believe me, I agree with you 100% with regards to importance of
> > simplicity. ALSA still has some complex edges, but is has come a long way.
> > More documentation, tutorials and example code are still needed, but it
> > takes time (and volunteers) to
On Monday 12 January 2004 9:11 am, Kai Vehmanen wrote:
> Now the commercial OSS (www.opensound.com) is a different thing. It too
> (like ALSA) provides coherent behaviour across different drivers.
I guess this is what I am talking about, really.
> > _Dont get me wrong_, ALSA is great and a lot
On Mon, 12 Jan 2004, Lorn Potter wrote:
>> I am currently looking into rewriting our current OSS sound routines to
>> native ALSA, as it seems OSS will invariably be phased out now that the
>> ALSA driver is distrubuted with the Linux kernel, plus ALSA seems to have a
> Personally, I hope OSS com
On Mon, 12 Jan 2004 08:29:54 +1000
Lorn Potter <[EMAIL PROTECTED]> wrote:
> On Monday 12 January 2004 4:13 am, James Wright wrote:
> > I am currently looking into rewriting our current OSS sound routines to
> > native ALSA, as it seems OSS will invariably be phased out now that the
> > ALSA drive
On Monday 12 January 2004 4:13 am, James Wright wrote:
> I am currently looking into rewriting our current OSS sound routines to
> native ALSA, as it seems OSS will invariably be phased out now that the
> ALSA driver is distrubuted with the Linux kernel, plus ALSA seems to have a
> great number of
Ultimately i think with ALSA we could do away with the concept of calling
update_jsound() in the game loop and instead use asyncrosnous mode and use
update_jsound() as my callback function? Although i'd need to get ALSA to call
update_jsound() when we are in our last period, so we can write
> I am currently looking into rewriting our current OSS sound routines to nat
>ive ALSA, as it seems OSS will invariably be phased out now that the ALSA driv
>er is distrubuted with the Linux kernel, plus ALSA seems to have a great numbe
>r of benefits for us.
>
> Our current sound routines per
Hello,
I am currently looking into rewriting our current OSS sound routines to native
ALSA, as it seems OSS will invariably be phased out now that the ALSA driver is
distrubuted with the Linux kernel, plus ALSA seems to have a great number of benefits
for us.
Our current sound routines p
10 matches
Mail list logo
