Re: Coreaudio-api Digest, Vol 3, Issue 240
Re: Coreaudio-api Digest, Vol 3, Issue 240
- Subject: Re: Coreaudio-api Digest, Vol 3, Issue 240
- From: "B.J. Buchalter" <email@hidden>
- Date: Fri, 04 Aug 2006 16:48:08 -0400
- Thread-topic: Coreaudio-api Digest, Vol 3, Issue 240
Hi Jon,
>> Why don't you write a C++ wrapper AU that calls into your (well-
>> defined C
>> audio engine).
>
> Sfront is a compiler that creates C programs that are audio
> engines from a domain-specific language (MPEG 4 Structured Audio).
>
> Altering the compiler to produce engines that are correctly-wrapped C++
> programs is a significant undertaking, given sfront's design -- a
> 100,000 line
> program that generate other programs is not easy to re-factor,
> especially
> since the output needs to remain compliant with an MPEG standard.
> Whereas writing a new audio driver for sfront is easy.
I guess my point is that you can write 1 AU that can open and talk to
(multiple) sfront compiled C programs
> It's easier for me to reverse-engineer the C API out of AUBase,
> so I'll just go that route. Thanks,
Perhaps. Either way makes sense. My point is that you can define your own
API between the AU shell and the sfront audio driver. Then you can utilize
the AU shell for any number of compiled sfront programs.
AUBase is just an implementation of a wrapper to the C API, which is pretty
well documented I think. It is just a set of component manager selectors to
implement properties, parameters and commands (like process).
I think the selectors are defined in the AU headers (in the system headers
-- not the AU SDK).
Best regards,
B.J. Buchalter
Metric Halo
5 Donovan Drive
Hopewell Junction, NY 12533 USA
tel +1 845 223-6112
fax +1 603 250-2451
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden