Trojan AUs
Trojan AUs
- Subject: Trojan AUs
- From: Andre Schnoor <email@hidden>
- Date: Thu, 5 Mar 2009 13:01:05 +0100
Hi all,
the situation I have is that I want to hook up a huge composition
application with DAWs such that the DAW hosts the sounds played by the
"virtual fingers" of the application. The application will need to
load and unload AUs and their presets without any user interaction
required. Think of this arrangement as a sound server with hot
swapping and garbage collection.
I am aware that this sort of "remote control" is not supported by any
DAW to date (and probably never will), so my question is how to
achieve this by means of a specialized AU plugin.
Imagine an AU that is loaded into each channel strip of the DAW,
acting as a wrapper for hosting one arbitrary AU instrument itself. It
communicates with the application via TCP, pipes, ReWire, SYSEX, or
whatnot, receiving instructions to load and unload other AUs and their
respective presets as needed by the application. The DAW would see it
as a black box, thinking the user is doing all this manually ;-)
For arrangements with up to 50 instruments, this would mean 50 empty
wrapper AUs loaded into the DAW in advance, waiting to receive
commands from their master application.
Would that be a reasonable solution? Has anyone perhaps already done
similar things?
Any comments and suggestions are appreciated!
Andre
P.S: You might think, why the heck? The idea behind this is that it
doesn't make sense to reinvent the wheel and implement yet another
host while all these wonderful DAWs out there are mature and robust
already.
_______________________________________________
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