Re: SetParameter at note scope?
Re: SetParameter at note scope?
- Subject: Re: SetParameter at note scope?
- From: Bill Stewart <email@hidden>
- Date: Fri, 8 Aug 2003 11:55:38 -0700
The idea of the group scope is that you can create individual notes on
their own groups, where these notes can either share (or not) their own
instrument ID's (though with the part/group assignments this
flexibitility is lost)
I think the Poly Pressure controller would be the way to implement this
(and it is conformant and you have controllers that send this message)
- then you can assign which parameter (s) are going to be affected for
a part (or instrument if its in the DLS instrument definitions), and
the poly pressure controller then gives you the ability to apply this
differently for each note currently playing.
Bill
On Friday, August 8, 2003, at 10:24 AM, Marc Poirier wrote:
On Fri, 8 Aug 2003, Philippe Wicker wrote:
On Friday, August 8, 2003, at 10:00 AM, Urs Heckmann wrote:
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.
Okay, Okay. Not a very good idea it seems :-) However, I didn't mean
to
publish **all** parameters in this NoteScope. This question came to my
mind when I noticed that there are only 2 APIs that use the
NoteInstanceID: Start and Stop. As I was looking for a way to apply
(variable) pitches individually to notes in the same group I went to
the conclusion that this is impossible with the current specification
(or to be more accurate that I don't see how to do it which is
probably
nearer to the truth :-) I found that SetParameter could be a way to do
it provided a NoteScope. Well, if SetParameter is not the right way,
then the question remains pending. If I have to change "on the fly"
volume, pitch, pan, ... of a single note within a group because my
user
wants it, how do I do? Maybe I should answer "wait for the G6 or the
G7" :-))
Does anyone actually want to benchmark? Personally, I highly doubt
that
even thousands of parameter changes per rendering slice are going to
pose
much of a performance hit, but the only way to know is to try...
Marc
_______________________________________________
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.
--
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
________________________________________________________________________
__
_______________________________________________
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.