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: William Stewart <email@hidden>
- Date: Wed, 15 Feb 2006 14:00:43 -0800
The AU Lab application has some support for these features within the
limited context that it provides:
On 15/02/2006, at 5:23 AM, Ian Kemmish wrote:
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.)
In the next release of AU Lab (due shortly) this is the ONLY way
notes are started and stopped. We might look into associating tunings
aside from 12-tone equal temp with the incoming MIDI note ons
2) Arbitrary groups, not just 16 pretending to be MIDI channels.
3) Arbitrary parts.
This is an AU issue I think - I'm not sure what you need a host to do
to support this?
4) Arbitrary named parameters published on group and part scope.
AU Lab will also do this in the generic view - at least on Part
scope. Group scope is a scope defined for control mappings.
Publishing a param on group scope is analogous to saying "I
implement Mod Wheel" in a MIDI spec. See the doc on parts and groups
for more discussions of these.
Bill
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!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -
Ian Kemmish 18 Durham Close, Biggleswade, Beds
SG18 8HZ
email@hidden Tel: +44 1767 601361 Mob: +44
7952 854387
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -
_______________________________________________
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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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