Re: in-memory AudioUnit?
Re: in-memory AudioUnit?
- Subject: Re: in-memory AudioUnit?
- From: Patrick Gostovic <email@hidden>
- Date: Wed, 12 Nov 2003 14:02:21 -0500
Have you considered bundling the "private" plugins in the application
bundle? I have a similar situation where I'm making components that
don't really make sense out of the context of my app. Have a look at
CFBundleCopyResourceURL, CFURLGetFSRef, RegisterComponentFileRef.
pg
On 12-Nov-03, at 1:22 PM, Christopher Corbell wrote:
>
Is it possible to compile and register an AudioUnit
>
in-memory in an application, without ever creating a component
>
package on disk?
>
>
We're working on a Cocoa host and may include a few original
>
units. While most units will probably be public there are a
>
couple that may be specific to our app. We could just do the
>
unit normally and hamstring functionality if our app's not the
>
host, but I'm still curious whether an in-memory-only unit
>
is possible, and if there's an example of this.
>
>
Thanks,
>
Christopher
>
_______________________________________________
>
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.