• 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: How are AU User Presets handled?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How are AU User Presets handled?


  • Subject: Re: How are AU User Presets handled?
  • From: Chris Reed <email@hidden>
  • Date: Wed, 12 Feb 2003 18:05:53 -0600

On Wednesday, Feb 12, 2003, at 14:34 US/Central, Bill Stewart wrote:

One thing that didn't come up previously is the idea that aside from organising particular presets into a directory, there was no discussion of further specialising this into directories of presets (a similar concept to banks)...

Thus:

Library/Audio/Presets/Mfg/AUName/MyPlug/
Industrial/
blah1, blah2 -> these are the individual presets
ProgRock/
blah1, blah2 -> ...
etc...

That's actually not a bad idea is it?

The host should then build the user preset menu based on the names of directories that are contained within the plugin preset dir. (This could actually be a recursive n-level deep series of pop up menus/directories for the categorization freaks:)

That's actually a great idea, and pretty easy to implement too. The only question I have is the best way to ask the user for the name of the "bank" or subdirectory. Should N levels deep be supported? I guess the absolute best way would be to display a dialog similar to a save file panel.

I'll try to add support for this to the AUPresetManager class in SynthTest so there is an implementation available for people to examine and argue over. :)


As for the session activities - I think that is out of the scope of the AU and is a host issue. But one question does remain

Logic currently builds the preset menus for you - so this is really an issue of how the host will present user presets to the user. We are not expecting the AU's view to build these menus - or are we? That is the only point of confusion I have about this discussion as our previous discussions were discussions about how the host apps would handle these, NOT the AUs.

No... AU edit views should *not* normally present a menu of presets. This should be handled by the host. Imho, of course.

cheers
-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: 
 >How are AU User Presets handled? (From: Bill Stewart <email@hidden>)

  • Prev by Date: Re: Troubles with MIDI input
  • Next by Date: Re: Property notification questions
  • Previous by thread: How are AU User Presets handled?
  • Next by thread: Re: How are AU User Presets handled?
  • Index(es):
    • Date
    • Thread