Hi all,

I’ve got an audio algorithm that I’d like to port over to run in a MacOS/X 
audio environment.  The algorithm is somewhat similar to a 24x24 mixer, in that 
it takes 24 mono audio streams as input, swizzles them all together, and emits 
24 mono audio streams as output.

From studying the Core Audio documentation, it appears that this algorithm 
could be represented by a “signal processor” style Audio Unit.  What I’m not 
sure about, however, is how useful such an Audio Unit would be on a machine 
that doesn’t also have a 24-channel audio input device and a 24-channel audio 
output audio device to connect it to.

In particular, what I’d like to be able to do is connect (whatever audio input 
or output devices do exist on the host Mac) to various specified user-specified 
subsets of my algorithm's inputs/outputs; for example, I might want to feed 
mixer outputs 5 and 8 to my Mac’s headphone jack, and feed mixer outputs 15 and 
16 to my Mac’s line-out jack.  Similarly, I might want my Mac’s microphone jack 
to feed in to input 3 and my USB headset’s mic to feed in to input 4 of the 
mixer algorithm.

If I implement my mixing algorithm as a 24-channel Audio Unit, are 
audio-routing decisions like those described above something that can be done 
outside of my app?  If so, would they be done using “Audio MIDI Setup”, or “AU 
Lab”, or is there some other GUI that better handles that sort of thing?   Or 
if not, do I need to create the necessary GUI myself?  Or is there some other 
way to go about this that would better interface with the rest of the Mac audio 
environment?  Perhaps there is some example code that is particularly relevant 
to this sort of use case?

Thanks for any advice you can give,
Jeremy


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to