"time limited" is bad news indeed. In more honest language it means the
primary developers aren't doing much primary development. I myself (a)
don't have time (am not willing) to maintain PortAudio, and (b) lack the
necessary expertise on the Mac (because I don't have one, not because I'm
unwilling to learn). 

If there's a developer in the Csound community who's willing to do this,
please, step up to the plate and get on the PortAudio developer list and
become a "primary maintainer."

However, Ross Bencina is certainly paying attention to our posts, so maybe
we'll see some effective maintenance. I hope.

Original Message:
-----------------
From: Richard Dobson richarddobson@blueyonder.co.uk
Date: Fri, 14 May 2004 10:01:04 +0100
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4697] Re: PortAudio


The crucial advance in v19 is the ability to support more than one driver
model 
within an application, e.g. both ASIO and DirectSound, or both ASIO and 
CoreAudio/HAL on OS X. Not all these platforms are at equal stages of
support, 
but I do get the impression they are all progressing.

If we stayed with v18 we would have to build separate versions of Csound
for 
ASIO, DirectSound and CoreAUdio, etc.

The more contributors there are to PortAudio v19, the sooner it will be 
complete. Ross Bencina (authot of AudioMulch) makes the point that much of
the 
stuff that remains to be done is "vey simple"; but the primary developers
on 
each platform are very "time limited".


Richard Dobson

Anthony Kozar wrote:
> I have been wondering about this myself.  v19 has had very poor (or
> non-existent) support for several platforms/audio drivers, so far.
> (Although this may be improving ?)
> 
> I haven't tried either v18 or v19 primarily because Csound5 is supposed to
> use v19 and that version does not work on MacOS (9) yet.  So I don't
pretend
> to speak authoritatively, but it is beginning to look to me that unless we
> decide to complete PortAudio v19 ourselves, Csound5 will likely be delayed
> for some platforms.  (Or at least real-time support will be).
> 
> Can anyone here who watches the PortAudio mailing list gauge how quickly
> progress is being made?
>  
> Anthony Kozar
> anthony.kozar@utoledo.edu
> 
> 


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

I have been considering attempting to do the Mac port for PortAudio v19
since it appears no one else has volunteered.  I have concerns though that I
am not up to the task.

I wrote a real-time software synth for Mac OS 9 as my master's project last
year.  However, I used a third-party library for interfacing with the Mac
Sound Manager so that I wouldn't have to delve into the details too much.
(I did have to diagnose and fix several low-level problems in the library
anyways, but ...)

I also am not competent as a programmer for critical threading and
concurrency issues.

So, the short of it is I could try, but I cannot guarantee the result won't
be buggy and cause more headaches for others in the long run.

Anthony Kozar
anthony.kozar@utoledo.edu


On 5/14/04 7:19 AM, gogins@pipeline.com etched in
stone:

> I myself (a)
> don't have time (am not willing) to maintain PortAudio, and (b) lack the
> necessary expertise on the Mac (because I don't have one, not because I'm
> unwilling to learn).
> 
> If there's a developer in the Csound community who's willing to do this,
> please, step up to the plate and get on the PortAudio developer list and
> become a "primary maintainer."