Re: How to connect AU with external apps
Re: How to connect AU with external apps
- Subject: Re: How to connect AU with external apps
- From: Brian Willoughby <email@hidden>
- Date: Wed, 25 Aug 2010 15:25:53 -0700
On Aug 25, 2010, at 14:00, andermoo wrote:
On Jun 22, 2010, at 07:37, andermoo wrote:
On Tue, Jun 22, 2010 at 4:33 AM, andermoo
<email@hidden> wrote:
what is the recommended way for an AU to communicate with an
external
application (non-realtime)? If I used OSC, would that conflict
with the
host's own use of OSC (if any)?
connect for what purpose? control? sharing audio data?
Control. I want to make the AU respond to commands sent by the
app and feed it with content (MIDI). Timing is not critical. The
idea is to have multiple AUs (one per track) that are coordinated
intelligently by one master app.
It seems like you want to write an AU host application. Is there
any reason why your control app should not actually host the AUs
that you want to control with it?
Brian Willoughby
Sound Consulting
Hi Brian,
sorry for my late reply, I seem to have missed yours.
the reason I don't want to write a host application is that I
probably can't. Production-quality hosting with mixing and effects
is a complex endeavour. There are many capable and mature DAW out
there, so why should I reinvent the wheel and eventually fail?
If it is possible to load, say 20-50 instances of the AU into
Logic, each of which listens to commands from my master application
(e.g. to load a plug-in, select a preset, receive MIDI data), I
could leverage the power of a very mature DAW for sound rendering,
while focussing on music-related problems with my app.
The question is, whether it would be possible to have all these
instances communicate with the app via OSC (or another means for
IPC) without disrupting the host? I wouldn't need real-time speed,
rather batches of commands and data, scheduled ahead of time.
If my idea turned out to be unrealistic, then I would need to look
for existing host code and start from that. I definitely want to
avoid many years of coding unless absolutely necessary.
Andre
The term "host" covers an extremely wide range. Just because Logic
is called a "host" doesn't mean that it is always so difficult to
write an application to host AudioUnits. In fact, it's actually
rather easy. That's part of the power of CoreAudio.
Perhaps you should explain what you're trying to do. So far, you've
not listed any features of Logic that you will be leveraging other
than the ability to host 20 to 50 AudioUnits on multiple tracks,
presumably with each track reading from audio files, and mixing the
results. These things are all made easy by CoreAudio and AUGraph.
It's only when you start adding feature-rich GUI and tons of
additional features that you get into years of coding like the
technology represented by Logic.
You might also want to do some research into the existing features of
Logic. It has MIDI support that is so extensive it's practically a
programming language of its own. You could potentially hook up a
MIDI controller to Logic, and with clever programming of the
Environment, you could solve your problem without writing a control
application at all.
Brian Willoughby
Sound Consulting
_______________________________________________
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