• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Mutitimbral - A clarification, sort of
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mutitimbral - A clarification, sort of


  • Subject: Re: Mutitimbral - A clarification, sort of
  • From: Chris Reed <email@hidden>
  • Date: Thu, 17 Jul 2003 15:48:51 -0500

On Thursday, Jul 17, 2003, at 15:05 US/Central, Urs Heckmann wrote:

Chris,

I'm obviously too stupid to get it right 8-)

:-P


Note events is no problem, never was.

But how should I find out about the group in AUParameterSet() or AUBase:SetParameter()?!?

Furtherly, how should I find out to which group I assign a Preset on RestoreState()/NewfactoryPresetSet()? (Here having in mind that the AU is not aware of the AUView, where some - but not all - hosts put their preset mechanisms)

A multitmbral-aware host should offer awareness of groups, hence offer group specific automation & state handling. I do not see how this should be accomplished with current implementations, due to lack of GroupID arguments in critical methods.

Hmmm. Or do I have to understand it this way that in GroupScope, ElementID == GroupID?!? (Which still doesn't solve the State/Preset question, only the parameter/automation issue)

Yes, that's it exactly! In the group scope, ElementID == GroupID. And GroupID == MIDI channel.

And you're right, there is the problem with presets. But hopefully Chris Roger's suggestion will be implemented, and the problem will be solved.

For now, you could just consider all presets to be global, even factory presets. They would encapsulate the state of each group. Certainly not a preferable way to handle it, but it would at least work with what we have now.

It's in your custom UI that you would provide the way for the user to select which patch (I'm considering "patch" as sub-global/per-group and "preset" as global) is assigned to which group. Later, when hosts support group level presets, this won't be as necessary.


Well. I'm tired today. Will come back to it later.


Sleep well. :-)

-chris
_______________________________________________
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.

References: 
 >Re: Mutitimbral - A clarification, sort of (From: Urs Heckmann <email@hidden>)

  • Prev by Date: Re: Mutitimbral - philosophy
  • Next by Date: Hardware control surfaces (was Re: Private Parameters)
  • Previous by thread: Re: Mutitimbral - A clarification, sort of
  • Next by thread: Re: Mutitimbral - A clarification, sort of
  • Index(es):
    • Date
    • Thread