Re: SetParameter at note scope?
Re: SetParameter at note scope?
- Subject: Re: SetParameter at note scope?
- From: Urs Heckmann <email@hidden>
- Date: Fri, 8 Aug 2003 10:00:02 +0200
Am Freitag, 08.08.03, um 08:50 Uhr (Europe/Berlin) schrieb Philippe
Wicker:
Hello all,
Following the recent thread about AU MIDI events scheduled beyond next
rendering slice, I am asking why there isn't any SetParameter at note
scope. There is the group scope which is fine as long as you want to
deal with, well, a group of notes. There may be situation where a
user would like to modify parameters such as pitch, volume, or
whatever for a single note within a group (e.g. playing 2 notes with
the same value - but now with different ID - and modifying the pitch
of one of them). It's not opposed to the group mechanism, simply
complementary. Any comments?
I'd vote for an implementation of Polypressure. (I have an EPS16+,
remember?)
Well, maintaining the whole state (== all parameters) for each instance
of voice (== note played) is a nice feature of some expensive hardware
synths, but for efficient native implementations that share cpu with
other stuff, it's a bit like overkill. This is at least my guess. With
my currently 8 voices and 140 parameters, I'd have to track more than
1000 values during processing (global automation tasks & single voice
changes). That would be more time consuming than anything I do anyway.
Cheers,
;) Urs
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.