• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
[ANN] Audio IPC framework and SDK
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ANN] Audio IPC framework and SDK


  • Subject: [ANN] Audio IPC framework and SDK
  • From: Philippe Wicker <email@hidden>
  • Date: Thu, 25 Dec 2003 17:13:36 +0100

Hi all,

At last, I've been able to reach a beta state for a project I've started quite a long time ago (when there was a thread on this list about Rewire in Mac OS X).

What is it?

"Audio IPC" stands for "Audio Inter Process Communication". The archive "Audio IPC SDK 1.0.sit" contains the complete sources of a set of tools and demos app that allows CoreAudio applications (ie different processes) to write to or read from a stream of audio data. The audio is provided through a source audio endpoint and pulled by the consumer application through a destination audio endpoint. Although coded in C++, the public API is in C, and AudioEndpoints can be bound to AUs so that the framework can easily be used within any CoreAudio app.

How does it work?:

In short, the idea is to create/remove AudioEndpoints within the audio client apps, and to manage connection/disconnection of these endpoints within a central application with its own UI (AudioServices.app). As of today, an AudioClient app may create 3 types of AudioEndpoints: input, output and slave insert. Additionally there is a specialized effect AU (HostInsert.component).

- Input AudioEndpoint: it allows an app to receive data through audio streams (one stream per AudioEndpoint).
- Output AudioEndpoint: it allows an app to send data through audio streams (one stream per AudioEndpoint).
- SlaveInsert: this is a bit special. It allows to plug an external app as an insert in an AU host. The SlaveInsert can be seen as, say, a 2 pins (one in, one out) male plug.
- HostInsert AU: this is the female plug.

Binding of AUs to AudioEndpoints are managed by client apps, while the connections are managed by the AudioServices application via its GUI (a bit like it is done in AudioMidiSetup).

The archive is available at the address: homepage.mac.com/pwicker

[OT] While you are at here, you may also have a look at the other part of my site where you can find some photos of the Sahara desert (North Africa) taken during some of the travels I made in that region.

Happy christmas.

Philippe Wicker
email@hidden
_______________________________________________
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.

  • Prev by Date: Re: My First CoreMidi App Redone
  • Next by Date: Re: Developing Tool for Audio program
  • Previous by thread: Re: Newbie problem: javax.sound.midi & finding devices
  • Next by thread: ClassInfo save and restore in Reverb AU
  • Index(es):
    • Date
    • Thread