Re: MultiTimbralSynth + Source Code
Re: MultiTimbralSynth + Source Code
- Subject: Re: MultiTimbralSynth + Source Code
- From: Urs Heckmann <email@hidden>
- Date: Sun, 20 Jul 2003 00:37:50 +0200
Am Samstag, 19.07.03, um 21:25 Uhr (Europe/Berlin) schrieb Bill Stewart:
OK - This is very interesting...
We've had a long week of discussing how this should work, and are in
the process of sending out what we think is a template of expectations
for this kind of functionality...
So - a note of caution
It compiles, ship it...
I think there will need to be some changes to the way this is
implemented to completely accomodate the ability to layer parts on
different control groups, etc...
Yes. I find that, too.
I'm in the process of writing up a summary of what we think will work
for this (and some more definitive statements of what we actually
intended the group scope to address)...
So, Urs, I hope there's a pre-release disclaimer in this SDK :)
Huh? - I only release pre-releases. People know that 8-)
I'll get out a summary of this as soon as possible...
Cool!
However, the stuff I offer is part of a thinking process, no more no
less.
Furing that process, I found out I had to make decisions. Decisions ==
Uncertainty. For instance, there's the decision if "Multi Presets" hold
complete "Singles" or if they just point to them. In the current
situation, I put Singles completely into Multis. Your thinking process
may come out differently. (Though I find it useful to have Singles
stored completely in Multis. More diversity, more flexibility)
idea (stupid, maybe): Can Singles be Instruments? - .aupreset == Multi,
.auinstrument == Single?!?
Furtherly I wanted to check out how "deep" the Scope/Element stuff is
implemented. - I think there are some areas where they miss, for
instance when requesting parameter lists. - These are only Scope-wise,
but not Element specific, which is inconsistent IMHO as Parameters can
have Scope and Element addresses.
You see, we're talking about abstract concepts that we adopted from
example code and then neglected because it just worked at some point.
But now we need to get the grip of what these concepts were made for.
The best way to do this, is to play around with these concepts and see
what their mom says 8-)
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.