Re: Do any hosts support the "interesting" parts of the AU API?
Re: Do any hosts support the "interesting" parts of the AU API?
- Subject: Re: Do any hosts support the "interesting" parts of the AU API?
- From: Stefan Gretscher <email@hidden>
- Date: Wed, 15 Feb 2006 23:16:22 +0100
Hi Ian,
we ment to add support for the Extended Note API to Logic (mostly for
taking advantage of its tuning capabilities), but got stuck with it
for several reasons.
While some of the lesser details are still being discussed with the
CoreAudio team, the main issue is that many (or rather: most)
existing AUs fail to support the Extended Note API (despite it being
a mandatory part of the AU spec..).
Since there is no way for a host to figure out which AUs suffer from
the problem and which AU is fine with the Extended Note API, we could
not go ahead and switch to the new API - we couldn't release a Logic
update that suddenly would stop working with most major AU
instruments. So we'll have to wait for the majority of developers to
update their AUs according to the spec before moving on in this area...
There is hope though: as Bill announced in his reply, AU Lab will
soon switch to the Extended Note API, so there'll be a reference test
case for developers and an increased pressure to move on to
supporting the new API alongside "old-school" Midi.
For the time being, we are alas stuck with utilizing standard MIDI
commands for communicating Logics tuning features to the AUs...
Best,
Stefan
Am 15.02.2006 um 14:23 schrieb Ian Kemmish:
Apart from the fact that a PowerPC ran my code roughly three times
faster than a Pentium (sigh), the main reason I had for
resurrecting my synth architecture two years ago was that the AU
API seemed to be making a determined attempt to get away from
MIDI. Little things like:
1) StartNote and StopNote - the fractional note numbers are
essential if you want scales with more than twelve notes per octave
without sacrificing usable range. The ability to specify an
arbitrary instrument is nice too (although, Apple, it would be nice
if I could pass in a dictionary of arbitrary note parameters
instead of an array of conventional note parameters.)
2) Arbitrary groups, not just 16 pretending to be MIDI channels.
3) Arbitrary parts.
4) Arbitrary named parameters published on group and part scope.
All I've seen hosts do so far is query the AU's list of parameters
on global scope -- for a multi-timbral modular synth where the user
decides what parameters are published by each voice, this is
useless! Even for a synth where the list of parameters is the same
for all time and across all groups, they should still surely be
published on group scope, not global scope?
I *think* my synth supports all of these - but without a suitable
host, it's impossible to test this assertion.
My synth is about to enter alpha test, and I'm depressed that in
2006 I'm still forced to look to the user like a MIDI synth... If
your host supports any of the above, please let me know!
------------------------------------
Stefan Gretscher
plug-in development & 3rd party plug-in support
Logic Pro team, Apple Computer
email: email@hidden
phone: (+49)-4101-495-586
(Central European Timezone)
_______________________________________________
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