Re: man coreaudio (?)
Re: man coreaudio (?)
- Subject: Re: man coreaudio (?)
- From: Chris Reed <email@hidden>
- Date: Mon, 13 Oct 2003 10:07:19 -0500
Stanko,
I would recommend looking at PortAudio for such a project. If all you
need is a simple (and, surprise, portable) audio I/O library, it fits
the bill perfectly.
http://www.portaudio.com/
-chris
On Oct 12, 2003, at 5:20 PM, Stanko Juzbasic wrote:
Hello,
Thanks for your good will to encourage my learning efforts.
From the point of objective truth, you're probably right - who am I to
argue...
Unfortunately, I have as much time as I have and as few objectives as
I do:
These are porting some educational software that I used to write for
Columbia University Music Department some years ago, on SGI - IRIX,
which is (as you may know) a well documented system, with literally
gigabytes of help files. My only ambition is to port audio I/O
routines, so students can use those apps on their macsosx boxes. I
can't afford time to take care of Cocoa, or Java. It's not even my
career - I'm a music composer.
It is very difficult for me to get around a new, obscurely documented
API.
I really find a pity eventually having to work without a consistent
reference, yes, things as simple as:
man strtok
(APPLE, CAN YOU READ THIS?)
I don't believe working should ever be an excuse for not simultanously
documenting own work.
Thanks again,
Stanko
On Sunday, October 12, 2003, at 06:05 PM, Chris Reed wrote:
On Friday, Oct 10, 2003, at 17:36 US/Central, Stanko Juzbasic wrote:
Hi, Chris,
Thanks for your concern.
I don't quite understand your reply.
Do you suggest that I memorize prototypes from the header files, by
guessing in which header they
might be located?
there is a lot of headerdoc documentation in the headers. you should
be thoroughly familiar with the headers, anyway, if you're going to
be using the api. for any new api i learn, the headers are the first
place i head to.
Or search in /Developer/Documentation in order to find everything
except for what I need?
there's documentation about audiounits, the java api, and coremidi in
there. the java api is almost exactly the same as the c api.
Or consult a PDF which is already obsolete?
that pdf covers some high-level concepts that are useful.
Isn't there a less painful way of dealing with CoreAudio?
it's not painful at all... i found it to be quite easy to learn.
Shouldn't Apple take care of that?
they are. there's at least one full-time tech writer working on new
coreaudio documentation. certainly this should have happened earlier,
but i'd much rather have the developers working on the api instead of
documentation.
the most important thing is that the apple developers make themselves
available on the coreaudio-api list. this is by far the best source
of information anyone could hope for.
there's more than enough information available. just because it's not
all in one pdf doesn't make it any less valuable.
cheers
-chris
CA is a highly sophisticated API, which is anything else but trivial.
I hoped it also might also be accompanied by a reference which is
worth it.
Is there a commercial CoreAudioManual.app one is supposed to buy in
order to have it all in one place?
Stanko
On Friday, October 10, 2003, at 11:03 PM, Chris Reed wrote:
1. header files
2. /Developer/Documentation/CoreAudio
3. the list archives (this list, coreaudio-api)
4. the CoreAudio Swiki: http://www.mat.ucsb.edu:8000/CoreAudio
5. there's an old coreaudio pdf somewhere on Apple's developer
site, but it's out of date now
cheers
-chris
On Oct 10, 2003, at 1:18 PM, Stanko Juzbasic wrote:
BTW,
is there anything close to a CoreAudio man page, or reference
document?
Stanko
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.