On Wed, Feb 11, 2015 at 11:08 PM, Jeremy Friesner <[email protected]>
wrote:
> 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?
this all depends on the host application the user chooses to run your
plugin. there are actually 2 layers of routing (at least):
* sources outside of the host application (hardware or software) and
how they connect to the inputs of the host application
* connections between the inputs of the host application and your
plugin
some hosts will give you full control over both layers. others will give
you control over only one of them, and some will give you no control at all.
writing a plugin has the HUGE benefit that it frees you from dealing
directly with audio interface hardware, especially if you imagine users
interacting with multiple devices. it has the drawback that your plugin has
absolutely no control over where its inputs come from or where they go.
_______________________________________________
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]
