Re: MIDI-controller plugin basic
Re: MIDI-controller plugin basic
- Subject: Re: MIDI-controller plugin basic
- From: Brian Willoughby <email@hidden>
- Date: Tue, 11 Mar 2008 02:30:32 -0700
Todd,
I can't see any way to do what you want from an AU. Don't forget
that the user might connect the outboard synth's audio outputs to a
live mixer instead of an audio interface input. What you want would
not be possible without an elaborate GUI for the user to redundantly
specify the audio cabling for most of the physical studio. By the
time you've created all of this GUI, you don't really need an AU.
You're describing an application feature. Logic has one way of
dealing with this universe, by segregating MIDI, audio, and virtual
instruments (MIDI-to-Audio) each onto their own type of track. But
you could just as easily organize a DAW with the workflow you
desire. You would still be at the mercy of the user, who must
provide information about physical cabling.
Personally, I see utility in an AU which takes MIDI, processes it,
and then generates MIDI. However, I do not see any sensibility to
tying a specific MIDI output stream with an audio input (pair) within
an AU. AUs are in the middle of an audio chain, and they do not
connect directly to physical inputs. By definition, the AU host
application must control the audio input by choosing the
connections. An AU cannot select its own input source.
I hope this makes some sense. You've got a great feature idea, but
you're just trying to implement it in the wrong realm. Think: AU
host, and you're set.
Brian Willoughby
Sound Consulting
On Mar 10, 2008, at 18:38, Todd Blanchard wrote:
There is no real way for an AU to control an external synth - audio
units are for generating audio (or processing)...
FWIW, What he's asking for is probably my most requested feature.
AudioUnits are lovely, but old geezers like me still have a lot of
hardware synthesizers too. I don't really give a fig whether a synth
is real or virtual, I want all the synths in one menu and I want to
just pick one and use it on a given mixer channel.
The 'puter already knows about all the midi devices courtesy of Audio
Midi Setup. But AMS only lets you specify MIDI connections. If it
also captured the audio connections between these and the channels of
the various audio interfaces, then you could write something with the
same external interface as a MusicDevice, but instead of generating
audio, its audio output would be "generated" by simply echoing the
synth's audio inputs on its output bus. Furthermore, sending it MIDI
would just send the commands to the appropriate MIDI bus/channel
where the device lives.
In fact, I just finished implementing this although I did it at the
level of my ObjectiveC wrapper for AudioUnits and AUGraph rather than
dive into making it a "proper" AU.
-Todd Blanchard
_______________________________________________
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