• 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: Changing published parameters list.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changing published parameters list.


  • Subject: Re: Changing published parameters list.
  • From: William Stewart <email@hidden>
  • Date: Tue, 27 Jan 2004 15:44:46 -0800

On 27/01/2004, at 12:27 PM, Philippe Wicker wrote:

Hi all,

This may look a bizarre question. I'm thinking of an AU that may have to change the public parameters when new presets are loaded. For instance, a multi effect AU could need to publish parameters for a chorus and a delay for a given preset, or parameters for a flanger and a reverb for another preset, etc. Of course, parameter changes are not the only issue here. If parameters are changing, the UI has to change also. Same needs may arise for a MusicDevice offering instruments based on different waves generation algorithms.

Hence my questions: is it possible to do this with the current AU specifications? If yes, it could require some kind of "renegotiation" with the host app.

yes - this is possible and entirely within the AU spec. Further the generic view we ship will mostly do the right thing and respond correctly to this (there's one issue to do with changing ranges of params that we have to fix here).


Could it be feasible without needing changes to existing hosts?

This is the problem. Especially given the application of automation curves and the like to different 'versions' of an AU.

The solution that people seem to be settling on (for better or worse) is having the AU publish generic parameters, using the name-value translation services, and providing a means for a user to redefine the named representation for these different parameters. (At least that is one solution).

I'm not sure that there is really a clear-cut answer to this and I also expect that host apps will evolve over time to accommodate a richer plug=in model than was previously available...

Bill


Thanks,

Philippe Wicker
email@hidden
_______________________________________________
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.
References: 
 >Changing published parameters list. (From: Philippe Wicker <email@hidden>)

  • Prev by Date: Changing published parameters list.
  • Next by Date: Re: Streaming OS X audio over network
  • Previous by thread: Changing published parameters list.
  • Next by thread: MIDI pan message (CC#10) to kControllerPan in QTMA
  • Index(es):
    • Date
    • Thread